I have a running JAX-WS webservice which already has some working endpoints. Now I\'m having the following issue:
I\'m having two different SOAP Requests here and I don\
When using a prefix bound to a namespace like in
92623-15853588
0
0
then only the element getMoldDataHistory
is put into the specified namespace. The reason is that the syntax xmlns:his="..."
only declares the prefix. This then must used at all elements that you want to be in the specified namespace. In this code snippet, the only element is getMoldDataHistory
.
Using the xmlns="..."
syntax like in
92623-15853588
0
0
not only declares the namespace, but also puts the associated element and all child elements into this namespace.
Conclusion: These two XML snippets are not semantically equivalent.
If there was such a thing as an "expanded element name" syntax, then these XML snippets would look like ...
First one:
<{http://history.production.soap.webservices.product.company.at/}getMoldDataHistory>
<{}machineId>92623-15853588{}machineId>
<{}start>0{}start>
<{}end>0{}end>
{http://history.production.soap.webservices.product.company.at/}getMoldDataHistory>
Second one:
<{http://history.production.soap.webservices.product.company.at/}getMoldDataHistory>
<{http://history.production.soap.webservices.product.company.at/}machineId>92623-15853588{http://history.production.soap.webservices.product.company.at/}machineId>
<{http://history.production.soap.webservices.product.company.at/}start>0{http://history.production.soap.webservices.product.company.at/}start>
<{http://history.production.soap.webservices.product.company.at/}end>0<{/http://history.production.soap.webservices.product.company.at/}end>
{http://history.production.soap.webservices.product.company.at/}getMoldDataHistory>