In my program there is a similar mistake 
I add in package-info:

@javax.xml.bind.annotation.XmlSchema(namespace =
"http://phoneBook.remote.ice.usl.cv.ua";, elementFormDefault =
javax.xml.bind.annotation.XmlNsForm.QUALIFIED)
package test;

but problem not solved.



JIRA [EMAIL PROTECTED] wrote:
> 
> 
>     [
> http://jira.codehaus.org/browse/XFIRE-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89372
> ] 
> 
> Tom Lambrechts commented on XFIRE-893:
> --------------------------------------
> 
> Adding package-info with a namespace solves this problem:
> 
> @javax.xml.bind.annotation.XmlSchema(namespace="http://book.xfiretraining.envoisolutions.com";,
>                                      elementFormDefault =
> javax.xml.bind.annotation.XmlNsForm.QUALIFIED)
> package com.envoisolutions.xfiretraining.book;
> 
> 
> 
>> 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
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/-jira--Created%3A-%28XFIRE-893%29-The-use-of-a-Namespace-without-prefix-on-the-inmessage-results-in-wrong-unmarshalling-of-jaxb-type-parameters-tf3300609.html#a9352540
Sent from the XFire - Dev mailing list archive at Nabble.com.


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

    http://xircles.codehaus.org/manage_email

Reply via email to