ser-root element in SOAP (input + output)

, ,
1

Hello everyone,

I am encountering a serious problem using auto-generated WSDL files, that I am using now to expose webservices.

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <SOAP-ENV:Header/>
   <SOAP-ENV:Body>
      <ser-root:creationTafResponse xmlns:ser-root="Mynamespace"/>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

The ser-root element appears when I call my webservice using soapUi.
I don’t need this element, and I am unable to validate data against the used xml schema with the ser-root element.
I am using 7.1.2 WM and the fix installed are:
IS_7-1-2_XA_Fix2
IS_7-1-2_Core_Fix10
IS_7-1-2_Flow_Fix2
IS_7-1-2_PubSub_Fix2
IS_7-1-2_SrvPrtcl_Fix8
IS_7-1-2_WebSvcsXML_Fix8
IS_7-1-2_PkgMgmt_Fix1
PRT_7-1-2_Fix1
TNS_7-1-2_DB_Fix3
TNS_7-1-2_Doc_Fix2
TNS_7-1-2_General_Fix2
TNS_7-1-2_Partner_Fix2

Any suggestions, is welcomed

Thanks

2

ser-root is not an element but rather a prefix for your namespace “Mynamespace”. Global elements, those appearing directly under the root element are required to be namespace qualified. This can be done either via an explicit prefix or a default namespace, the effect is the same. Prefixes just provide shorthand to reference namespaces, so a prefix should not cause a properly constructed xml schema to fail to validate.

3

Thank you for your reply griffima.
Indeed, for the element “creationTafResponse”, I had “tns” as namespace prefix, defined in the XSD. Consequently, the validation is rejected with an error that says: ser-root namespace not defined, or something like this.

I saw that the ser-root prefix is a bug that had been corrected with IS_7-1-2_WebSvcsXML_Fix2. Well, I have IS_7-1-2_WebSvcsXML_Fix8.
I want really make this prefix disappear and use my default namespace prefix, “tns”

Regards,

4

I believe the bug you are referring to is not prefix related but rather an additional element being added to the structure. The additional element is a root level element with an ser-root prefix but the bug was with the element being there not the prefix.

You have to be able to validate against any prefix because they are not revelant other than pointing to the proper namespace. since you can’t control what prefix a given client can use, it should not break validation regardless of the prefix as long as it resolves to the proper namespace.