SOAPFactory that is shipped with JDK1.6.x seems to add the prefix:namspace declaration to each child element in the soap envelope, for the actual elements of the payload. The namespace is declared at the envelope level and I thought just a prefix needs to be added to the actual usage of the elements.
Yes, this is not posing any problems, however, just got curious because even when those attributes are removed, the message still successfuly gets processed-
any hints on how to disable it?
Make sure that the attribute elementFormDefault is not set to "qualified" in the XML schema declaration for the payload.
The default value is "unqualified" (no elementFormDefault attribute is present).
If you do code-first development, you will want to use the @XmlSchema annotation on the packet level. Example from the API documentation:
<!-- XML Schema fragment -->
If this is not the cause of the "problem", then I do not know what it may be.