[
https://issues.jboss.org/browse/WELD-988?page=com.atlassian.jira.plugin.s...
]
Ales Justin commented on WELD-988:
----------------------------------
-Dorg.jboss.weld.xml.disableValidating=true should disable xml parsing validation.
disableValidating = AccessController.doPrivileged(new
PrivilegedAction<Boolean>() {
public Boolean run() {
return
Boolean.getBoolean("org.jboss.weld.xml.disableValidating");
}
});
beans.xml schema validation should be configurable to turn if off
-----------------------------------------------------------------
Key: WELD-988
URL:
https://issues.jboss.org/browse/WELD-988
Project: Weld
Issue Type: Enhancement
Components: Bootstrap and Metamodel API
Affects Versions: 1.1.2.Final
Environment: Windows7 / weld 1.1.2 / tomcat6
Reporter: Manuel Hartl
Priority: Minor
- when you use the standard beans.xml schema location in your beans.xml (referencing
http://java.sun.com/xml/ns/javaee/beans_1_0.xsd) then WELD tries to look it up on the
internet.
- Currently (10.10.2011) oracle seems to have technical issues with their web servers and
returns an html error page when accessing the URL. this leads to a very long startup of
our weld applications because of url retrieval timeouts and in most cases even leads to a
stopping of the web application
-> in my opinion there should be configuration option (system property?) to turn
schema validation of beans.xml off.
for production environments this is often not neccessary and maybe even will result in a
speedup.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira