|
Problem |
In WebSphere® Application Server V4.0, the xmlconfig35.dtd
(shipped for compatibility), has no order requirements. However, the J2EE™
DTD for WebSphere Application Server V4.0, web-app_2_2.dtd, does have an
order requirement. Therefore, errors result during module installations
because J2EE web-app_2_2.dtd for Web modules are not in the correct
order. |
|
Cause |
In the J2EE DTD (Document Type Definition) for Web
applications, order does matter. |
|
Solution |
For the children within the <web-app> tag,
the J2EE DTD (J2EE web-app_2_2.dtd) has the following line for the
<web-app> tag:
<!ELEMENT web-app (icon?,
display-name?, description?, distributable?,context-param*, servlet*,
servlet-mapping*, session-config?, mime-mapping*, welcome-file-list?,
error-page*, taglib*, resource-ref*, security-constraint*, login-config?,
security-role*, env-entry*, ejb-ref*)> |
|
For comparison, the xmlconfig.dtd has the following line for the
<web-app> tag:
<!ELEMENT web-application
(model-full-name?,description?,document-root?,classpath?,error-page?,filter-list?,group-attributes?,auto-reload?,reload-interval?,enabled?,root-uri?,shared-context?,shared-context-jndi-name?,isclone?,session-config?,error-page-j2ee?,mime-mapping?,welcome-file-list?,taglib?,model-full-name?,servlet*)*> |
|
Notice that in the preceding xmlconfig.dtd there is an asterisk (
* ) at the end of the line, before the ending bracket ( >
). However, in the J2EE DTD, there is no asterisk at the end. This means
that in the xmlconfig.dtd, the order of tags can interchange
because of this asterisk, but the J2EE order has to follow the specified
order because the asterisk is not there.
J2EE DTDs for WebSphere Application Server V4.0 are located in the
following directory:
%WAS_ROOT%/deploytool\itp\plugins\com.ibm.etools.j2ee\dtds |
|
|
|
|
|
|
|