ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fLozano <fjlozanoaco...@gmail.com>
Subject Re: Axis2 local transport
Date Wed, 15 Aug 2007 14:26:55 GMT


Ok so Ode can call a local process without using axis2. Does this mean that
the invocation for the local process is not a web service invocation in the
sense of it being wrapped like a soap message?

In other words, is the invocation for the local process wrapped like a
regular web service invocation?

If it isn't, then this invocation doesn't require any soap unwrapping or xml
parsing right?

Matthieu Riou-5 wrote:
> Actually for processes you don't need to do anything now. If from process
> A
> you try to invoke process B and ODE finds that process B is deployed
> locally
> it will invoke it directly, without hitting any communication layer. So
> process to process communication has almost no latency cost.
> For service invocation, I would think it's probably only tweaking the
> axis2.xml bundled with ODE and your endpoints. The local transport sender
> is
> already configured, so adding a local transport receiver and using proper
> endpoint addresses (starting with local:// I believe) should work. I
> haven't
> tried it myself but it looks like everything is there. You might want to
> ask
> the Axis2 people as well to make sure there's not another gotcha but ODE
> is
> just like any other local web service here.
> Cheers,
> Matthieu
> On 8/13/07, Paul Brown <paulrbrown@gmail.com> wrote:
>> On 8/13/07, Kristoffer Sjögren <stoffe@gmail.com> wrote:
>> > That is how I interpret it, and that's what i want to do. Or more
>> > exact, i want to invoke services from ode, services which are in the
>> > same JVM, and if possible, the same classloader so that a
>> > call-by-reference is possible.
>> I haven't looked at the plumbing since the IL refactor, but it used to
>> be possible to directly connect a BPEL process to another BPEL process
>> within the Ode container and without hitting the wire.  This is still
>> a "hop" in the sense that it involves persistence (to the extent that
>> the process does) and serialization of state, but it doesn't involve
>> serializing and deserializing, e.g., to SOAP.
>> If you truly want in-band invocation and don't have long-running
>> operations, why not consider XPath extension functions?  I'll let
>> other Ode'ers steer you away if I'm not thinking clearly, but that's
>> one way to get what you're after.
>> -- Paul

View this message in context: http://www.nabble.com/Axis2-local-transport-tf4252925.html#a12163139
Sent from the Apache Ode User mailing list archive at Nabble.com.

View raw message