leobaz2
asked on
XML namespace prefix appearing
We have recently migrated our JAX-RPC web services from Websphere 5.1 to 7.0. The web services have not changed during the migration and the WSDL files for both versions are identical. However, there is one difference in the web service response that is causing problems for the client. Apparently there is a namespace prefix (p909) added for the elements that originally did not have any prefix. This prefix is not in any of the WSDL files nor is it part of the request. It just appears out of nowhere.
Does anyone know why this prefix is being added and how to prevent it? Could it be a Websphere setting?
Thanks
Does anyone know why this prefix is being added and how to prevent it? Could it be a Websphere setting?
Thanks
I think the reasons why it has been added in 7.0 are given in this rather long but extensive article :-
http://www.ibm.com/developerworks/webservices/library/ws-tip-namespace.html
and it seems that by setting elementFormDefault="unqual ified" you might get the original back again.
Strictly speaking BOTH forms of the XML are perfectly legal and the client ought to be conform.
http://www.ibm.com/developerworks/webservices/library/ws-tip-namespace.html
and it seems that by setting elementFormDefault="unqual
Strictly speaking BOTH forms of the XML are perfectly legal and the client ought to be conform.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Open in new window