axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Weston, Toby" <>
Subject RE: [Axis2] Asynchronous client calls to asynchronous BPEL proces s
Date Fri, 21 Apr 2006 12:42:22 GMT
Thanks for the note Yves,

I've got things working with synchronous - setting the SOAPAction (good
spot) but am having trouble with asynchronous services :(

BPEL seems to use "initiate" and "onResult" as the two actions, so I use
"initial" to make the, er, initial call. Axis2 seems to create the WS-A
headers for me, I just don't think BPEL calls back to it... Maybe its
something to do with Axis2 not recognising a callback with a SOAPAction set
of "onResult"? BPEL claims to have "skipped" the callback in the

Its a real headache!


Yves Langisch wrote:
> Toby,
> I'm able to call a synchronous BPEL process (also Oracle BPEL process
> manager) from Axis2 without any problems. One problem I came across
> was that you always have to specify a SOAPAction. Oracle doesn't
> support incoming requests w/o SOAPAction. Since I had an already
> existing WSDL with operations w/o SOAPAction which I had to provide
> as a BPEL process this was a problem. That's where my Axis2 service
> come into play. Now I call my Axis2 service according to my WSDL w/o
> SOAPAction and proxy it with the appropriate SOAPAction to the BPEL
> process.       
> Yves
> On Fri, 2006-04-21 at 08:49 +0100, Weston, Toby wrote:
>> Hope you don't mind the 'bump' folks but I'd be interested in *any*
>> comments on calling BPEL based services from Axis2.
>> Thanks :)
>> Weston, Toby wrote:
>>> Hi Folks,
>>> Has anyone successfully made a call to a asynchronous BPEL process?
>>> I'm using Axis 0.95 and Oracle BPEL process manager but it doesn't
>>> seem to work as expected. I'm using a blocking dual client from
>>> within a servlet, it creates the WS-addressing headers fine and
>>> makes the request getting the acknowledgment, but the BPEL flow just
>>> tells me that the callback to the client was "skipped", it didn't
>>> fail (at the BPEL end) but the client never receives the callback.
>>> The temporary service __ANONYMOUS_SERVICE__/__OPERATION_OUT_IN__ on
>>> port 6060 is operational (I can't think of a way to intercept it the
>>> message with TCPMonitor for example, though).
>>> I tried against two different versions of BPEL (latest on OC4J and
>>> slightly earlier version on Weblogic) and they behave slightly
>>> different (both don't work). The client works against the Axis ECHO
>>> sample so I'm wondering if there is a known problem with BPEL?
>>> As a side point, the Axis ECHO sample that uses WS-addressing; is
>>> this really a synchronous process? I mean to say that the WSDL looks
>>> synchronous and non-Axis clients seem to be able to call it in a
>>> synchronous way... how is this testing a dual client? Are there any
>>> public asynchronous services (non-BPEL!) that I can test against?
>>> Thanks in advance for any pointers or suggestions :)
>>> All the best,
>>> Toby

View raw message