I totally agree with Paul , in this case Synapse is acting as SOAP node (intermediate SOAP node)
Paul Fremantle wrote: > I don't know enough about the mustUnderstand handling in Axis2, but it > seems to me that we might also want to identify a Synapse instance as > a given role. > > In other words, if we are acting as an intermediary, we may be > implementing a specific role, and not the "ultimate receiver". So we > only need to understand the headers that are targeted at our role or > the "next" role. > > Paul > > On 7/12/06, Asankha C. Perera <[EMAIL PROTECTED]> wrote: > >> Saminda >> >> Yes.. you are right, we need to be able to ask Axis2 to not validate >> mustunderstand headers.. we should get them to introduce a property for >> this and use it.. >> >> asankha >> >> Saminda Abeyruwan wrote: >> > Hi Devs, >> > >> > AxisEngine#receiver() always check for must understand header before >> > invoking the relevant message receiver. This would really give a hard >> > time in Synapse when we tried to implement qos support such as RM ect. >> > >> > Synapse has its own SynapseMessageReceiver(SMR) and SynapseDispatcher >> > and all the messages will be passed to this message receiver via >> > SynapseDispatcher. During this first phase we are not apply any QOS. >> > All QOS handles through mediators. Ex: RM will handles through >> > RMMediator(RMM). RMMediator is a part of Synapse. We use these >> > mediators to engage Axis2 modules hence supporting QOS. >> > >> > So in the case of RM all control messages and application messages >> > will be passed to RMM. Now if a messages comes with must understand >> > true, it will not pass to SMR at the first phase, because Axis2 engine >> > check for must understand and it will throw an exception. >> > >> > Intermediaries like Synapse would not need to understand must >> > understand headers and it should be upto the Service endpoint to >> > understand it. >> > >> > So IMHO, in order to user AxisEngine in SynapseEnvironment, we need a >> > switch to configure must understanding. >> > >> > >> > Thank you >> > >> > Saminda >> > >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > -- Thanks, Deepal ................................................................ ~Future is Open~ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
