Comment #2 on issue 2620 by [email protected]: Guaranteed Ordering Of Sip Event Dispatch
http://code.google.com/p/mobicents/issues/detail?id=2620
I believe that the order of invocation is dictated by the transaction layer of the SIP protocol. The transaction layer of SIP protocol defines a finite state machine for each element of the protocol which makes clear the set of rules and behavior that should be followed.
CTF provides an abstract layer over JSR289 in order to promote a simplified programming model. Using CTF annotations you don't need to follow the JSR289 programming model in order to process SIP requests/responses, the developer can just register a method to receive events for SIP requests or responses and process them accordingly, for example : public mySuperDuperRegistrationMethod (@Observes @Register SipServletRequest req)
