axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjiva Weerawarana (JIRA)" <>
Subject [jira] Commented: (AXIS2-371) AxisServiceBuilder should be using WOM not WSDL4J
Date Tue, 10 Jan 2006 05:19:20 GMT
    [ ] 

Sanjiva Weerawarana commented on AXIS2-371:

We discussed this at the hackathon and the consensus was that we need to plan to migrate to
Woden when they're ready. That is, WOM is not a strategic component for us but rather a tactical
one. When Woden is ready for us, then we will take a hard dependency on it like we have for
commons schema and policy. (That was also the convincing argument for removing the (unused)
support for Axis* implementing the WOM interfaces.)

Standardizing on WOM right now doesn't help us because every time we need some data we need
to copy it from the WSDL4J model to WOM and them to Axis*. So in effect we have to do a lot
of work which we know will have to go away.

BTW this was the objective of WOM from day 1. We started that because there was no WSDL version
independent WSDL representation around. Now Woden aims to become that. Its unfortunate that
they didn't take WOM and build on it but that's ok .. we can drop this and adopt Woden when
they come out (on top of StAX I might add .. otherwise we propogate the problem we now have
of requiring two XML parsers).


> AxisServiceBuilder should be using WOM not WSDL4J
> -------------------------------------------------
>          Key: AXIS2-371
>          URL:
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug
>     Reporter: Davanum Srinivas

> Can we please standarding the WOM as the single representation for holding information
from either WSDL1 or WSDL2? AxisServiceBuilder bypasses the WOM and uses wsdl4j directly.
> thanks,
> dims

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