March 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2109) Server shutdown undeployment calls have unmet dependency

by Heiko Braun (JIRA)

Server shutdown undeployment calls have unmet dependency --------------------------------------------------------- Key: JBPM-2109 URL: https://jira.jboss.org/jira/browse/JBPM-2109 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Integration Reporter: Heiko Braun Assignee: Heiko Braun Fix For: jBPM 4.0.0.Beta1 -- 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

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-2082) Instance ID doesn't reveal the process version

by Heiko Braun (JIRA)

Instance ID doesn't reveal the process version ---------------------------------------------- Key: JBPM-2082 URL: https://jira.jboss.org/jira/browse/JBPM-2082 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Heiko Braun Assignee: Tom Baeyens Fix For: jBPM 4.0.0.Beta1 -- 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

15 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-2108) Provide deployers for jboss 4 & 5

by Heiko Braun (JIRA)

Provide deployers for jboss 4 & 5 --------------------------------- Key: JBPM-2108 URL: https://jira.jboss.org/jira/browse/JBPM-2108 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Integration Reporter: Heiko Braun Assignee: Heiko Braun Fix For: jBPM 4.0.0.Beta1 -- 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

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBPM-1449) TagLibraryConfig loadImplicit errors

by Ronald van Kuijk (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1449?page=com.atlassian.jira.plug... ] Ronald van Kuijk commented on JBPM-1449: ---------------------------------------- define 'an actual fix' please? > TagLibraryConfig loadImplicit errors > ------------------------------------ > > Key: JBPM-1449 > URL: https://jira.jboss.org/jira/browse/JBPM-1449 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Reporter: Len DiMaggio > Assignee: Alejandro Guizar > Priority: Minor > > Platform JIRA for project JIRA: JBPM-1065 -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBPM-1449) TagLibraryConfig loadImplicit errors

by Alejandro Guizar (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1449?page=com.atlassian.jira.plug... ] Alejandro Guizar reopened JBPM-1449: ------------------------------------ Assignee: Alejandro Guizar (was: Thomas Diesler) An actual fix is required for 3.2.5.SP. > TagLibraryConfig loadImplicit errors > ------------------------------------ > > Key: JBPM-1449 > URL: https://jira.jboss.org/jira/browse/JBPM-1449 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Reporter: Len DiMaggio > Assignee: Alejandro Guizar > Priority: Minor > > Platform JIRA for project JIRA: JBPM-1065 -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBPM-1446) display non GMT+0 time zones

by Alejandro Guizar (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1446?page=com.atlassian.jira.plug... ] Alejandro Guizar reopened JBPM-1446: ------------------------------------ Fix is required in branch 3.2.5.SP as well. > display non GMT+0 time zones > ---------------------------- > > Key: JBPM-1446 > URL: https://jira.jboss.org/jira/browse/JBPM-1446 > Project: JBoss jBPM > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core Engine > Affects Versions: jBPM 3.2.3 > Reporter: Jiri Pechanec > Assignee: Alejandro Guizar > Fix For: jBPM 3.2.6 GA > > Attachments: Screenshot.jpg, SolutionShot.png > > > I spotted it today so I am creating the link to project JIRA. It is really inconvenient for user to have UTC time displayed in browser. See JBPM-987 -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-2097) Release jBPM jPDL 3.2.6.SP1

by Alejandro Guizar (JIRA)

Release jBPM jPDL 3.2.6.SP1 --------------------------- Key: JBPM-2097 URL: https://jira.jboss.org/jira/browse/JBPM-2097 Project: JBoss jBPM Issue Type: Release Security Level: Public (Everyone can see) Components: Core Engine Reporter: Alejandro Guizar Assignee: Alejandro Guizar Fix For: jBPM 3.2.6 GA Service release to 3.2.6.GA. Include jsf-console 3.2.6.SP2, see JBPM-2095. -- 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

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-2090) JpdlXmlReader: couldn't parse process definition probable schema validation problem

by Karl Palsson (JIRA)

