You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Davanum Srinivas (JIRA)" <ji...@apache.org> on 2007/09/28 14:54:15 UTC
[jira] Updated: (AXIS2-1381) Need to enhance code generation from
WSDL to support JMS extensions
[ https://issues.apache.org/jira/browse/AXIS2-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS2-1381:
------------------------------------
Assignee: (was: Davanum Srinivas)
> Need to enhance code generation from WSDL to support JMS extensions
> -------------------------------------------------------------------
>
> Key: AXIS2-1381
> URL: https://issues.apache.org/jira/browse/AXIS2-1381
> Project: Axis 2.0 (Axis2)
> Issue Type: New Feature
> Components: codegen
> Affects Versions: 1.1
> Environment: All
> Reporter: Brennan Spies
> Attachments: files.zip, patch.zip
>
>
> 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: http://ws.apache.org/wsif/providers/wsdl_extensions/jms_extension.html.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org