On Nov 28, 2007 4:45 PM, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
> Hi devs, > I wonder why ODE does not have ws-addressing axis2 module engaged by > default.. I would also like know whether is there any particular > reasons for not engaging ws-addressing module in ODE, as I'm planning > to use ODE in production with ws-addressing module engaged... > > Even Axis2 ships with addressing engaged by default... It's just a > matter of having the WEB-INF/modules/addressing.mar , adding the > needed phases to axis2.xml and engaging globally using axis2.xml.. > In particularly ws-addressing support is needed if the workflow client > is doing a dual channel non-blocking invocation, which I think would > be a common scenario for a workflow engine.. > 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. 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. We're doing far more than we should to include WS-Addressing headers in ODE right now (see [1] and [2]). 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 >
