[
https://jira.jboss.org/browse/JBPM-2774?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar commented on JBPM-2774:
----------------------------------------
Implemented option (c) to give integrators full control over the location of the schema
resources in the classpath, thus realizing Pete Muir's suggestion of
"externaliz[ing resources] so that it is up to the integrating product to
define". Automatic loading as described in option (a), while convenient, might pose a
threat as it can be exploited to have the engine load resources of arbitrary content and
size.
It should be noted the default jBPM configuration references only the Pageflow 2.2 schema
because, in JAXP 1.2, "it is illegal to have two schemas that share the same
namespace" (cf. section 3.5).
parsing of pageflow causes to require internet connection
---------------------------------------------------------
Key: JBPM-2774
URL:
https://jira.jboss.org/browse/JBPM-2774
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.5.SP5
Reporter: Marek Novotny
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
JpdlParser has hard coded XSDs for local parsing instead of regular expression or
wildcards in the file name of pageflow xsd.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira