[
http://jira.codehaus.org/browse/XFIRE-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91553
]
Tim Morrow commented on XFIRE-893:
----------------------------------
Wow! I'm glad someone else figured this out. I almost gave up on my generated
client because of this issue.
FWIW I'm using the Maven2 plugin to invoke wsgen and generate the
JAXB2-annotated objects. It auto-generated a package-info.java file containing
this:
[EMAIL PROTECTED](namespace = "http://wherever.com";)}}
{{package com.wherever.ws.account;}}
It was the addition of {{elementFormDefault =
javax.xml.bind.annotation.XmlNsForm.QUALIFIED}} that fixed the problem for me.
package-info.java now looks like:
[EMAIL PROTECTED](namespace = "http://wherever.com",}}
{{ elementFormDefault =
javax.xml.bind.annotation.XmlNsForm.QUALIFIED)}}
{{package com.wherever.ws.account;}}
Of course, I had to jump through hoops to overwrite the generated
package-info.java with the new one.
Would you happen to know if it is possible to coerce the wsgen-generated
package-info.java to include that elementFormDefault ?
> The use of a Namespace without prefix on the inmessage results in wrong
> unmarshalling of jaxb type parameters
> -------------------------------------------------------------------------------------------------------------
>
> Key: XFIRE-893
> URL: http://jira.codehaus.org/browse/XFIRE-893
> Project: XFire
> Issue Type: Bug
> Components: JAXB 2.0
> Affects Versions: 1.2.4
> Environment: Server: org.codehaus.xfire.jaxb2.JaxbServiceFactory
> JAXB binding wrapped document style.
> Client: org.codehaus.xfire.spring.remoting.XFireClientFactoryBean
> Reporter: Tom Lambrechts
> Assigned To: Dan Diephouse
>
> JAXB types are not unmarshalled correct when using the xfire client.
> An empty object of the correct type is received, properties of the JAXB type
> are not deserialized.
> When using soapUI to call the Soap services the JAXB type is correctly
> unmarshalled.
> When looking to the message that is gooing over the wire a difference in the
> namespace of the inMessage is found.
> It seems that with a prefix for the namespace it works and without prefix not.
> (Working) SoapUI message:
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:foo="http://foo"; xmlns:myns="myNs">
> <soapenv:Header/>
> <soapenv:Body>
> <foo:helloWorld>
> <myns:myDTObject>
> <name>testName</name>
> </myns:myDTObject>
> </foo:helloWorld>
> </soapenv:Body>
> </soapenv:Envelope>
> (non Working) Message generated by the XFireClientFactoryBean:
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> <soap:Body>
> <helloWorld xmlns="http://foo";>
> <ns2:myDTObject xmlns:ns2="myNs">
> <name>testName</name>
> </ns2:myDTObject>
> </helloWorld>
> </soap:Body>
> </soap:Envelope>
--
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
