December 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1911) GWT Console does not deploy in JBoss500

by Thomas Diesler (JIRA)

GWT Console does not deploy in JBoss500 --------------------------------------- Key: JBPM-1911 URL: https://jira.jboss.org/jira/browse/JBPM-1911 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Heiko Braun Fix For: GWT Console 1.0.0 GA 12:25:21,184 ERROR [AbstractKernelController] Error installing to Parse: name=vfszip:/home/tdiesler/svn/jbossas/tags/JBoss_5_0_0_GA/build/output/jboss-5.0.0.GA/server/default/deploy/jbpm/report-server.war state=Not Installed mode=Manual requiredState=Parse org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/home/tdiesler/svn/jbossas/tags/JBoss_5_0_0_GA/build/output/jboss-5.0.0.GA/server/default/deploy/jbpm/report-server.war at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:337) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:297) at org.jboss.deployment.JBossWebAppParsingDeployer.createMetaData(JBossWebAppParsingDeployer.java:103) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:269) at org.jboss.deployment.JBossWebAppParsingDeployer.createMetaData(JBossWebAppParsingDeployer.java:75) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:230) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:619) Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: loader-repository not found as a child of jboss-web at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203) at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168) -- 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

2
2
0 / 0

[JBoss JIRA] Commented: (JBPM-1450) Disable jBPM logging

by Alejandro Guizar (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1450?page=com.atlassian.jira.plug... ] Alejandro Guizar commented on JBPM-1450: ---------------------------------------- To disable the jBPM logging, simply exclude the logging service from the jbpm-context element in jbpm.cfg.xml: <jbpm-context> <service name="persistence" factory="org.jbpm.persistence.db.DbPersistenceServiceFactory" /> <service name="tx" factory="org.jbpm.tx.TxServiceFactory" /> <service name="message" factory="org.jbpm.msg.db.DbMessageServiceFactory" /> <service name="scheduler" factory="org.jbpm.scheduler.db.DbSchedulerServiceFactory" />  <service name="authentication" factory="org.jbpm.security.authentication.DefaultAuthenticationServiceFactory" /> </jbpm-context> > Disable jBPM logging > -------------------- > > Key: JBPM-1450 > URL: https://jira.jboss.org/jira/browse/JBPM-1450 > Project: JBoss jBPM > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Console > Reporter: Mark Little > Assignee: Alejandro Guizar > Fix For: SOA 4.2 CP03, SOA 4.3 > > -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1778) Empty map variables on process creation is set as null

by Paco Avila (JIRA)

Empty map variables on process creation is set as null ------------------------------------------------------ Key: JBPM-1778 URL: https://jira.jboss.org/jira/browse/JBPM-1778 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.3 Environment: JBoss 4.2.2.GA, Database HSQL, Ubuntu Linux Reporter: Paco Avila If I create a ProcessInstances with an empty variables Map, it is set to null. But if I put any value, I works fine. This below code show this behavior. Uncomment the "vars.put("uno", "dos");" line to see it return a the right map when it is not empty. JbpmContext jbpmContext = JbpmConfiguration.getInstance().createJbpmContext(); try { HashMap<String, String> vars = new HashMap<String, String>(); //vars.put("uno", "dos"); ProcessDefinition pd = ProcessDefinition.parseXmlString( "<process-definition>" + " <start-state>" + " <transition to='s' />" + " </start-state>" + " <state name='s'>" + " <transition to='end' />" + " </state>" + " <end-state name='end' />" + "</process-definition>" ); ProcessInstance pi = pd.createProcessInstance(vars); TaskMgmtInstance tmi = pi.getTaskMgmtInstance(); tmi.createStartTaskInstance(); System.out.println("Created ProcessInstance Variables: "+pi.getContextInstance().getVariables()); } catch (Exception e) { e.printStackTrace(); } finally { jbpmContext.close(); } -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1866) add javadocs to installer

by Tom Baeyens (JIRA)

add javadocs to installer ------------------------- Key: JBPM-1866 URL: https://jira.jboss.org/jira/browse/JBPM-1866 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 3.3.1 GA currently only the userguide is in the docs directory. javadocs for jpdl and identity components should be added. -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1706) Documentation - Classes not documented in javadocs

by Facundo Chambo (JIRA)

