XMLs contained by archives are parsed aggressively by deployers, resulting in unexpected
errors
-----------------------------------------------------------------------------------------------
Key: JBAS-7834
URL:
https://jira.jboss.org/jira/browse/JBAS-7834
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployers
Reporter: Marius Bogoevici
Assignee: Ales Justin
Take a working application (like a very basic war) and add a file ending in -hibernate.xml
(e.g. /WEB-INF/application-hibernate.xml) which references a schema which is unknown to
the Hibernate Deployer (or no schema).
A simple file containing this:
<broken/>
would do.
From this point on, the application will fail deploying consistently.
Unfortunately, application-hibernate.xml is not a reserved file name under JavaEE, so a
valid application may contain such files and fail to deploy. In such cases, the
application server should be more lenient and ignore those files.
Note 1: the problem may appear for other suffixes.
Note 2: the problem has been sporadically noticed in the Spring world, but it's not
necessarily a Spring-related issue (heavy usage of XML in Spring may trigger the problem
more consistently).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira