Hi Shawn, Thanks for the ideas. Here are the clarifications.. (In the middle of the axis summit)
1. What does the "Message" look like? 2. Is WSA information burnt into the "Message" much like in Indigo? >>My idea is to provide something similar to Indigo, where the user is provided with an API to create a SOAP message. Accroding to the yesterday's discussion, we conclude that the MessageSender has two methods that the user (Client or the Call) can access. send(MessageCOntext) Send(SOAPEnvelope) So at the moment the Message is not provided, but will be a future addition. 3. What does the client programming model(s) look like, this proposal seems to be directed more at the internals, correct? >>Yes, it is focused to internals. We will provide the client programming model using Call API, yet the user (client) can access MessageSender directly. 4. Interesting use of the MessageContext, I'll have to think about that. What happened to the MessageBus concept? >>It seems like we don't need the MessageContext to be in the runnable mode after all. Engine will provide mechanism to pause and resume MessageContext. So if some handler want to release the current thread and continue with the current MessageContext then what the handler can do is, keep a reference to the current MessageContext and set the pause=true in the MessageContext. Then the engine will stop processing the rest of the handlers in the handler chain. Once the handler needs to start processing the message that it stops earlier, it can call, engine.resume(MessageContext) and the engine will continue with the stopped point. We may refine this part during the summit itself, have to see :) Last Q >>I agree with you regarding that, hope others are also with the same idea I will try to clarify this soon. Thanks, Jaliya -----Original Message----- From: Shawn Dahlen [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 29, 2005 10:11 AM To: Jaliya Ekanayake Cc: [email protected] Subject: Re: [Axis2]A Proposal for the messaged based Axis2 core Jaliya - Just got a chance to begin reading the proposal (noticed that it was slightly different than the document in the toy engine Srinath and you put together). I wish I could reply in full now, but alas I need to catch some shut eye. My work has granted me tomorrow and next day to collaborate, so I will spend tomorrow reviewing the proposal (and anything else you guys might put together at the conference). At first glance, I like the direction. A few questions. 1. What does the "Message" look like? 2. Is WSA information burnt into the "Message" much like in Indigo? 3. What does the client programming model(s) look like, this proposal seems to be directed more at the internals, correct? 4. Interesting use of the MessageContext, I'll have to think about that. What happened to the MessageBus concept? 5. At the messaging level, I do not believe a contract (ala WSDL) should be necessary. The contract between the parties is implicit (or the developers looked up a document / WSDL? to see the messages required for communication). The service model of course would generate the appropriate proxies based on the service descriptor (WSDL). Is the opinion of others at the conference? I do apologize for my inability to help share ideas quickly on this topic. Always tough trying to find that spare time :) - Shawn On Mon, 28 Mar 2005 09:39:55 +0600, Jaliya Ekanayake <[EMAIL PROTECTED]> wrote: > > > > Hi Shawn and All, > > > > I have suggested few changes to Axis2 core with the aim of supporting more > message based services. The proposal is sent in the attachment. > > I would be interested in hearing your thoughts. > > > > Thanks, > > > > Jaliya >
