October 2010 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2958) Timer should refer to the business calendar used at the time of creation

by Toshiya Kobayashi (JIRA)

Timer should refer to the business calendar used at the time of creation ------------------------------------------------------------------------ Key: JBPM-2958 URL: https://jira.jboss.org/browse/JBPM-2958 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 3.2.9 Reporter: Toshiya Kobayashi Assignee: Alejandro Guizar Fix For: jBPM 3.2.10 Assuming you want to use different business calendars by loading different jbpm.cfg.xmls; When you use a Timer, a scheduler service thread will set repeatDate to the timer using BusinessCalendar which is associated with given jbpmContext. The jbpmContext comes from default jbpm.cfg.xml (jbpm.esb/jbpm.cfg.xml). Also the BusinessCalendar field is static. So you cannot switch business calendars for each Timer in the scheduler service thread. The timer should be able to acquire the business calendar which was used at the time of Timer creation. -- 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

13 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-2866) update structure of documentation project

by Darrin Mison (JIRA)

update structure of documentation project ----------------------------------------- Key: JBPM-2866 URL: https://jira.jboss.org/browse/JBPM-2866 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.8 Reporter: Darrin Mison Assignee: Darrin Mison Fix For: jBPM 3.2.8 We need to update the structure of the jBPM 3 docs so the docbook is consumable in both jDocBook and Publican. -- 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

13 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPM-2834) Conditional transition cannot be considered as a default one

by Martin Vecera (JIRA)

Conditional transition cannot be considered as a default one ------------------------------------------------------------ Key: JBPM-2834 URL: https://jira.jboss.org/jira/browse/JBPM-2834 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 3.2.8, jBPM 3.2.9 Environment: SOA-P 4.3.CP03 ER1 Reporter: Martin Vecera The documentation reads: ==== The contents of the condition element is a jPDL expression that should evaluate to a boolean. A decision takes the first transition (as ordered in the processdefinition.xml) for which the expression resolves to true. If none of the conditions resolve to true, the default leaving transition (== the first one) will be taken. ==== If I have only a conditional transition in a node (hence the first one) it is not used as the default leaving transition. Process definition to simulate the behaviour: ==== <?xml version="1.0" encoding="UTF-8"?> <process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="processDefinition3"> <start-state name="start"> <transition to="node1"></transition> </start-state> <node name="node1" async="true"> <transition to="node2" condition="#{AAA == null}"></transition> </node> <node name="node2"> <transition to="end1"></transition> </node> <end-state name="end1"></end-state> </process-definition> ==== Exception being thrown on signaling process's token: 10:16:33,629 ERROR [JobExecutorThread] job execution failure org.jbpm.JbpmException: transition is null at org.jbpm.graph.def.Node.leave(Node.java:449) at org.jbpm.graph.def.Node.leave(Node.java:430) at org.jbpm.graph.def.Node.execute(Node.java:421) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:173) at org.jbpm.graph.def.Node_$$_javassist_81.execute(Node_$$_javassist_81.java) at org.jbpm.job.ExecuteNodeJob.execute(ExecuteNodeJob.java:24) at org.jbpm.job.executor.JobExecutorThread.executeJob(JobExecutorThread.java:192) at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:66) JBPM-Console says: Error signalling token: An exception of type "org.jbpm.JbpmException" was thrown. The message is: Node(node1) has no default transition -- 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

13 years, 10 months

2
9
0 / 0

[JBoss JIRA] Created: (JBPM-2957) Drools dependencies from the main pom.xml

by eric schabell (JIRA)

Drools dependencies from the main pom.xml ----------------------------------------- Key: JBPM-2957 URL: https://jira.jboss.org/browse/JBPM-2957 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 5.0 Alpha Environment: jBPM 5.0 alpha Reporter: eric schabell Priority: Minor Fix For: jBPM 5.0 Beta The main pom.xml can be cleaned up to either remove or modularize the Drools deps out/into separate module so that it is an optional component for user that want to use jBPM5 without rules components. -- 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

13 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-2505) ProcessInstanceQuery - no way to search by process variables

by Joao Fonseca (JIRA)

ProcessInstanceQuery - no way to search by process variables ------------------------------------------------------------ Key: JBPM-2505 URL: https://jira.jboss.org/jira/browse/JBPM-2505 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0.0 Alpha1, jBPM 4.0.0 Alpha2, jBPM 4.0.0.Beta1, jBPM 4.0.0.Beta2, jBPM 4.0.CR1, jBPM 4.0, jBPM 4.x, jBPM 4.2, jBPM 4.1 Reporter: Joao Fonseca Currently, there's no way of searching for process instances that contain variables set to a given value. Sometimes, there's no way of assigning a process instance key when starting a process, so we need to search for processes using values stored in some of the variables... -- 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

13 years, 11 months

8
13
0 / 0

[JBoss JIRA] Created: (JBPM-2687) Document how to install the web-console with a newbie tutorial under jboss, tomcat notably

by Alexandre Navarro (JIRA)

Document how to install the web-console with a newbie tutorial under jboss, tomcat notably ------------------------------------------------------------------------------------------ Key: JBPM-2687 URL: https://jira.jboss.org/jira/browse/JBPM-2687 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Console Affects Versions: jBPM 4.2 Reporter: Alexandre Navarro Fix For: GWT Console 1.0.x Document how to install the web-console with a newbie tutorial under jboss, tomcat notably. I tried to install it during 3 hours and at the end, it does not work and I gave up. It is very frustated not to have a good documentation to install webconsole on jboss, tomcat or some others appservers. -- 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

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1924) Improved participant UI

by Thomas Diesler (JIRA)

