[JBoss JIRA] Created: (JBPM-2320) populate name attribute in Deployment while parsing xml file
by sri r (JIRA)
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
15 years, 5 months
[JBoss JIRA] Created: (JBPM-2354) fix excluded integration tests for test-db
by Tom Baeyens (JIRA)
fix excluded integration tests for test-db
------------------------------------------
Key: JBPM-2354
URL: https://jira.jboss.org/jira/browse/JBPM-2354
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Fix For: jBPM 4.0
in the test-db pom:
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<failIfNoTests>false</failIfNoTests>
<trimStackTrace>false</trimStackTrace>
<excludes>
<exclude>org/jbpm/test/activities/ForkJoinInSameTransactionTest.java</exclude>
<exclude>org/jbpm/test/execution/ConcurrentEndTest.java</exclude>
<exclude>org/jbpm/test/async/AsyncEndCombinationTest.java</exclude>
<exclude>reporting/SQLStmtTest.java</exclude>
</excludes>
</configuration>
</plugin>
--
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
15 years, 5 months
[JBoss JIRA] Created: (JBPM-2352) jPDL Schema definition needs some tweaks
by Phil Bingley (JIRA)
jPDL Schema definition needs some tweaks
----------------------------------------
Key: JBPM-2352
URL: https://jira.jboss.org/jira/browse/JBPM-2352
Project: JBoss jBPM
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: jBPM 4.0.CR1
Reporter: Phil Bingley
The jpdl schema needs to be updated to be in line with the features of the supported jpdl attributes.
Some specific differences are apparent in the task definitions where the schema does not support the form or due date attributes of a task. A complex type currently exists that covers the attributes but is not referenced.
There are likely to be other differences between the schema and supported jpdl so the whole thing may need reviewing.
--
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
15 years, 5 months