Action event IDs for missing child contexts ?

[Tom Zeller]

I guess my question is : should we define an event id for every
context required in actions ?

Specifically, SignAssertions needs a SecurityParametersContext and
it's SignatureSigningParameters. So, I could add

 INVALID_SECURITY_PARAM_CTX = "InvalidSecurityParametersContext"

to org.opensaml.profile.action.EventIds, or do I return
EventIds.INVALID_MSG_CTX because the outgoing message context does not
contain the required child context ?

We define event ids this way because they are part of flow navigation,
at least that was the idea. But, it seems we probably will not handle
these missing context ids uniquely, instead we have a global
transition on 'Invalid*'. Maybe just an INVALID_CTX = "InvalidContext"
event ID ? I guess I am thinking that we probably will not change flow
navigation based on an invalid profile context vs invalid message
context.

Thoughts ?