January 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1094) some database tests fail when hsql configuration is removed

by Aleksandar Kostadinov (JIRA)

some database tests fail when hsql configuration is removed ----------------------------------------------------------- Key: JBPM-1094 URL: http://jira.jboss.com/jira/browse/JBPM-1094 Project: JBoss jBPM Issue Type: Bug Reporter: Aleksandar Kostadinov Assigned To: Fady Matar Tests org.jbpm.AllTests.testCustomVariableClassWithLongId org.jbpm.AllTests.testCustomVariableClassWithStringId org.jbpm.AllTests.testProcessDeployment fail with any database if hsqldb configuration from hibernate.cfg.xml is removed. Probably these are not picking up some configuration. See http://hudson.qa.jboss.com/hudson/view/jbpm/ for a reference. Assigning to Fady since he worked on database tests last time. Please reassign as appropriate. -- 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, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPM-1089) JBPM.3 SOA-P branch to be testable against EAP/SOA-P distribution

by Aleksandar Kostadinov (JIRA)

JBPM.3 SOA-P branch to be testable against EAP/SOA-P distribution ----------------------------------------------------------------- Key: JBPM-1089 URL: http://jira.jboss.com/jira/browse/JBPM-1089 Project: JBoss jBPM Issue Type: Task Reporter: Aleksandar Kostadinov Assigned To: Koen Aers We need to be able to test the SOA-P branch of jbpm against JBoss EAP 4.3 and JBoss SOA-P. So that will require the availability of a build option to select location of EAP/SOA-P binary zip distribution and if that property has been set, the test.classpath of tested modules to be set to use libraries from the distribution instead using classes from the jbpm build directory. As well there needs to be a property for the enterprise module test suite to skip deployment of jbpm on the JBoss server so we can test actual jars shipped and not these just compiled from sources. -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] Commented: (JBPM-1022) 3.2.1 Admin Console: Any user sees all users tasks

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1022?page=comments#action_12397510 ] Ronald van Kuijk commented on JBPM-1022: ---------------------------------------- Great, I'll change this tonight and check it in.... > 3.2.1 Admin Console: Any user sees all users tasks > --------------------------------------------------- > > Key: JBPM-1022 > URL: http://jira.jboss.com/jira/browse/JBPM-1022 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Affects Versions: jBPM jPDL 3.2.1, jBPM jPDL 3.2.2 > Reporter: Burr Sutter > Assigned To: Ronald van Kuijk > Priority: Blocker > Fix For: jBPM jPDL 3.2.3 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > In the current Admin Console, any given user will see all other users tasks. Plus a user can "take" another person's assigned tasks even when they are not an "administrator". -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1022) 3.2.1 Admin Console: Any user sees all users tasks

