[Solution] DocumentBuilderFactory, Serialization, and WL 8.1 SP 2

Question

<pre>
Hello All!
I finally have gotten my web services to work properly. All of my serialization
woes were caused by my using the javax.xml.parsers.DocumentBuilderFactory and
NOT setting the following options:
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
factory.setValidating(false);
factory.setNamespaceAware(true);
Yup. That's it. I saw this being done in one of the tech support people's examples:
private Document getDocumentWithWL(String resourceName)
throws Exception
weblogic.apache.xerces.parsers.DOMParser parser = new weblogic.apache.xerces.parsers.DOMParser();
parser.setFeature(
"http://apache.org/xml/features/dom/defer-node-expansion",
false );
parser.setFeature( "http://xml.org/sax/features/validation",
false);
parser.setFeature( "http://xml.org/sax/features/namespaces",
true);
parser.setFeature( "http://apache.org/xml/features/validation/schema",
true);
parser.parse(new org.xml.sax.InputSource(this.getClass().getClassLoader().getResourceAsStream(resourceName)));
return(parser.getDocument());
and decided to write the analog to this using the DocumentBuilderFactory:
private Document getDocumentWithDB(String resourceName)
throws Exception
DocumentBuilder db = null;
DocumentBuilderFactory fac = DocumentBuilderFactory.newInstance();
// Set params
fac.setValidating(false);
fac.setNamespaceAware(true);
db = fac.newDocumentBuilder();
Document doc = db.parse(this.getClass().getClassLoader().getResourceAsStream(resourceName));
return(doc);
Now my doc/lit web services are able to marshall data between the service and
client. I have to still use the DII dynamic proxy client method for invoking
the web service (SOAPElement!! grr).
Thanks to all who helped diagnose this problem. You know that you have this problem
when you see errors about "Local name of attribute can not be null ...." coming
out of weblogic's XML serialization code.
Hope this helps someone else out there
-- jake
</pre>

Answer 1

Well basically that means there was a partial message that came in over a socket, and the server waited 60 seconds for the rest of the message, but it never arrived.
Was the server, or a client under heavy load? Did you notice any response time problems?
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/