You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Dain Sundstrom (JIRA)" <ji...@apache.org> on 2008/12/04 19:26:44 UTC
[jira] Created: (OPENEJB-968) XML system entities do not work
XML system entities do not work
--------------------------------
Key: OPENEJB-968
URL: https://issues.apache.org/jira/browse/OPENEJB-968
Project: OpenEJB
Issue Type: Bug
Components: configuration, tomcat
Affects Versions: 3.1, 3.0
Reporter: Dain Sundstrom
NamespaceFilter used to disable DTD downloading in JaxB also disables SYSTEM entity references in the XML. For example, the following will cause a null pointer exception in the tomcat integration:
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/j2ee/dtds/web-app_2.3.dtd" [
<!ENTITY inclusionFile SYSTEM "file.xml" >
]
>
<web-app>
&inclusionFile;
</web-app>
This problem exists in all JaxB parsing code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OPENEJB-968) XML system entities do not work
Posted by "Henri Gomez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715525#action_12715525 ]
Henri Gomez commented on OPENEJB-968:
-------------------------------------
A quick note about this.
XML include is supported with Tomcat 5.5 and 6.0 for some times.
It's a very usefull feature when you want to split a big application web.xml in smaller parts.
Regards
> XML system entities do not work
> --------------------------------
>
> Key: OPENEJB-968
> URL: https://issues.apache.org/jira/browse/OPENEJB-968
> Project: OpenEJB
> Issue Type: Bug
> Components: configuration, tomcat
> Affects Versions: 3.0, 3.1
> Reporter: Dain Sundstrom
>
> NamespaceFilter used to disable DTD downloading in JaxB also disables SYSTEM entity references in the XML. For example, the following will cause a null pointer exception in the tomcat integration:
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
> "http://java.sun.com/j2ee/dtds/web-app_2.3.dtd" [
> <!ENTITY inclusionFile SYSTEM "file.xml" >
> ]
> >
> <web-app>
> &inclusionFile;
> </web-app>
> This problem exists in all JaxB parsing code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.