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 >
