June 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1895) verify html documentation style sheets for internet explorer

by Tom Baeyens (JIRA)

verify html documentation style sheets for internet explorer ------------------------------------------------------------ Key: JBPM-1895 URL: https://jira.jboss.org/jira/browse/JBPM-1895 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.0.0 Alpha2 currently the userguide and devguide don't display well on internet explorer. -- 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, 4 months

2
7
0 / 0

[JBoss JIRA] Created: (JBPM-1285) add fixed date timer support

by Tom Baeyens (JIRA)

add fixed date timer support ---------------------------- Key: JBPM-1285 URL: http://jira.jboss.com/jira/browse/JBPM-1285 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PVM Reporter: Tom Baeyens add support in the TimerDefinition for fixed dueDates this should be done by adding a dueDate (type java.util.Date) property to the TimerDefinition and adding the necessary logic in the timer creation. -- 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

15 years, 4 months

4
10
0 / 0

[JBoss JIRA] Created: (JBPM-1189) Create a story for the xsd

by Koen Aers (JIRA)

Create a story for the xsd --------------------------- Key: JBPM-1189 URL: http://jira.jboss.com/jira/browse/JBPM-1189 Project: JBoss jBPM Issue Type: Task Reporter: Koen Aers Assigned To: Tom Baeyens Currently the jpdl xsd appears in multiple locations: - the runtime - the designer - online These should be synchronized at regular times. There should be a strategy to make sure this happens. -- 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

15 years, 4 months

5
7
0 / 0

[JBoss JIRA] Created: (JBPM-2022) EnvironmentFactory cannot be bound to JBNDI

by Heiko Braun (JIRA)

EnvironmentFactory cannot be bound to JBNDI ------------------------------------------- Key: JBPM-2022 URL: https://jira.jboss.org/jira/browse/JBPM-2022 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Reporter: Heiko Braun Assignee: Heiko Braun Fix For: jBPM 4.0.0.GA Bonanova:enterprise hbraun$ mvn -Djboss.bind.address=localhost -Dtest=CommandExecutorTest test 10:13:45,303 ERROR [STDERR] Feb 6, 2009 10:13:45 AM org.jbpm.log.Jdk14Log info INFO: WARNING: environment factory binding failed javax.naming.CommunicationException [Root exception is java.io.NotSerializableException: org.jbpm.pvm.internal.svc.DefaultCommandService] at org.jnp.interfaces.NamingContext.bind(NamingContext.java:664) at org.jnp.interfaces.NamingContext.bind(NamingContext.java:598) at javax.naming.InitialContext.bind(InitialContext.java:359) at org.jbpm.enterprise.internal.ejb.CommandExecutorSLSB.bind(CommandExecutorSLSB.java:184) at org.jbpm.enterprise.internal.ejb.CommandExecutorSLSB.ejbCreate(CommandExecutorSLSB.java:149) -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2004) finish database cleanup of all the tests

by Tom Baeyens (JIRA)

finish database cleanup of all the tests ---------------------------------------- Key: JBPM-2004 URL: https://jira.jboss.org/jira/browse/JBPM-2004 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.0.0.Beta2 -- 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, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-1288) evaluate the previous methods

by Tom Baeyens (JIRA)

evaluate the previous methods ----------------------------- Key: JBPM-1288 URL: http://jira.jboss.com/jira/browse/JBPM-1288 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: PVM Reporter: Tom Baeyens this relates to Execution.getPreviousNode() Execution.getPreviousTransition() Node.isPreviousNeeded() Comment in Execution.java: // TODO evaluate the previous methods // these methods are kind of performance optimisations. a sequence and // some other specific control flow implementations can be optimised if they // have access to the previous node or transition. // Those activities could also be implemented by letting the activities store // the contextual information in process variables or some other execution // context. But with the previous properties as done now, these control flow // nodes can be implemented without storing an extra record. It's only a property // that is only updated when the node configuration indicates that it's needed. // (see also Node.isPreviousNeeded()) -- 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