Documentation - Classes not documented in javadocs -------------------------------------------------- Key: JBPM-1706 URL: https://jira.jboss.org/jira/browse/JBPM-1706 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: jBPM 3.2.3 Environment: Any Reporter: Facundo Chambo Priority: Minor JBoss jBPM 3.2.3 Userguide Chapter 22.3 org.jbpm.security.authorizer.Authorizer class is not in javadocs, not even org.jbpm.security.authorizer package. JBoss jBPM 3.2.3 Userguide Chapter 12.11.3 org/jbpm/identity/User, org/jbpm/identity/Group and org/jbpm/identity/Membership are not in javadocs, not even org.jbpm.identity package. -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1891) Properly document ServiceLoader extension mechanism

by Heiko Braun (JIRA)

Properly document ServiceLoader extension mechanism --------------------------------------------------- Key: JBPM-1891 URL: https://jira.jboss.org/jira/browse/JBPM-1891 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: GWT Console 1.0.0 CR1 -- 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

1
2
0 / 0

[JBoss JIRA] Commented: (JBPM-1450) Disable jBPM logging

by Julian Coleman (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1450?page=com.atlassian.jira.plug... ] Julian Coleman commented on JBPM-1450: -------------------------------------- We modify the hibernate.cfg.xml (*) for the SOA platform. We also now add: <property name="jta.UserTransaction">UserTransaction</property> when we do the other modifications. However, (as per SOA-1039), we haven't modified the standalone jBPM version. It looks like we should probably do that as well. (*) We take jpdl/jar/src/main/config/hibernate.cfg.xml as the source for our modifications. > Disable jBPM logging > -------------------- > > Key: JBPM-1450 > URL: https://jira.jboss.org/jira/browse/JBPM-1450 > Project: JBoss jBPM > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Console > Reporter: Mark Little > Assignee: Alejandro Guizar > Fix For: SOA 4.2 CP03, SOA 4.3 > > -- 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

1
0
0 / 0

[JBoss JIRA] Deleted: (JBPM-1916) Query parameter binding or query with limits can fail with SOA-P 4.2 CP03 jars

by Jiri Pechanec (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1916?page=com.atlassian.jira.plug... ] Jiri Pechanec deleted JBPM-1916: -------------------------------- > Query parameter binding or query with limits can fail with SOA-P 4.2 CP03 jars > ------------------------------------------------------------------------------ > > Key: JBPM-1916 > URL: https://jira.jboss.org/jira/browse/JBPM-1916 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: RHEL 4/PostgreSQL/Oracle 9/Oracle 10 > Reporter: Jiri Pechanec > Priority: Critical > > The tests org.jbpm.AllTests.testBulkJobs and org.jbpm.AllTests.testMultipleExecutors are failing when the testsuite is executed with SOA-P delivered jars on classpath. The problem is caused by incorrect parameter binding for query GraphSession.findLatestProcessDefinitionQuery. > When the test suite is executed on the checked out build, the log contains lines > 08:14:04,146 [main] DEBUG QueryParameters : named parameters: {name=bulk messages} > 08:14:04,147 [main] DEBUG NullableType : binding 'bulk messages' to parameter: 1 > When the tests are failing, the named parameter is bound to the second index > 01:05:36,026 [main] DEBUG QueryParameters : named parameters: {name=bulk messages} > 01:05:36,027 [main] DEBUG NullableType : binding 'bulk messages' to parameter: 2 > Also note the difference in generated sql > OK: > /* named HQL query GraphSession.findLatestProcessDefinitionQuery */ select > processdef0_.ID_ as ID1_112_, > processdef0_.NAME_ as NAME3_112_, > processdef0_.DESCRIPTION_ as DESCRIPT4_112_, > processdef0_.VERSION_ as VERSION5_112_, > processdef0_.ISTERMINATIONIMPLICIT_ as ISTERMIN6_112_, > processdef0_.STARTSTATE_ as STARTSTATE7_112_ > from > JBPM_PROCESSDEFINITION processdef0_ > where > processdef0_.NAME_=? > order by > processdef0_.VERSION_ desc limit ? > Error: > /* named HQL query GraphSession.findLatestProcessDefinitionQuery */ select > top ? processdef0_.ID_ as ID1_123_, > processdef0_.NAME_ as NAME3_123_, > processdef0_.DESCRIPTION_ as DESCRIPT4_123_, > processdef0_.VERSION_ as VERSION5_123_, > processdef0_.ISTERMINATIONIMPLICIT_ as ISTERMIN6_123_, > processdef0_.STARTSTATE_ as STARTSTATE7_123_ > from > JBPM_PROCESSDEFINITION processdef0_ > where > processdef0_.NAME_=? > order by > processdef0_.VERSION_ desc > and then it the log is > select processdef0_.ID_ as ID1_123_, processdef0_.NAME_ as NAME3_123_, processdef0_.DESCRIPTION_ as DESCRIPT4_123_, processdef0_.VERSION_ as VERSION5_123_, processdef0_.ISTERMINATIONIMPLICIT_ as ISTERMIN6_123_, processdef0_.STARTSTATE_ as STARTSTATE7_123_ from JBPM_PROCESSDEFINITION processdef0_ where processdef0_.NAME_=? order by processdef0_.VERSION_ desc > Why is there top ? whcih probably causes to bind parameter on the second position and there is no top ? in the PSQL Exception? -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1916) Query parameter binding or query with limits can fail with SOA-P 4.2 CP03 jars

