[jbpm-issues] [JBoss JIRA] Resolved: (JBPM-1707) pageflow parsing is slow

[Alejandro Guizar (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBPM-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alejandro Guizar resolved JBPM-1707.
------------------------------------

    Resolution: Done


I made the jPDL parser read the pageflow schema from a local resource instead of the remote URL.
Plus I added several pageflow parsing tests to the existing XmlSchemaTest.

> pageflow parsing is slow
> ------------------------
>
>                 Key: JBPM-1707
>                 URL: https://jira.jboss.org/jira/browse/JBPM-1707
>             Project: JBoss jBPM
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Core Engine
>    Affects Versions: jBPM 3.2.3
>         Environment: Red Hat Enterprise Linux AS release 4 (Nahant Update 7)
> enterprise-installer-4.3.0.GA-1.ep1.8.jar
> jdk-1.5.0_16-fcs
>            Reporter: Alejandro Guizar
>            Assignee: Alejandro Guizar
>             Fix For: jBPM 3.3.0 CR1
>
>
> 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.

-- 
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