Hi Srinath and All, I have created a wiki to discuss the issues related to WS-* implementations on top of Axis2. IMHO, we need to have a good design for the above implementation to avoid future integration issues. Dreaming is good at this point I guess ;)
Currently the main design decisions that we need to come up with are; How o handle the protocol specific messages such as RequestSecurtiyToken and CreateSequenceRequest etc..? Where to interpret these messages? Is it at the handlers or in some operations? Please add your comments and thoughts. Thanks, Jaliya ----- Original Message ----- From: "Srinath Perera" <[EMAIL PROTECTED]> To: <[email protected]> Cc: <[email protected]> Sent: Monday, November 14, 2005 7:17 AM Subject: Re: [Axis2] Where to start the out messages in the handler flow? Hi Chamikara, Jaliiya; In axis2 archtecture point of view create sequence should be handled via "injecting a operation to the service". But I chat with Jaliya and it seems there are some complexities when we try to use the operation. e.g. 1) That way every operation should go till the end of the flow, e.g. Security message that request a session key would go though RM Handler ... but do not have RM Headers 2) All the Message (e.g. Create sequence Message) go though all the service level Handlers Since you are the guy wrote (and dream about ;) ) RM code, you know the problems that occurs. May be operations do not slove problem or can be improved. If we do not use operations injection we should scrap it from the architecture and generalized what ever the methodolgy use for RM to address this and add it to Axis2 core. I will try to have a look at the Sandesha2 code and think a way around it. Shall we create a wiki somewhere listing the isssues module archtecture should address. We need to add Ruchith to this discussion as well e.g. 1) RM Create Sequence/ Terminate Sequnce Messages should be proccessed, answered and the Handler chain should be stopped 2) Each RM/Security Handler should reject messages without RM/Security headers .... Thanks Srinath ation and > think that we need some definite way to do this at least for the modules > that we implement. > > > > Say, engine receive RM Specific Create message. We can interpret this > message either in RMInHandle or RMMessageReceiver. In addition modules may > have pre-dispatch handlers, in RM case we use one to eliminate duplicate > messages. > > > > If we interpret this from RMInHandler then we can stop that message from > going through all the other handlers. > > If we interpret this from RMMessageReceiver then this message will go > through the handlers deployed for the service. > > > > Now we need to send CreateSequenceResponse message from any of the above > two locations. > > If we send the response from RMInHandler we need to decide what is the > handler configuration for this message. Is it all the handlers deployed > for > that service or only the handlers that are after the RMPhase? (RMHandlers > deployed in RMPhase) > > > > If we send the CreateSequenceResponse from RMMessageReceiver then this > message will go through all the outgoing handlers deployed for that > service. > > > > IMHO we should interpret module specific messages using any handler in > > the > module and if there is a response that we need to send for that, it should > start from that phase. (not from the beginning of the handler flow) > > So in this way, phase n will affect only to phase n+1 as shown in the > attached diagram. > > > > We need to decide the same thing from the pre-dispatch handlers as well. > If one pre-dispatch handler want to send a response, then what are the > handlers that we use in the response path. > > > > Thoughts? > > > > Thanks, > > > > Jaliya > > > > > > > > > >
