[ 
http://jira.codehaus.org/browse/XFIRE-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100278
 ] 

Diana commented on XFIRE-914:
-----------------------------


I am using version 1.2.6 and encountered the same problem that XFire does not 
use the correct namespace on the wrapper elements in doc/literal wrapped style.

I tried the JAX-WS profile work around, but the problem remains.  

Is there any other configuration required?  like, does it requires to use the 
JAXWSServiceFactory as the service factory?  
What exactly does the JAX-WS profile create in additional to the regular 
generated classes?

Thanks.

> WSDL-First Service Uses Wrong Namespace in Wrapper Element
> ----------------------------------------------------------
>
>                 Key: XFIRE-914
>                 URL: http://jira.codehaus.org/browse/XFIRE-914
>             Project: XFire
>          Issue Type: Bug
>          Components: JAX-WS, JAXB 2.0
>    Affects Versions: 1.2.5
>            Reporter: Chris Moesel
>            Assignee: Dan Diephouse
>         Attachments: pizza_service_1.2.5.zip, pizza_service_1.2.5_FIXED.zip
>
>
> If a WSDL defines its schema types in a different namespace than the main 
> namespace of the WSDL, XFire will not use the correct namespace on the 
> wrapper elements in doc/literal wrapped style.  This is a new bug-- it worked 
> correctly in XFire 1.2.4.
> In the attached example, the response wrapper "OrderPizzaResponse" element 
> should have the namespace "http://mypizzico.com/pizza/types";, but instead has 
> the namespace "http://mypizzico.com/pizza";.
> The generated XFire client seems to have a similar bug in its request by 
> specifying the wrong namespace for the "Order Pizza" element.
> This can be demonstrated by running "mvn install" or "mvn test".  
> NOTE:  Although the TestCase does NOT fail, you can see in the logs (thanks 
> to the LoggingHandler) the incorrect XML being passed back and forth.  I 
> think the TestCase doesn't fail because the bug is in both the client and the 
> server.
> NOTE2:  You can see the correct XML by changing the dependencies in the 
> POM.xml to use XFire 1.2.4 instead.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to