Hi Alek; mm ..They got a Handler Resolver ..but I doubt to which extent they will be a repalcement for phase rules. We should look in to it case by case.
I am ok if we have a special JAX-WS relase or something .. but main Sandesha should run on Axis2 ..my gut feeling is otherwise we might not use Axis2 features to full potential Thanks Srinath On 12/6/05, Aleksander Slominski <[EMAIL PROTECTED]> wrote: > Srinath Perera wrote: > > >I list few main archtectural concerns .. there may be more > > > >1) Context hairachy > >2) Phase rules > >3) Operation injection > >4) Pausing the execution and restarting it > >5) possible dependancies on the messaging > > > >I do not belive it is easy to provide a mapping, and strongly > >desagree making Sandesha too work on non Axis2 interface. We design > >Axis2 to provide very high level support for SOAP extensions .. they > >go in to detail unlikly any spec would provide > > > > > i ma be totally wrong but it seems to me that of all those five aspects > (4) is critical - everything else can be done with JAXWS or any other > handler based framework ... (4) requires ability to "persist" execution > context of a chain of handlers (hopefully in a file or a database to > make the process _really_ reliable) and then resume the chain if > handlers execution from then "freeze" point. > > thanks, > > alek > > >On 12/5/05, Glynn, Eoghan <[EMAIL PROTECTED]> wrote: > > > > > >>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] > >> > >> > >> > >> > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > -- > The best way to predict the future is to invent it - Alan Kay > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