JpdlXmlReader: couldn't parse process definition probable schema validation problem ----------------------------------------------------------------------------------- Key: JBPM-2090 URL: https://jira.jboss.org/jira/browse/JBPM-2090 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.3.1 GA Environment: 3.3.1GA Reporter: Karl Palsson ProcessDefinition.parseXXX all fail for me. FileInputStream fis = new FileInputStream(fileName); ProcessDefinition pd = ProcessDefinition.parseParZipInputStream(new ZipInputStream(fis)); Or any variant thereof, gives me errors that seem related to schema validation. Full stack trace below. According to: http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.GA/html/JBPM_Refe... and some other brief mentions in bug reports, it seems that schema validation should only be applied if there is an xmlns= attribute on the process defintion tag. However, even without any xmlns attribute, I get these errors. I have tried using my own process definitions, with and without the xmlns attribute. <process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="CreateLineService2"> or <process-definition name="CreateLineService2"> or even <process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="CreateLineService2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:jbpm.org:jpdl-3.2 http://docs.jboss.org/jbpm/xsd/jpdl-3.2.xsd"> I've even tried using the processdefinition.xml that comes in "examples\simple\src\main\jpdl" from the jbpm-3.3.1GA installer, with exactly the same results. I cannot try the ant task, as it demands a hibernate.cfg.xml, but we're using hibernate annotations and spring, so we don't have a cfg.xml file. There is no longer a deployer servelet like in jbpm 3.1.2 (which we were using before a recent upgrade) so I don't know of any other way of trying to deploy a new process now. The error message has not proved very helpful to me to try and work around this myself. :( 2009-03-09 17:22:25,260 DEBUG [org.jbpm.jpdl.xml.JpdlParser:main] - <schema resource found: org/jbpm/jpdl/xml/jpdl-3.2.xsd> 2009-03-09 17:22:25,260 DEBUG [org.jbpm.jpdl.xml.JpdlParser:main] - <schema resource found: org/jbpm/jpdl/xml/jpdl-3.3.xsd> 2009-03-09 17:22:25,260 DEBUG [org.jbpm.jpdl.xml.JpdlParser:main] - <schema resource found: org/jbpm/jpdl/xml/jpdl-3.0.xsd> 2009-03-09 17:22:25,260 DEBUG [org.jbpm.jpdl.xml.JpdlParser:main] - <schema resource found: org/jbpm/jpdl/xml/jpdl-3.1.xsd> 2009-03-09 17:22:38,073 ERROR [org.jbpm.jpdl.xml.JpdlXmlReader:main] - <couldn't parse process definition> org.dom4j.DocumentException: http://java.sun.com/xml/jaxp/properties/schemaSource Nested exception: http://java.sun.com/xml/jaxp/properties/schemaSource at org.dom4j.io.SAXReader.read(SAXReader.java:484) at org.jbpm.jpdl.xml.JpdlParser.parse(JpdlParser.java:66) at org.jbpm.jpdl.xml.JpdlXmlReader.readProcessDefinition(JpdlXmlReader.java:142) at org.jbpm.jpdl.par.JpdlArchiveParser.readFromArchive(JpdlArchiveParser.java:51) at org.jbpm.jpdl.par.ProcessArchive.parseProcessDefinition(ProcessArchive.java:87) at org.jbpm.graph.def.ProcessDefinition.parseParZipInputStream(ProcessDefinition.java:191) at vodafone.nip.applications.processupload.ProcessUploader.loadFile(ProcessUploader.java:50) at vodafone.nip.applications.processupload.ProcessUploader.main(ProcessUploader.java:41) Nested exception: org.xml.sax.SAXException: http://java.sun.com/xml/jaxp/properties/schemaSource at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1176) at org.dom4j.io.SAXReader.read(SAXReader.java:465) at org.jbpm.jpdl.xml.JpdlParser.parse(JpdlParser.java:66) at org.jbpm.jpdl.xml.JpdlXmlReader.readProcessDefinition(JpdlXmlReader.java:142) at org.jbpm.jpdl.par.JpdlArchiveParser.readFromArchive(JpdlArchiveParser.java:51) at org.jbpm.jpdl.par.ProcessArchive.parseProcessDefinition(ProcessArchive.java:87) at org.jbpm.graph.def.ProcessDefinition.parseParZipInputStream(ProcessDefinition.java:191) at mycode.blah() -- 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

15 years, 9 months

3
9
0 / 0

[JBoss JIRA] Created: (JBPM-2095) Release JSF console 3.2.6.SP2

by Alejandro Guizar (JIRA)

Release JSF console 3.2.6.SP2 ----------------------------- Key: JBPM-2095 URL: https://jira.jboss.org/jira/browse/JBPM-2095 Project: JBoss jBPM Issue Type: Release Security Level: Public (Everyone can see) Components: Console Reporter: Alejandro Guizar Assignee: Alejandro Guizar Fix For: jBPM 3.2.6 GA JSF console is broken. Timer creation fails with the exception below. javax.naming.NamingException: Could not dereference object [Root exception is javax.naming.NameNotFoundException: ejb not bound] at org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:1215) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:758) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:774) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627) at javax.naming.InitialContext.lookup(InitialContext.java:409) at org.jbpm.scheduler.ejbtimer.EntitySchedulerServiceFactory.lookup(EntitySchedulerServiceFactory.java:54) at org.jbpm.scheduler.ejbtimer.EntitySchedulerServiceFactory.getTimerEntityHome(EntitySchedulerServiceFactory.java:43) EJB reference ejb/TimerEntityBean in jboss-web.xml points to an unexisting bean. This had been fixed in 3.2.6.GA but somehow got reintroduced in 3.2.6.SP1. -- 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

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-2098) Provide comprehensive console test coverage

by Thomas Diesler (JIRA)

Provide comprehensive console test coverage ------------------------------------------- Key: JBPM-2098 URL: https://jira.jboss.org/jira/browse/JBPM-2098 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Console Reporter: Thomas Diesler Assignee: Heiko Braun Fix For: jBPM 3.2.6.SP1 Heiko, we please show us the manual test protocol that you are running through for every jBPM console release. The results need to be documented publicly for every release. -- 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

15 years, 9 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 March 2009