15 years, 4 months

1
7
0 / 0

[JBoss JIRA] Created: (JBPM-2273) remove transaction from jta config

by Tom Baeyens (JIRA)

remove transaction from jta config ---------------------------------- Key: JBPM-2273 URL: https://jira.jboss.org/jira/browse/JBPM-2273 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.0 the jbpm.tx.jta.cfg.xml contains a transaction. for all configurations that have <hibernate-session current="true" /> there should be no standard transaction. -- 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, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-1685) Check persistence of exception field in JobImpl

by Guillaume Porcher (JIRA)

Check persistence of exception field in JobImpl ----------------------------------------------- Key: JBPM-1685 URL: https://jira.jboss.org/jira/browse/JBPM-1685 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: PVM Reporter: Guillaume Porcher Priority: Critical in jobs, there is a exception field to put the exception stacktrace in hibernate mappings, this column length is set to 4000. Some stacktrace are more than 4000 char long, this creates an exception with hibernate. <tomb> porcherg: the 4000 is because of some DB limitation <tomb> i believe db2 <tomb> iirc, in db, the max string field is 4000 <tomb> if you want to go beyond that, we would need to use CLOBs <tomb> but i'm open to alternatives <tomb> maybe the stacktrace field should be a CLOB ? <porcherg> tomb: the problem is that it creates an exception if it is too long <tomb> yes <tomb> so we have to fix it somehow <tomb> just removing the 4000 limit is not good <tomb> as it will not work on db2 <tomb> so we either manually truncate the exception field in the code <tomb> in the setter <tomb> or we change it into a clob <tomb> probably the latter is better <porcherg> maybe we can use hibernate "text" type <porcherg> "text: Maps long Java strings to a SQL CLOB or TEXT type. " <tomb> do you guys have access to db2 db ? <tomb> the first thing we should do is verify if this problem is really present <tomb> so we should remove the 4000 limit in the hibernate mappings and see if we can create that problem on db2 <tomb> once we can reproduce it, then we can start looking for alternatives that fix the problem on db2 <tomb> then we can see if the fix works on the other dbs <tomb> i am a bit reluctant to start using clobs <tomb> as this would be the first use case for it <tomb> and clobs might lead to even more DB dependent issues... <tomb> but if there is no other way, then we have to <tomb> so let's start by removing the 4000 limit in the hibernate mappings and prioritizing that we have to test it in db2 -- 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, 4 months

2
7
0 / 0

[JBoss JIRA] Created: (JBPM-2278) verify publication of enterprise module jar

by Tom Baeyens (JIRA)

verify publication of enterprise module jar ------------------------------------------- Key: JBPM-2278 URL: https://jira.jboss.org/jira/browse/JBPM-2278 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.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

15 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-1438) Task assigned to different actor-id can be seen and manipulated in jBPM console

by Martin Vecera (JIRA)

Task assigned to different actor-id can be seen and manipulated in jBPM console ------------------------------------------------------------------------------- Key: JBPM-1438 URL: https://jira.jboss.org/jira/browse/JBPM-1438 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jPDL 3.2.2 Environment: JBossESB server 4.3.GA, bpm_orchestration4 Reporter: Martin Vecera By default JBossESB server 4.3.GA has several jBPM users configured including 'user' and 'manager'. bpm_orchestration4 example contains one process definition which assigns two tasks, first to actor-id 'user' and the second to actor-id 'manager'. The problem is that the 'user' can see and manipulate both of the tasks. Steps to reproduce: 1. download JBossESB server 4.3.GA 2. start it using bin/run.sh 3. go to samples/quickstarts/bpm_orchestration4 4. run one by one: ant deploy, ant deployProcess, ant startProcess 5. open jBPM console and login as 'user' with password 'user' 6. click on Tasks to see the task list and on Examine to open the task, then on Save and Close 7. refresh the task list and you can see second task assigned to 'manager', try to Examine it... -- 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, 4 months

3
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues June 2009