On Fri, Jun 20, 2008 at 1:37 PM, Paul Fremantle <[EMAIL PROTECTED]> wrote:
> > > > How this restart happens? > > module.init() > > > Here if the client start sending messages again then RM can start the RM > > Source and start working. > > > > But if this has only 15 orders and there are no messages to send then it > has > > to send a resume message. > > Here RM has implemented as a passive handler. I agree with you that this > is > > because of Axis2 design. Therefore RM can not work independently. > > I don't agree. Isn't this why we added module.init()? As soon as > Mercury is initialized it can begin recovery processes. > I think no. Here are some of the problems came to my mind. As I understood module init is to initialize some variables as in service or any other thing. Axis2 roughly have this kind of Layers when sending messages. Application Client Stub/Service Client Operation Client Axis Engine & Handlers (RM handler is here) Transport sender Always the Message Creation module engagement happens at the Application Client level and AxisService Operation creation happens at the Service Client/ Operational client level. Ideally at the handlers supposed to process soap messages. But RM does some resending and new message sending by coping the AxisService/Operation created at the Service Client level. The modules that should be engaged and hence the handler chain determine at the Application Client level. Lets say we try to initialize this in module.init() method. Module init() is called from the deployment engine. Normally Message sending should happen after deployment. And say this operation has engaged security. How can we create the AxisService/Operation? How do we know the Security policy? even how do we know security was engaged or not? How to start the Transport Listeners to get the messages? I Agree with you this is something related to Axis2 Design. But I am unable to think a way to over come these problems. thanks, Amila. > > Paul > > > > -- > Paul Fremantle > Co-Founder and CTO, WSO2 > Apache Synapse PMC Chair > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Amila Suriarachchi, WSO2 Inc.
