Re: [cinjug-users] DTD path problem.

["Edward Sumerfield" <esumerfd@xxxxxxxxxxx>]

The default url is an HTTP url that causes a net request. In the case of struts-config to

http://jakarta.apache.org/struts/dtds/struts-config_1_1.dtd

While this will usually work it does mean that your production system is dependant on connectivity to the Jakarta site. Others depend on the w3c site and so on. While these sites very rarely go down, I think its a good idea to eliminate all external dependencies from you production apps.

If you unplug your network cable and start your web server it will not start. It follows that if the Jakarta network crashes, your web server will not start.

Since DTDs are only checked at load time it does make this dependency a small one.

From a development perspective, I can sit outside in the sunshine on a disconnected laptop and still run my web server. Some might say this is more important that the production app issue.

----- Original Message -----

From: James Carman

To: Edward Sumerfield ; CinJug

Sent: Monday, June 16, 2003 12:01 PM

Subject: Re: [cinjug-users] DTD path problem.

This has never been a problem for me.  I just use the default URL for it.  When struts loads the file, it knows what DTD to use.

----- Original Message -----

From: Edward Sumerfield

To: CinJug

Sent: Monday, June 16, 2003 12:07 PM

Subject: [cinjug-users] DTD path problem.

To avoid net requests during XML parser loads I have changed all the DTD paths to local files with a little ant task to replace the "DOCROOT" with the expected deployment directory. This allows me to configure the deployment directory at build time so each developer can drive their own deployment with their own build.properties file.

 

 <!DOCTYPE struts-config PUBLIC
          "-//Apache Software Foundation//DTD Struts Configuration 1.1//EN"
          "file://DOCROOT/WEB-INF/struts-config_1_1.dtd">

 

Except, the SunOne App Server changes the deploy directory each time the product is deployed, putting the docroot into a numbered directory that changes so there no way to know the directory prior to deployment.

 

Anyone have any strategies to accomplish net independence and install directory isolation at the same time?

 

Ed