I say often caused by white space because people assume white space is always ignorable, but that's not the case here.
Call.invoke(Call.java:1812) This is often caused by a white space before the XML declaration, but it could be any text, like a dash or any character.
When using this XML Schema to validate the input XML document, the following error gets reported: ) as defined below has been used in the code examples to validate the input document.
XMLError Reporter.report Error(Unknown Source) at org.apache. XMLError Reporter.report Error(Unknown Source) at org.apache. XMLScanner.report Fatal Error(Unknown Source) at org.apache. XMLDocument Scanner Impl$Prolog Dispatcher.dispatch(Unknown Source) at org.apache. SOAPEnvelope(Message.java:435) at org.axis.security. WSDo All Receiver.invoke(WSDo All Receiver.java:114) at org.strategies. Simple Chain.invoke(Simple Chain.java:83) at org.client. Axis Client.invoke(Axis Client.java:198) at org.client. Added: Is that dash in front of your prolog part of the document?
Sun Microsystems Inc., at that time had just formalized the Java Community Process (JCP), and the first version of JAXP (JSR-05) was made public in early 2000, supported by industry majors like (in chronological order) BEA Systems, Fujitsu Limited, Hewlett-Packard, IBM, Netscape Communications, Oracle, and Sun Microsystems, Inc.
JAXP 1.0, then called Java API for XML Parsing, was a box office hit in the developer community, because of the pluggability layer provided by JAXP; that's what the essence of JAXP is.
Namespaces have been introduced to XML after the first specification of XML had received the official W3C Recommendation status.
This is the reason why (most of the) XML parser implementations do not support XML Namespaces by default, to handle the validation of XML documents with namespaces correctly it is therefore necessary to configure the underlying parsers to provide support for XML Namespaces.