by Jiri Pechanec (JIRA)

Query parameter binding or query with limits can fail with SOA-P 4.2 CP03 jars ------------------------------------------------------------------------------ Key: JBPM-1916 URL: https://jira.jboss.org/jira/browse/JBPM-1916 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: SOA 4.2 CP03 Environment: RHEL 4/PostgreSQL/Oracle 9/Oracle 10 Reporter: Jiri Pechanec Priority: Critical The tests org.jbpm.AllTests.testBulkJobs and org.jbpm.AllTests.testMultipleExecutors are failing when the testsuite is executed with SOA-P delivered jars on classpath. The problem is caused by incorrect parameter binding for query GraphSession.findLatestProcessDefinitionQuery. When the test suite is executed on the checked out build, the log contains lines 08:14:04,146 [main] DEBUG QueryParameters : named parameters: {name=bulk messages} 08:14:04,147 [main] DEBUG NullableType : binding 'bulk messages' to parameter: 1 When the tests are failing, the named parameter is bound to the second index 01:05:36,026 [main] DEBUG QueryParameters : named parameters: {name=bulk messages} 01:05:36,027 [main] DEBUG NullableType : binding 'bulk messages' to parameter: 2 Also note the difference in generated sql OK: /* named HQL query GraphSession.findLatestProcessDefinitionQuery */ select processdef0_.ID_ as ID1_112_, processdef0_.NAME_ as NAME3_112_, processdef0_.DESCRIPTION_ as DESCRIPT4_112_, processdef0_.VERSION_ as VERSION5_112_, processdef0_.ISTERMINATIONIMPLICIT_ as ISTERMIN6_112_, processdef0_.STARTSTATE_ as STARTSTATE7_112_ from JBPM_PROCESSDEFINITION processdef0_ where processdef0_.NAME_=? order by processdef0_.VERSION_ desc limit ? Error: /* named HQL query GraphSession.findLatestProcessDefinitionQuery */ select top ? processdef0_.ID_ as ID1_123_, processdef0_.NAME_ as NAME3_123_, processdef0_.DESCRIPTION_ as DESCRIPT4_123_, processdef0_.VERSION_ as VERSION5_123_, processdef0_.ISTERMINATIONIMPLICIT_ as ISTERMIN6_123_, processdef0_.STARTSTATE_ as STARTSTATE7_123_ from JBPM_PROCESSDEFINITION processdef0_ where processdef0_.NAME_=? order by processdef0_.VERSION_ desc and then it the log is select processdef0_.ID_ as ID1_123_, processdef0_.NAME_ as NAME3_123_, processdef0_.DESCRIPTION_ as DESCRIPT4_123_, processdef0_.VERSION_ as VERSION5_123_, processdef0_.ISTERMINATIONIMPLICIT_ as ISTERMIN6_123_, processdef0_.STARTSTATE_ as STARTSTATE7_123_ from JBPM_PROCESSDEFINITION processdef0_ where processdef0_.NAME_=? order by processdef0_.VERSION_ desc Why is there top ? whcih probably causes to bind parameter on the second position and there is no top ? in the PSQL Exception? -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1858) managing tasks through task service api

by Tom Baeyens (JIRA)

managing tasks through task service api --------------------------------------- Key: JBPM-1858 URL: https://jira.jboss.org/jira/browse/JBPM-1858 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.0.0 Alpha1 goal is that this api should support UIs for users to dynamically create tasks and close them tracking their work. -- 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

3
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues December 2008