|
Problem(Abstract) |
A DTD in a J2EE specification will be changed from SYSTEM
to PUBLIC by IBM® WebSphere® Application Server during install or
expansion., |
|
|
|
Cause |
The Application Server install does include these DTD
entries and will use the local copies prior to looking for the one listed.
However, a public DTD is needed to trigger this local search. This is why
WebSphere Application Server changes the DOCTYPE declaration from SYSTEM
DTD to PUBLIC DTD during install or when using the EARExpander
utility. |
|
|
Resolving the
problem |
A system DTD may be desired because of the inability of a
machine to access the Internet. This is inconsistent with the J2EE
specification, that requires that all valid J2EE application deployment
descriptors be contained in a PUBLIC doctype definition similar to the one
below:
<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD
J2EE
Application 1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd">
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|