Hi, > It's not engaged because we've had issues with it in past versions of Axis2 > (1.1 IIRC). Basically it wasn't playing nice with our stateful exchange > headers. Oh... I suspected there must have been an issue... To find it out is one of the reasons for sending the earlier mail... Anyway I'm still not familiar with ODE stateful exchange mechanism. Have to explore more..
>We haven't had time to test it again with Axis2 1.3 to make sure it > now works properly. So if you're willing to try it and make sure that there > are no problem when exchanging messages with those headers, you're more than > welcome. Simple external services invocations worked without an issue.. I would definitely check for our use cases... But I don't think I know ODE enough to ensure that it works correctly with all of ODE.. I'll give it a shot and let you all know.. >We're doing far more than we should to include WS-Addressing > headers in ODE right now (see [1] and [2]). Looks like I did not convey my issue clearly... My use case is a asynchronous dual channel client (using Axis2 non-blocking client with a separate listener [1]) invoking a process deployed in ODE... This case does not work if the service exposed by ODE does not have addressing engaged.. Also what are the addressing versions are supported by ODE if it's different from Axis2 addressing... thanks, Thilina > > Cheers, > Matthieu > > [1] > http://svn.apache.org/repos/asf/ode/branches/APACHE_ODE_1.1/axis2/src/main/java/org/apache/ode/axis2/hooks/SessionInHandler.java > [2] > http://svn.apache.org/repos/asf/ode/branches/APACHE_ODE_1.1/axis2/src/main/java/org/apache/ode/axis2/hooks/SessionOutHandler.java > > > > > > > Just my 0.02 $ :)... > > > > thanks, > > Thilina > > > > -- > > Thilina Gunarathne - http://thilinag.blogspot.com > > > -- Thilina Gunarathne - http://thilinag.blogspot.com
