Hi Sanjiva, I'd be interested in hearing what you see as the crucial Sandesha2/Axis2 touch-points that don't have direct JAXWS analogues, just to get a sense of what would be involved in layering it over Celtix.
I should declare my interest at this point ... I'm a colleague of Andrea's on the Celtix project. Regards, Eoghan > -----Original Message----- > From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED] > Sent: 04 December 2005 23:39 > To: Chamikara Jayalath > Cc: Smyth, Andrea; [email protected] > Subject: Re: Use of Sandesha in Celtix? > > > On Fri, 2005-12-02 at 08:57 +0600, Chamikara Jayalath wrote: > > Hi Andrea, > > > > Many parts of Sandesha2 (e.g. Handlers, Invoker, Sender) have strong > > dependencies on Axis2. So you will have to do some work to get them > > ported. I think this is the same for Sandesha1. > > Axis2 was carefully designed to allow and support the existence of > components such as Sandesha2 which extend Axis2. As such, > Sandesha2 has > to depend on Axis2 concepts in order to do the best possible RM > implementation for Axis2. If we were to have Sandesha2 access Axis2 > behind some standard interfaces, we'd lose all of those > capabilities and > instead would have to use a much more muted/weak interface. > That doesn't > make any sense from Sandesha2's point of view because it > can't maximize > the capabilities of the SOAP stack its providing RM for. > > Now, if someone wants to provide a layer over Sandesha2 that makes it > JAX-WS compliant that's fine of course. However, it is not fine IMO to > make Sandesha2 directly JAX-WS dependent instead of Axis2 dependent > because then we'd be losing quality not gaining it. > > Sanjiva. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
