axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rich Scheuerle (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AXIS2-4565) JAX-WS: Fails to examine the @RequestWrapper targetNamespace. Also needs to tolerate wsimport NS->PKG mapping algorithm
Date Wed, 25 Nov 2009 22:04:39 GMT

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

Rich Scheuerle resolved AXIS2-4565.
-----------------------------------

    Resolution: Fixed

> JAX-WS: Fails to examine the @RequestWrapper targetNamespace.   Also needs to tolerate
wsimport NS->PKG mapping algorithm
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-4565
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4565
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: jaxws
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Background:
> The JAX-WS runtime examines the web service annotations and packages to determine which
packages should be included in the JAXBContext.
> The JAX-WS runtime uses the namespace->package algorithm defined by the JAXB Specification
when it needs to convert namespace references into packages.
> -----------------------
> Problem 1:
> The JAX-WS runtime is not examining the targentnamespace parameter on the @RequestWrapper
and @ResponseWrapper annotations.  Thus it might neglect to include a package in the JAXBContext.
> (Note that this is rare.  The JAX-WS runtime looks at the package referenced in the className
parameter.  Thus problems only occur if the wrapper element and the wrapper complexType are
defined in two separate schemas...which is rare)
> ------------------------
> Problem 2:
> Many applications are built using the wsimport tool.  This tool apparently has a slightly
different namespace->package mapping algorithm.   For example, the JAXB specification (rule
8b) indicates if a namespace word collides with a java keyword, then a _ is appended .   
> JAXB Rule: "urn://my.interface.com"  becomes "com.interface_.my".    
> The wsimport tool prepends the underscore.
> WSIMPORT Rule: "urn://my.interface.com"  becomes "com._interface.my".   
> --------------------------
> Proposed Solution:
> For 1) The engine will be changed to examine the @RequestWrapper and @ResponseWrapper
targetnamespace parameters.
> For 2) The engine will be changed to tolerate both rules.

-- 
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