-
Bug
-
Resolution: Done
-
Major
-
jBPM 3.2.3
-
None
On a RHEL machine, while deploying a seam based ear, which contains 13 pageflow definitions, the parsing of these 13 pageflow files takes more than 34 minutes .
The culprit seems to be the usage of the original systemId (http://jboss.com/products/seam/pageflow-2.0.xsd) in the org.jbpm.jdpl.xml.JpdlParser$JpdlEntityResolver class, as this
apparently results in slow internet lookups:
log.debug("original systemId as input source");
inputSource = new InputSource(systemId);
Using a null InputSource:
inputSource = new InputSource((InputStream)null);
brings the parsing time down to less than 1 second.
Of course it would be better to actually pass in a reference to the local pageflow-2.0.xsd file, which is inside the jboss-seam.jar.
- blocks
-
JBPAPP-3520 pageflow-2.1.xsd resolved from internet rather than from classpath
- Closed
- is duplicated by
-
JBPM-1710 Provide local reference for Seam pageflows to pageflow-2.0.xsd
- Resolved
- is related to
-
JBPM-2774 parsing of pageflow causes to require internet connection
- Resolved
- relates to
-
JBAS-7659 Timeouts in org.jboss.test.deployers.seam.test.Seam*ExampleUnitTestCase
- Closed