[JBoss JIRA] Created: (JBPM-1093) Allow more than one action to be executed when entering a page node
by Matthew Lieder (JIRA)
Allow more than one action to be executed when entering a page node
-------------------------------------------------------------------
Key: JBPM-1093
URL: http://jira.jboss.com/jira/browse/JBPM-1093
Project: JBoss jBPM
Issue Type: Feature Request
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Reporter: Matthew Lieder
Assigned To: Tom Baeyens
Only the first <action> is executed when multiple actions are children of <page> and <start-page> elements in a jPDL pageflow. It would be greatly appreciated if the logic could be changed so that all <action> elements are executed (like they are when children of <transition> elements).
Example:
<page name="page1" view-id="/page1.xhtml">
<action expression="#{someMethodThatIsExecuted} />
<action expression="#{someMethodThatIsNotExecuted} />
<transition name="save" to="terminate">
<action expression="#{someMethodThatIsExecuted} />
<action expression="#{someMethodThatIsExecuted} />
</transition>
</page>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 3 months
[JBoss JIRA] Created: (JBPM-1827) Investigate example test failures against Sybase
by Thomas Diesler (JIRA)
Investigate example test failures against Sybase
------------------------------------------------
Key: JBPM-1827
URL: https://jira.jboss.org/jira/browse/JBPM-1827
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Productization
Reporter: Thomas Diesler
Fix For: jBPM 3.3.1 GA
<exclude>org/jbpm/db/DeleteProcessInstanceDbTest.java</exclude>
<exclude>org/jbpm/graph/exe/SubProcessPlusConcurrencyDbTest.java</exclude>
<exclude>org/jbpm/jbpm1072/JBPM1072Test.java</exclude>
<exclude>org/jbpm/jbpm1755/JBPM1755Test.java</exclude>
<exclude>org/jbpm/jbpm983/JBPM983Test.java</exclude>
<exclude>org/jbpm/job/executor/JobExecutorDbTest.java</exclude>
<exclude>org/jbpm/optimisticlocking/LockingTest.java</exclude>
<exclude>org/jbpm/scheduler/exe/UnsafeSessionUsageTest.java</exclude>
<exclude>org/jbpm/seam/JobExecutorCustomizationTest.java</exclude>
--
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
17 years, 3 months
[JBoss JIRA] Created: (JBPM-1913) Support JBoss AS 5.0 for JSF Console
by Ronald van Kuijk (JIRA)
Support JBoss AS 5.0 for JSF Console
------------------------------------
Key: JBPM-1913
URL: https://jira.jboss.org/jira/browse/JBPM-1913
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Console
Affects Versions: jBPM 3.3.0 GA
Environment: JBoss AS 5.0.0.GA, OpenJDK 1.6.0, Fedora 10
Reporter: Ronald van Kuijk
Priority: Trivial
Fix For: jBPM 3.3.2 GA
The jsf console does not work in JBoss AS 5.0.0.GA.
Seam had a similar issue, JBSEAM-3066, and they solved it by including jsf-facelets-1.1.15.B1.jar instead of 1.1.14. I tried it locally and it solves the problem for me to and everything still works on JBoss AS 4.2.x.
Any objections to changing the dependency for 3.3.2? Or are there little objections to still include it in 3.3.1?
--
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
17 years, 3 months
[JBoss JIRA] Created: (JBPM-1893) reorganised resources
by Tom Baeyens (JIRA)
reorganised resources
---------------------
Key: JBPM-1893
URL: https://jira.jboss.org/jira/browse/JBPM-1893
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Tom Baeyens
Fix For: jBPM 4.0.0 Alpha1
previously, some resources were scanned over the complete classpath. like org/jbpm/pvm/pvm.hibernate.mappings.xml and org/jbpm/pvm/pvm.wire.bindings.xml
no more deep scanning is done. this leads to confusing duplicate entries in the all-in-one-jar file. and also it leads to duplicate entries in the zip file that combines all the resources of these multiple sub projects into a single source directory. then zip asks:"do you want to overwrite?"...
the solution is that all resource files will all be named individually and no deep scanning will be done.
to keep the easy user extensibility, a user resource file will be looked for and included automatically if present.
--
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
17 years, 4 months