axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Asankha C. Perera (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AXIS2-1381) Need to enhance code generation from WSDL to support JMS extensions
Date Fri, 27 Feb 2009 03:48:01 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Asankha C. Perera resolved AXIS2-1381.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.4.1

This issue is very old.. AFAIK this is working with 1.4.x etc..please feel free to re-open
if there is any issue pending

> 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
>             Fix For: 1.4.1
>
>         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.


Mime
View raw message