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

Morten Wilken commented on XFIRE-941:
-------------------------------------

Incidently, this problem manifests itself when we use the wsdl to generate .net 
clients and call the xfire service.

> Namespace error when using doc/lit wrapped
> ------------------------------------------
>
>                 Key: XFIRE-941
>                 URL: http://jira.codehaus.org/browse/XFIRE-941
>             Project: XFire
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.5
>         Environment: windows xp
>            Reporter: Morten Wilken
>            Assignee: Dan Diephouse
>         Attachments: service.infrastruktur.ping.wsdl, 
> wrapper.infrastruktur.ping.xsd
>
>
> We have a problem regarding namespaces, when using doc/lit wrapped 
> webservices.
> We have 3 files to each webservice:
> 1. service.wsdl (with namespace="service"), containing all wsdl specific 
> information ,bindings etc.
> 2. wrapper.xsd (with namespace="wrapper") which defines elements for all 
> requests and responeses.
> 3. entity.xsd (with namespace="entity") which defines the actual data of the 
> operations.
> We then generate the code using wsgen and all is well.
> What we experience is that the SOAP response, which has as the root element a 
> response defined in the wrapper namespace actually is being generated in the 
> service namespace.
> so for an operation we have:
> Service:
> ...
>       <wsdl:message name="hentInterval">
>               <wsdl:part name="parameters" element="kalender:hentInterval" />
>       </wsdl:message>
>       <wsdl:message name="hentIntervalResponse">
>               <wsdl:part name="parameters" 
> element="kalender:hentIntervalResponse" />
>       </wsdl:message>
> (kalender points to the wrapper.xsd)
> ...
> Wrapper:
>       <xs:element name="hentInterval">
>               <xs:complexType>
>                       <xs:sequence>
>                               <xs:element name="startDato" type="xs:dateTime" 
> />
>                               <xs:element name="slutDato" type="xs:dateTime" 
> />
>                       </xs:sequence>
>               </xs:complexType>
>       </xs:element>
>       <xs:element name="hentIntervalResponse">
>               <xs:complexType>
>                       <xs:sequence>
>                               <xs:element ref="kalender:kalenderDagListe" />
>                       </xs:sequence>
>               </xs:complexType>
>       </xs:element>
> (here kalender references entities in the entity.xsd)
> This produces as a response:
> <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>
>       <hentBankdagIAarResponse 
> xmlns="http://service.letpension.dk/infrastruktur/kalender_v1";>
>          <kalenderDag 
> xmlns="http://entity.letpension.dk/infrastruktur/kalender_v1";>
>             <dato>1900-01-02T00:00:00.0+00:09</dato>
>  ...
>  
> Where we would expect it to respond:
> <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>
>       <hentBankdagIAarResponse 
> xmlns="http://wrapper.letpension.dk/infrastruktur/kalender_v1";>
>          <kalenderDag 
> xmlns="http://entity.letpension.dk/infrastruktur/kalender_v1";>
>             <dato>1900-01-02T00:00:00.0+00:09</dato>
>  
> Am i correct in assuming this is a bug in xfire?

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