WAR files (Tomcat) and deployment descriptor

Question

Hello,
I am currently writing a small utility to package a web application for Jakarta Tomcat as a .war file.
I have a functional version that imports the deployment descriptor web.xml, but I'd like to make it possible for the user to edit or create from scratch that file. I use the DOM API to make a logical model of my web.xml, but the parser won't accept the external dtd definition :
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
Here is my parser :
private void parse(File in) {
try {
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
factory.setNamespaceAware(true);
factory.setValidating(true);
DocumentBuilder builder = factory.newDocumentBuilder();
document = builder.parse(in); (((*)))
catch (...)
}//parse
---------------------------------------------It seems I have no further controls on DocumentBuilder and DocumentBuilderFactory.
The builder.parse call generates this exception :
java.net.NoRouteToHostException: Operation timed out: no further information
at java.net.PlainSocketImpl.socketConnect(Native Method)
at org.apache.crimson.parser.Resolver.resolveEntity(Resolver.java:389)The problem seems to be located in DOM's DefaultHandler entity resolver, but I don't ee clearly what to do.
Thanks for helping.

Answer 1

Hi,
I already tried every combination of settings with
DocumentBuilderFactory.setNamespaceAware
DocumentBuilderFactory.setValidating
DocumentBuilderFactory.setCoalescing
DocumentBuilderFactory.ExpandEntityReferencesI had the same result. Here is the exact dump :
java.net.NoRouteToHostException: Operation timed out: no further information
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:125)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:112)
        at java.net.Socket.<init>(Socket.java:273)
        at java.net.Socket.<init>(Socket.java:100)
        at sun.net.NetworkClient.doConnect(NetworkClient.java:50)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:331)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:517)
        at sun.net.www.http.HttpClient.<init>(HttpClient.java:267)
        at sun.net.www.http.HttpClient.<init>(HttpClient.java:277)
        at sun.net.www.http.HttpClient.New(HttpClient.java:289)
        at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection
.java:379)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon
nection.java:472)
        at org.apache.crimson.parser.Resolver.resolveEntity(Resolver.java:389)
        at org.apache.crimson.parser.ExternalEntity.getInputSource(ExternalEntit
y.java:88)
        at org.apache.crimson.parser.Parser2.pushReader(Parser2.java:2986)
        at org.apache.crimson.parser.Parser2.externalParameterEntity(Parser2.jav
a:2721)
        at org.apache.crimson.parser.Parser2.maybeDoctypeDecl(Parser2.java:1154)
        at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:488)
        at org.apache.crimson.parser.Parser2.parse(Parser2.java:304)
        at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
        at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl
.java:179)
        at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:161)
        at DOMView.main(DOMView.java:96)This shows that the entity resolver tries to access the distant DTD, so I tried to implement myself the EntityResolver interface, but I didn't well understood
what to do with that InputStream it has to return.