Thanks Anne, The problem is that this is running under GT4 who (I think) have a back level/modified version of wsdl2java. Will raise a bug on the globus site.
Regards, John John Ibbotson CEng FIEE Grid Provenance Project, Emerging Technology Services Hursley Park, MP137, Winchester, Hants. SO21 2JN, UK Tel: +44 1962 815188 Mobile: +44 7739 876 196 Email: [EMAIL PROTECTED] Provenance: http://www.gridprovenance.org Technical Solutions to business problems that require innovation across IBM knowledge portfolio. "Anne Thomas Manes" <[EMAIL PROTECTED] To m> [email protected] cc 29/06/2006 16:28 Subject Re: wsdl2java and namespaces Please respond to [EMAIL PROTECTED] he.org Looks like a bug. On 6/29/06, John Ibbotson <[EMAIL PROTECTED]> wrote: I have some WSDL that imports some schemas. The schema includes elements that are typed to WS-Addressing EndpointReferenceType. For example: <xs:element name="messageSource" type="wsa:EndpointReferenceType"> <xs:annotation> <xs:documentation> The source of the message within the sender. </xs:documentation> </xs:annotation> </xs:element> The is a child of an element of type: <xs:complexType name="InteractionKey"> <xs:sequence> <xs:element ref="ps:messageSource" /> <xs:element ref="ps:messageSink" /> <xs:element ref="ps:interactionId" /> </xs:sequence> </xs:complexType> When I use wsdl2java to build the stubs and deploy the service, my test message get deserialized on the server. However, the wsa namespace is not defined. A section of the deserialized XML looks like: <ps:interactionKey xmlns:ps="http://www.pasoa.org/schemas/version024/PStruct.xsd";> <ps:interactionId> http://TestCase.commonservices/IdentifiedContentWithIPAandASA/urlAsserter </ps:interactionId> <ps:messageSource> <wsa:Address> http://messageSource.hursley.ibm.com:18080/axis/services/sourceApplication </wsa:Address> </ps:messageSource> <ps:messageSink> <wsa:Address> http://messageSink.hursley.ibm.com:18080/axis/services/sinkApplication </wsa:Address> </ps:messageSink> </ps:interactionKey> Note that the ps namespace is defined on the interactionKey element and I would have expected the wsa namespace to be defined on the messageSource and messageSink elements so that the child QNames are correct. Any idea what's going on ? Regards, John --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