by Sebastien M. (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1022?page=comments#action_12397474 ] Sebastien M. commented on JBPM-1022: ------------------------------------ Ok, so I've tried it and it works well. The tasks shown are only those which belong to the user logged in. > 3.2.1 Admin Console: Any user sees all users tasks > --------------------------------------------------- > > Key: JBPM-1022 > URL: http://jira.jboss.com/jira/browse/JBPM-1022 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Affects Versions: jBPM jPDL 3.2.1, jBPM jPDL 3.2.2 > Reporter: Burr Sutter > Assigned To: Ronald van Kuijk > Priority: Blocker > Fix For: jBPM jPDL 3.2.3 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > In the current Admin Console, any given user will see all other users tasks. Plus a user can "take" another person's assigned tasks even when they are not an "administrator". -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1023) 3.2.1 Admin Console: No download for AS 4.2 with Java 5

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1023?page=comments#action_12397425 ] Ronald van Kuijk commented on JBPM-1023: ---------------------------------------- Those are? It's FOSS you know... Lot's of people who use other appservers like WLS, Oracle or whatever have to tune something, deployment wise.... or other. > 3.2.1 Admin Console: No download for AS 4.2 with Java 5 > ------------------------------------------------------- > > Key: JBPM-1023 > URL: http://jira.jboss.com/jira/browse/JBPM-1023 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Reporter: Burr Sutter > Assigned To: Tom Baeyens > > The current 3.2.1 jPDL Suite download doesn't produce a WAR that runs on AS 4.2 with Java 5. The offending jar seems to be gravel-14.jar -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-479) Option to allow Tokens with activechildren not to continue transition

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-479?page=comments#action_12397398 ] Ronald van Kuijk commented on JBPM-479: --------------------------------------- is this still an issue in 3.2? > Option to allow Tokens with activechildren not to continue transition > --------------------------------------------------------------------- > > Key: JBPM-479 > URL: http://jira.jboss.com/jira/browse/JBPM-479 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.1 alpha 1 > Environment: any > Reporter: Elmo > Assigned To: Tom Baeyens > Priority: Optional > > When a process instance (root token) is signalled in a fork, or in a subprocess, the process continues via the default leaving node. This is quite misleading. In my opinion the desired behavior would be blocking (i.e. means all child tokens must have ended) before continuing the transition. Although this can be managed through code, signalling the token (fork) by accident would give undesired results. If possible, I would like an option to stop the token from continuing if there are still active children. The code below illustrates this: > source: Token > public void signal() { > //initial checking > //proposed code: if option is used by developer, block the signal if there are active children > if( (CHECK_ACTIVECHILDREN_OPTION) && (this.hasActiveChildren()) ) > throw new IllegalStateException( "Cannot signal " + this + " if there are active children" ); > //signal routine > } > This option is false by default. I leave it to the group how they will set the option, either through the node definition (private) or to the process definition or maybe even through system properties (global). The users who will implement this must be aware of the consequences i.e. it is their responsibility to end the child tokens themselves or else it can never continue. This is only an option. I have not fully tested or did a full test case on the side effects of this, so I would appreciate if somebody could point this out because I have it implemented in my code. Thanks. > > Regards, > Elmo -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1023) 3.2.1 Admin Console: No download for AS 4.2 with Java 5

by Ryan R. LaMothe (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1023?page=comments#action_12397273 ] Ryan R. LaMothe commented on JBPM-1023: --------------------------------------- Normally, building and maintaining jBPM from CVS source when you are not a jBPM developer or a RedHat employee is unacceptable for a number of reasons. > 3.2.1 Admin Console: No download for AS 4.2 with Java 5 > ------------------------------------------------------- > > Key: JBPM-1023 > URL: http://jira.jboss.com/jira/browse/JBPM-1023 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Reporter: Burr Sutter > Assigned To: Tom Baeyens > > The current 3.2.1 jPDL Suite download doesn't produce a WAR that runs on AS 4.2 with Java 5. The offending jar seems to be gravel-14.jar -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1023) 3.2.1 Admin Console: No download for AS 4.2 with Java 5

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1023?page=comments#action_12397117 ] Ronald van Kuijk commented on JBPM-1023: ---------------------------------------- the jBPM source has (afaik) a build target for JBoss AS 4.2.x. So there should not be a need to disassemble etc.... in that case, unacceptable sounds a little harsh doesn't it ;-). Escalation is normally done by getting enough votes. Or in case you have paid support, contact that department. > 3.2.1 Admin Console: No download for AS 4.2 with Java 5 > ------------------------------------------------------- > > Key: JBPM-1023 > URL: http://jira.jboss.com/jira/browse/JBPM-1023 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Reporter: Burr Sutter > Assigned To: Tom Baeyens > > The current 3.2.1 jPDL Suite download doesn't produce a WAR that runs on AS 4.2 with Java 5. The offending jar seems to be gravel-14.jar -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1023) 3.2.1 Admin Console: No download for AS 4.2 with Java 5

by Ryan R. LaMothe (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1023?page=comments#action_12397116 ] Ryan R. LaMothe commented on JBPM-1023: --------------------------------------- This issue needs to be escalated to the top of the priority list. I have made a forum post regarding this issue at http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123853#4123853 The two main problems here are: 1) JSF libs in the web console WAR conflict with JBoss and are no longer needed in the WAR 2) JBoss AOP backported libs for JDK 1.4 are no longer needed since they conflict with JDK 1.5 Regardless of whether jBPM 3.3 or higher is supposedly going to Seam from JSF (and where is the release timeline posted???), the 3.2 release needs to be updated and re-released to work with JBoss AS 4.2.x. Having to download the jBPM enterprise EAR, disassemble it, manually remove/update/configure various components and then re-assemble the EAR to work properly is really unacceptable. How can this issue get escalated and who needs to be contacted to get this done? Thanks. > 3.2.1 Admin Console: No download for AS 4.2 with Java 5 > ------------------------------------------------------- > > Key: JBPM-1023 > URL: http://jira.jboss.com/jira/browse/JBPM-1023 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Reporter: Burr Sutter > Assigned To: Tom Baeyens > > The current 3.2.1 jPDL Suite download doesn't produce a WAR that runs on AS 4.2 with Java 5. The offending jar seems to be gravel-14.jar -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1111) Followup questions on removal of jpdl namespace ref in SOA-P quickstarts - SOA-344,JBESB-1503

by Len DiMaggio (JIRA)

Followup questions on removal of jpdl namespace ref in SOA-P quickstarts - SOA-344,JBESB-1503 ---------------------------------------------------------------------------------------------- Key: JBPM-1111 URL: http://jira.jboss.com/jira/browse/JBPM-1111 Project: JBoss jBPM Issue Type: Bug Components: BPEL Affects Versions: jBPM jPDL 3.2.2 Environment: jpdl 3.2.2 - SOA Platform build beta2 Reporter: Len DiMaggio Assigned To: Tom Baeyens Followup questions on this removal of the XML namespace reference - see SOA-344,JBESB-1503 - in processdefinition.xml files in SOA-P jBPM quickstarts: http://viewvc.jboss.org/cgi-bin/viewvc.cgi/labs/labs/jbossesb/branches/JB... Was this change made between SOA-P beta1 and beta2 - and if so in response to which JIRA? Or, was the change in beta1 and we missed it in our testing? Also - what's the reason for this change? Another side-effect of this change is that JBDS 1.0 - in creating a new jBPM project - creates a processdefinition file with this (the old) syntax: <?xml version="1.0" encoding="UTF-8"?> <process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="simple"> Should we recommend that users manually remove the namespace reference? -- 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, 11 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues January 2008