axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksander Slominski (JIRA)" <>
Subject [jira] Commented: (AXIS2-185) reply to EPR for in two channel is hard coded to
Date Thu, 01 Sep 2005 10:54:25 GMT
    [ ] 

Aleksander Slominski commented on AXIS2-185:

For NAT, mobile clients, fire walled clients etc the solution is to provide external service
that will act as an endpoint that client can advertise in EPR ReplyTo/FaultTo. One such service
with pull capability (so clients can access their messages even when client is behind firewall)
is open-source free WS-MsgBox - both design and code available at

also for content dispatch i think that this can work very well with "ultra-lightweight" ESB
that is a pure-dispatcher as long as it supports HTTP/SOAP/RPC and async SOAP/WS-Addressing
- that is our experience and we wrote a paper about its design and testing it long-distance,
long-latency haul (USA-France):

> reply to EPR for in two channel is hard coded to
> ----------------------------------------------------------
>          Key: AXIS2-185
>          URL:
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug
>   Components: client-api
>     Reporter: Thilina Gunarathne

> I found the reply to EPR in non blocking two channel case  is harcoded to
> IMHO this will cause mal functioning of the axis2 server when it's deployed in some where
else other than the local machine....
> Pls correct me if I'm wrong...

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message