aspose file tools
The moose likes Web Services and the fly likes addition of namespace to every element Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login


JavaRanch » Java Forums » Java » Web Services
Reply Bookmark "addition of namespace to every element" Watch "addition of namespace to every element" New topic
Author

addition of namespace to every element

chaitu sravs
Greenhorn

Joined: Oct 21, 2009
Posts: 11
Hi,

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?

Thanks,
Chinni
Ivan Krizsan
Bartender

Joined: Oct 04, 2006
Posts: 2194
Hi!
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:
@javax.xml.bind.annotation.XmlSchema (
elementFormDefault=XmlNsForm.UNQUALIFIED
...
)

<!-- XML Schema fragment -->
<schema
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:po="http://www.example.com/PO1"
elementFormDefault="unqualified">

If this is not the cause of the "problem", then I do not know what it may be.
Best wishes!
 
I agree. Here's the link: http://zeroturnaround.com/jrebel - it saves me about five hours per week
 
subject: addition of namespace to every element
 
Similar Threads
Mock exam question: SOAP doubt
Fault Query
SOAP doubts
When the default namespace is an empty string?
SOAP doubt: The Envelope element