ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthieu Riou" <matthieu.r...@gmail.com>
Subject Re: Ode client API
Date Mon, 20 Mar 2006 20:10:31 GMT
+1 as well. I'm pretty happy with the distinction that Maciej described.

On 3/20/06, Sanjiva Weerawarana <sanjiva@opensource.lk> wrote:
> On Mon, 2006-03-20 at 09:01 -0800, Paul Brown wrote:
> >
> > I'm on the same page with this -- it makes sense to keep the engine as
> > small as possible and use existing packages to layer on orthogonal
> > functionality (like SOAP handling), but I'd also like to be sure that
> > we maintain a reasonable level of purity and isolation -- using AXIS
> > as the default SOAP protocol stack shouldn't preclude the clear
> > integration of something like XFire or an application server's JAX-WS
> > stack by another user.  Just the same, the core engine should be have
> > the absolute minimum number of library dependencies to maximize the
> > possibilities for integrating it into other runtimes.
>
> +1; since the services exposed by the BPEL process are simply WSDL
> described services, I don't see why there'd be a need to have a deep
> coupling to Axis stuff for the sake of invoking into a process.
>
> Sanjiva.
>
>

Mime
View raw message