axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srinath Perera (JIRA)" <>
Subject [jira] Updated: (AXIS2-1658) Unable to send a result message to a host different from the caller (it was possible)
Date Wed, 13 Jun 2007 18:39:26 GMT


Srinath Perera updated AXIS2-1658:

    Priority: Minor  (was: Blocker)

This is very specific senario, I personally belive you should be use Inout Async with ReplyTo
between A <-> B and B<->C which simplify things lot. On other words when someone
invoke a Web service, that Web service may invoke other web services, but it does not affect
the first invocation in any way. You can use Async with replyTo avoid timeouts. Anyway I am
bringing down the priority

> Unable to send a result message to a host different from the caller (it was possible)
> -------------------------------------------------------------------------------------
>                 Key: AXIS2-1658
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: kernel
>         Environment: axis2 1.1 rc2 niglty 08/11/2006
>            Reporter: Michele Mazzucco
>            Assignee: Deepal Jayasinghe
>            Priority: Minor
>         Attachments: axis2_logs.log
> I'm not able to forward a result to an EPR different from where the original message
comes from. 
> I've node A (client) which sends a message to node B (in-only with addressing informations),
which in turn sends a different message to a
> node C.
> When the result is ready, node C sends it to node B, which (I'm simplifying) should send
the result (using a *new* ServiceClient object) to node A.
> Until now I've been using a RawXMLINOutMessageReceiver message receiver, while the method
signature was
> void result(OMElement)
> and it worked fine using options.setRelationships + the A's EPR. However now I get an
AxisFault exception saying an operation with the signature OMElement result(OMElement) does
not exist.
> I've tried to change the message receiver to in-only, but if I do this the forward operation
is ignored (see also the RawXMLInOnlyMessageReceiver java doc): it looks like the ServiceClient
sends the result to A, but it's never received.
> This issue has been discussed several times (i.e. [1, 2]) on this
> mailing list and the result was that it's actually possible.
> [1]
> [2]

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message