June 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBPM-719) Create ws dir, resources, build.xml under the project root

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-719?page=all ] Thomas Diesler updated JBPM-719: -------------------------------- Assignee: (was: Ronald van Kuijk) > Create ws dir, resources, build.xml under the project root > ---------------------------------------------------------- > > Key: JBPM-719 > URL: http://jira.jboss.com/jira/browse/JBPM-719 > Project: JBoss jBPM > Issue Type: Feature Request > Environment: n/a > Reporter: Ronald van Kuijk > Priority: Minor > Original Estimate: 2 hours > Time Spent: 2 days, 4 hours > Remaining Estimate: 2 hours > > Create <jbpm.home>/ws and all relevant subdirs according to what already exists (take console as an example) > Create a build.xml file according to what already exists (take console as an example) > Initially add jbossws from <jboss.home> if set, see other issue for getting jbossws in the repository -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-569) improve EL expression examples in the user guide

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-569?page=all ] Thomas Diesler updated JBPM-569: -------------------------------- Assignee: (was: Ronald van Kuijk) > improve EL expression examples in the user guide > ------------------------------------------------ > > Key: JBPM-569 > URL: http://jira.jboss.com/jira/browse/JBPM-569 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-718) Add a webservice frontend to jBPM

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-718?page=all ] Thomas Diesler updated JBPM-718: -------------------------------- Assignee: (was: Ronald van Kuijk) > Add a webservice frontend to jBPM > --------------------------------- > > Key: JBPM-718 > URL: http://jira.jboss.com/jira/browse/JBPM-718 > Project: JBoss jBPM > Issue Type: Feature Request > Environment: n/a > Reporter: Ronald van Kuijk > Priority: Minor > > A webservice frontend is an interesting feature. A schema has to be designed, ws toolkit choosen (jbossws 1.0.2GA?) subdir created in the build, ant files etc... etc...etc... > Subtasks will be created for this. Anyone to jump in, feel free -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1079) Put jBPM jPDL releases into the JBoss Maven Repo

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1079?page=all ] Thomas Diesler updated JBPM-1079: --------------------------------- Assignee: (was: Tom Baeyens) > Put jBPM jPDL releases into the JBoss Maven Repo > ------------------------------------------------ > > Key: JBPM-1079 > URL: http://jira.jboss.com/jira/browse/JBPM-1079 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Affects Versions: jBPM jPDL 3.2.2 > Reporter: Matthew Lieder > > You have v3.2.1 in repository.jboss.org/maven2, but not v3.2.2. -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-255) I18N for the webapp

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-255?page=all ] Thomas Diesler updated JBPM-255: -------------------------------- Assignee: (was: Ronald van Kuijk) > I18N for the webapp > ------------------- > > Key: JBPM-255 > URL: http://jira.jboss.com/jira/browse/JBPM-255 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Web Interface > Reporter: Ronald van Kuijk > Priority: Optional > Original Estimate: 1 day > Remaining Estimate: 1 day > > Not everybody speaks dutch -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1062) Serializable filter should be last in default jbpm.varmapping.xml

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1062?page=all ] Thomas Diesler updated JBPM-1062: --------------------------------- Assignee: (was: Tom Baeyens) > Serializable filter should be last in default jbpm.varmapping.xml > ----------------------------------------------------------------- > > Key: JBPM-1062 > URL: http://jira.jboss.com/jira/browse/JBPM-1062 > Project: JBoss jBPM > Issue Type: Bug > Affects Versions: jBPM jPDL 3.2.2 > Reporter: Marcus Schmidke > > In 3.2.2 there are again some entries behind the Serializable Type mapping (see #JBPM-748). I think, Serializable should always be last. -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1075) org.hibernate.hql.ast.QuerySyntaxException in org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(List actorIds)

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1075?page=all ] Thomas Diesler updated JBPM-1075: --------------------------------- Assignee: (was: Tom Baeyens) > org.hibernate.hql.ast.QuerySyntaxException in org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(List actorIds) > ---------------------------------------------------------------------------------------------------------------- > > Key: JBPM-1075 > URL: http://jira.jboss.com/jira/browse/JBPM-1075 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM jPDL 3.2, jBPM 3.1.4, jBPM jPDL 3.2 beta 2, jBPM jPDL 3.2.1, jBPM jPDL 3.2.2 > Environment: java version "1.5.0_04" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05) > Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode, sharing) > Reporter: Jo Geraerts > Attachments: patch > > > I encountered this bug when I was developping an application with jboss seam. At some point there was a Actor with no group ids. The processInstanceList component will invoke the getGroupTaskList(List actorIds) with a List with 0 entries. > So we end up in org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(actorIds) with the same List ( with 0 entries) > I get this Exception: > 10:43:42,265 ERROR [TaskMgmtSession] org.hibernate.hql.ast.QuerySyntaxException: unexpected end of s > ubtree [ > select distinct ti > from org.jbpm.taskmgmt.exe.PooledActor pooledActor > join pooledActor.taskInstances ti > where pooledActor.actorId in ( ) > and ti.actorId is null > and ti.isSuspended != true > and ti.isOpen = true > ] -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1050) Missing security-role element in jbpm-console web.xml

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1050?page=all ] Thomas Diesler updated JBPM-1050: --------------------------------- Assignee: (was: Tom Baeyens) > Missing security-role element in jbpm-console web.xml > ----------------------------------------------------- > > Key: JBPM-1050 > URL: http://jira.jboss.com/jira/browse/JBPM-1050 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Affects Versions: jBPM jPDL 3.2.1 > Reporter: James Baxter > Priority: Optional > > The jbpm-console uses a security role named 'user' in a security-constraint but does not declare the role in a security-role element. This produces the following console output: > [code] > INFO [ContextConfig] WARNING: Security role name user used in an <auth-constraint> without being defined in a <security-role> > [/code] > This issue can be fixed by adding the following to the web.xml: > [code] > <security-role> > <role-name>user</role-name> > </security-role> > [/code] -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-831) avoid using default id generator

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-831?page=all ] Thomas Diesler updated JBPM-831: -------------------------------- Assignee: (was: Tom Baeyens) > avoid using default id generator > -------------------------------- > > Key: JBPM-831 > URL: http://jira.jboss.com/jira/browse/JBPM-831 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.1.2 > Environment: The problem is common to all platform. > Issue is identifed on Oracle 9.1 specifically. > Reporter: Wenbo Zhu > > The Id generator should be named explicitly, which is currently not. > <id name="id" column="ID_"><generator class="native" /></id> > This will introdcue issue when jbpm schema has to be updated (dropped, e.g.) as the db may be shared with other apps that uses default hibernate id generator too .. in case of Oracle, it's "hibernate_sequence". > - Wenbo -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1032) task-assign-events are sometimes fired when group assignment is performed

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1032?page=all ] Thomas Diesler updated JBPM-1032: --------------------------------- Assignee: (was: Tom Baeyens) > task-assign-events are sometimes fired when group assignment is performed > ------------------------------------------------------------------------- > > Key: JBPM-1032 > URL: http://jira.jboss.com/jira/browse/JBPM-1032 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM jPDL 3.2.1 > Reporter: Karsten Dello > > A "task-assingn"-event is sometimes fired, if only group assignment (setting pooledActors) is performed. This always happens when a swimlane is in use which specifies pooled-actors (junit test 1). > On the other hand, when the pooled-actors are expressed via an assignment-element as an child element of a task (junit test 2), the event is not fired. > From my point of view the engine should either: > a) not fire an task-assign-event in case of group assignments at all > b) fire it consequently at all group assignments events > c) fire a different event > Ronald suggested in the forum thread (link above) to introduce a seperate event "task-group-assign" in case a task gets assigned to a group. In my opinion this would be the best solution to this problem. > public void testTaskAssignIsFiredWithSwimlaneGroupAssignment() { > ProcessDefinition processDefinition = ProcessDefinition.parseXmlString( > "<process-definition name=\"someprocessxyz\">" + > > " <event type=\"task-assign\">" + > " <script>System.out.println(\"task-assign-event fired!\");" + > " executionContext.setVariable(\"task-assign-event-has-fired\",Boolean.TRUE);</script>"+ > " </event>"+ > " <start-state>" + > " <transition to='a' />" + > " </start-state>" + > > " <swimlane name='swimlane22'>"+ > " <assignment pooled-actors='jan,nina'/>"+ > " </swimlane>"+ > " <task-node name='a'>" + > " <task name='sometask' swimlane='swimlane22'/>" + > " <transition to='end'/>"+ > " </task-node>"+ > > " <end-state name='end' />" + > > "</process-definition>" > ); > ProcessInstance processInstance = new ProcessInstance(processDefinition); > Token token = processInstance.getRootToken(); > > processInstance.signal(); > Object o=processInstance.getContextInstance().getVariable("task-assign-event-has-fired"); > assertEquals(Boolean.TRUE, o); > > } > public void testTaskAssignIsNOTFiredWithSwimlaneGroupAssignment() { > ProcessDefinition processDefinition = ProcessDefinition.parseXmlString( > "<process-definition name=\"someprocessxyz\">" + > > " <event type=\"task-assign\">" + > " <script>System.out.println(\"task-assign-event fired!\")"+ > " executionContext.setVariable(\"task-assign-event-has-fired\",Boolean.TRUE);</script>"+ > " </event>"+ > " <start-state>" + > " <transition to='a' />" + > " </start-state>" + > > " <task-node name='a'>" + > " <task name='sometask'>" + > " <assignment pooled-actors='jan,nina'/>"+ > " </task>"+ > " <transition to='end'/>"+ > " </task-node>"+ > > " <end-state name='end' />" + > > "</process-definition>" > ); > ProcessInstance processInstance = new ProcessInstance(processDefinition); > Token token = processInstance.getRootToken(); > processInstance.signal(); > > Object o=processInstance.getContextInstance().getVariable("task-assign-event-has-fired"); > assertEquals(Boolean.TRUE, o); > } -- 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

16 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues June 2008