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 Tue, 24 Oct 2006 05:33:17 GMT
    [ ] 
Brennan Spies commented on AXIS2-1381:

For the WSIF, that's essentially what I've already done. What I was referring to was that
there is one method within the the JMS extensions that is out of date with the current version
of WSDL4J; also, there is a custom logger (org.apache.wsif.logging.Trc), which is a bit out
of place in Axis 2.0 (replace with commons-logging). So the classes need a little updating.

OK, I'll get started on the patch. Should I just attach to this JIRA when I'm done?

> 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