[jbpm-issues] [JBoss JIRA] Commented: (JBPM-2320) populate name attribute in Deployment while parsing xml file
[
https://jira.jboss.org/jira/browse/JBPM-2320?page=com.atlassian.jira.plug...
]
sridhar r commented on JBPM-2320:
---------------------------------
We are planning to have a directory which houses all the process definitions. As multiple
teams will be using our jbpm application, we would like to force them to follow the
convention of having file name same as name attribute. So that we not only verify version
while updating process definition, we would also like to check if the file they are
uploading is same as file name.
populate name attribute in Deployment while parsing xml file
------------------------------------------------------------
Key: JBPM-2320
URL: https://jira.jboss.org/jira/browse/JBPM-2320
Project: JBoss jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.0.CR1
Reporter: sri r
Hi,
In jBPM 3.x, we had a way to check if a version of process defintiion is already deployed
by checking it against the name (name attribute from process definition.xml).
With jBPM 4.x, deployment.addResourceFromClasspath(fileName) populates DeploymentImpl
object with name attribute being null in it..
As a result, only way for end applications is to work around by comparing filename for
ex.
Instead if addResourceFromClasspath populates name attribute, we can directly query
based on it.
Noticed that jbpm 4 loads the deployment info into a hashmap with filename, lob object
into resource service.
resources.put(name, lob);
--
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