axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brennan Spies (JIRA)" <>
Subject [jira] Commented: (AXIS2-1381) Need to enhance code generation from WSDL to support JMS extensions
Date Fri, 27 Oct 2006 00:35:17 GMT
    [ ] 
Brennan Spies commented on AXIS2-1381:

I'm putting the finishing touches on the patch, and am getting ready to test it. A few issues
I've run across...

1. In revamping the org.apache.axis2.description.AxisServiceOM class to handle different protocol
bindings (so that JMS can be included), I've realized that SMTP and TCP have no standard uri
for <soap:binding transport="uri"/>. What to do in this case? Put in a dummy URI, similar
to the example in the WSDL 1.1 spec? Or exclude the 'transport' attribute?

2. WSDL4J's ExtensionRegistry was not really designed with reusability in mind. So I've added
a class that will register all of the appropriate WSDL 1.1 extensibility elements and the
JMS stuff. In order to get this to work, we also need a WSDLFactory impl that will reference
it, and some mechanism for WSDL4J discovering this impl. System property (javax.wsdl.WSDLFactory=...)
would be the easiest, but has two issues: 1) there doesn't seem to be a natural "choke point"
to add this line of code in Axis 2, so it would have to be in multiple places 2) In managed
environments, having a System property set might cause issues with other apps that are sharing
the JVM. The other approach is to put a properties file under META-INF/services/ for each
jar that uses WSDL4J's WSDLFactory. Which approach do you prefer?


> Need to enhance code generation from WSDL to support JMS extensions
> -------------------------------------------------------------------
>                 Key: AXIS2-1381
>                 URL:
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: New Feature
>          Components: codegen
>    Affects Versions: 1.1
>         Environment: All
>            Reporter: Brennan Spies
>         Assigned To: Davanum Srinivas
>         Attachments:
> Currently, there is no support for JMS WSDL extensions in Axis 2.0. Code generation for
a WSDL service with JMS bindings succeeds, but the client stub is missing a default JMS endpoint
reference, and transport elements and appropriate properties from <jms:address> should
be placed into the generated services.xml file.
> To do this, the appropriate extension elements for JMS in the WSDL must be recognized.
This requires adding them to WSDL4J's extensibility mechanism. The appropriate implementations
already exist in the Apache WSIF project:

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:


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

View raw message