Improved participant UI ----------------------- Key: JBPM-1924 URL: https://jira.jboss.org/jira/browse/JBPM-1924 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Console Reporter: Thomas Diesler Priority: Critical * Participant UI: A production-ready inbox & task-form display solution, with a full-set of form controls, editable CSS, etc. Two Goldman CTOs felt this was the absolute highest priority to resolve ASAP (I received the same feedback from them in August). They have already made attempts to modify the current Admin Console (JSF/Gravel-based) and intend to tweak the GWT-based console. However, the Eclipse-tooling Visual Task Form Designer is relatively weak, it doesn't allow me to easily express things like Drop-Down list, numeric input only, check-box, pop-up calendar for date, etc. This UI is a process participants (e.g. clerk in the office) primary UI, their view of the world, they see all their own and their team's tasks (note: the current console shows all tasks for everybody, not just the logged in user). The current UI only uses inputText (single-line edits). The JBoss logo needs to be customizable (I want it to say Goldman in that upper left corner) I'll attempt to mark up some changes to the current console so you get a feel for their specific feedback. It should be noted that Amentra also felt this was a mandatory feature before we can call ourselves a BPM product. No Java Coding, just pointing & clicking. -- 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

13 years, 11 months

6
10
0 / 0

[JBoss JIRA] Created: (JBPM-2141) Use same deployment archive suffixes across target containers

by Heiko Braun (JIRA)

Use same deployment archive suffixes across target containers ------------------------------------------------------------- Key: JBPM-2141 URL: https://jira.jboss.org/jira/browse/JBPM-2141 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Integration Reporter: Heiko Braun Assignee: Heiko Braun In AS 5.0.0 we need to use the .jar suffix for deployments. This should become the same as in AS 4.2.x, when moving to 5.0.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

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-2827) Run gwt-console on JBoss AS 4.x and 5.x

by Kris Verlaenen (JIRA)

Run gwt-console on JBoss AS 4.x and 5.x --------------------------------------- Key: JBPM-2827 URL: https://jira.jboss.org/jira/browse/JBPM-2827 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kris Verlaenen How can we support deployment on both JBoss AS 4.x and 5.x? Because for 4.x I need to exclude a lot of jars because they otherwise conflict with the ones by default on the server classpath (hibernate, jta, jpa, javassist). Having an issue with javassist in this case as well, as the version you are bundling in the gwt-console-server-drools.war conflicts with the javassist + hibernate on server classpath. Is there any chance this could be marked as provided? These jars don't seem to be there in AS 5.x by default, so in that case the war should contain all jars? -- 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

13 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2965) jBPM4 Alpha start.demo ant task fails

by eric schabell (JIRA)

jBPM4 Alpha start.demo ant task fails -------------------------------------- Key: JBPM-2965 URL: https://jira.jboss.org/browse/JBPM-2965 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 5.0 Alpha Environment: intel x08_64, fedora 13, sun jdk 1.6_16 Reporter: eric schabell Fix For: jBPM 5.0 Alpha After running ant install.demo (which takes fooooooreeeeevvvvveerrrrrrr !) I try to run a simple 'ant start.demo' and get first a pop-up from eclipse: JVM terminated. Exit code=13 /usr/bin/java -Xms40m -Xmx384m -XX:MaxPermSize=256m -jar /opt/Download/JBPM/jbpm5/jbpm-installer/eclipse//plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar -os linux -ws gtk -arch x86 -showsplash -launcher /opt/Download/JBPM/jbpm5/jbpm-installer/eclipse/eclipse -name Eclipse --launcher.library /opt/Download/JBPM/jbpm5/jbpm-installer/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.1.1.R36x_v20100810/eclipse_1309.so -startup /opt/Download/JBPM/jbpm5/jbpm-installer/eclipse//plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar -exitdata 8c0005 -data .//workspace -plugincustomization ./eclipse.preferences.ini -vm /usr/bin/java -vmargs -Xms40m -Xmx384m -XX:MaxPermSize=256m -jar /opt/Download/JBPM/jbpm5/jbpm-installer/eclipse//plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar Then at the start.humantask I get: start.human.task: [java] Failed to instantiate SLF4J LoggerFactory [java] Reported exception: [java] java.lang.NoClassDefFoundError: org.slf4j.impl.StaticLoggerBinder [java] at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121) [java] at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111) [java] at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268) [java] at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241) [java] at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254) [java] at org.hibernate.cfg.Configuration.<clinit>(Configuration.java:151) [java] at java.lang.Class.initializeClass(libgcj.so.10) [java] at java.lang.Class.initializeClass(libgcj.so.10) [java] at org.hibernate.ejb.Ejb3Configuration.<clinit>(Ejb3Configuration.java:107) [java] at java.lang.Class.initializeClass(libgcj.so.10) [java] at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:124) [java] at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52) [java] at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34) [java] at org.jbpm.DemoTaskService.main(Unknown Source) [java] Exception in thread "main" java.lang.NoClassDefFoundError: org.slf4j.impl.StaticLoggerBinder [java] at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121) [java] at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111) [java] at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268) [java] at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241) [java] at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254) [java] at org.hibernate.cfg.Configuration.<clinit>(Configuration.java:151) [java] at java.lang.Class.initializeClass(libgcj.so.10) [java] at java.lang.Class.initializeClass(libgcj.so.10) [java] at org.hibernate.ejb.Ejb3Configuration.<clinit>(Ejb3Configuration.java:107) [java] at java.lang.Class.initializeClass(libgcj.so.10) [java] at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:124) [java] at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52) [java] at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34) [java] at org.jbpm.DemoTaskService.main(Unknown Source) [java] Java Result: 1 start.demo: BUILD SUCCESSFUL Total time: 30 seconds This is all done with the latest build (yesterday, 20 Oct 2010) installer from hudson. -- 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

13 years, 11 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues October 2010