November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPM-760) Add indexes to foreign keys where appropriate

by Jeff DeLong (JIRA)

Add indexes to foreign keys where appropriate --------------------------------------------- Key: JBPM-760 URL: http://jira.jboss.com/jira/browse/JBPM-760 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM 3.2 Reporter: Jeff DeLong Assigned To: Tom Baeyens create index IDX_MODDEF_PROCDEF on JBPM_MODULEDEFINITION (PROCESSDEFINITION_); create index IDX_MODINST_PRCINST on JBPM_MODULEINSTANCE (PROCESSINSTANCE_); create index IDX_NODE_ACTION on JBPM_NODE (ACTION_); create index IDX_PROCIN_ROOTTKN on JBPM_PROCESSINSTANCE (ROOTTOKEN_); create index IDX_TASK_TASKNODE on JBPM_TASK (TASKNODE_); create index IDX_TSK_TSKCTRL on JBPM_TASK (TASKCONTROLLER_); create index IDX_TASK_TASKMGTDEF on JBPM_TASK (TASKMGMTDEFINITION_); create index IDX_TASKINST_TASK on JBPM_TASKINSTANCE (TASK_, TOKEN_); create index IDX_TASKINST_TMINST on JBPM_TASKINSTANCE (TASKMGMTINSTANCE_); create index IDX_TOKEN_NODE on JBPM_TOKEN (NODE_); create index IDX_TOKEN_PROCINST on JBPM_TOKEN (PROCESSINSTANCE_); create index IDX_TOKEN_PARENT on JBPM_TOKEN (PARENT_); create index IDX_TKVARMAP_CTXT on JBPM_TOKENVARIABLEMAP (CONTEXTINSTANCE_); create index IDX_TKVARMAP_TOKEN on JBPM_TOKENVARIABLEMAP (TOKEN_); create index IDX_VARINST_TKVARMP on JBPM_VARIABLEINSTANCE (TOKENVARIABLEMAP_); create index IDX_VARINST_PRCINST on JBPM_VARIABLEINSTANCE (PROCESSINSTANCE_); create index IDX_VARINST_TK on JBPM_VARIABLEINSTANCE (TOKEN_); -- 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

19 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-761) SchedulerThread opens the default jbpm configuration (jbpm.cfg.xml) even when created with a different config specification

by Michael Holtzman (JIRA)

SchedulerThread opens the default jbpm configuration (jbpm.cfg.xml) even when created with a different config specification --------------------------------------------------------------------------------------------------------------------------- Key: JBPM-761 URL: http://jira.jboss.com/jira/browse/JBPM-761 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.2 Environment: Windows XP, JVM 1.4.2 Reporter: Michael Holtzman Assigned To: Tom Baeyens Priority: Minor See jBPM forum http://www.jboss.com/index.html?module=bb&op=viewtopic&t=91756 Side issue: There is no way to instantiate org.jbpm.scheduler.impl.Scheduler with a non-default jbpmConfiguration specification. -- 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

19 years, 8 months

2
1
0 / 0

[JBoss JIRA] Closed: (JBPM-345) persisting process definition with superstate hibernate problems

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-345?page=all ] Tom Baeyens closed JBPM-345. ---------------------------- Resolution: Done long time fixed; i just don't remember in which version > persisting process definition with superstate hibernate problems > ---------------------------------------------------------------- > > Key: JBPM-345 > URL: http://jira.jboss.com/jira/browse/JBPM-345 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0.1 > Reporter: James Depoorter > Assigned To: Tom Baeyens > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When persisting a process definition with superstates and reloading, hibernate has trouble loading "root" nodes mixed with superstates. The superstate 'overwrites' the link. This is due to the re-use of the collectionindex column for both nodes within superstates, and nodes within process definition, and the fact that EVERY node has a link to the process definition. -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-764) condition expression string is restricted to 255 character length if the process definition is persistent

by Hannes Stillerich (JIRA)

condition expression string is restricted to 255 character length if the process definition is persistent --------------------------------------------------------------------------------------------------------- Key: JBPM-764 URL: http://jira.jboss.com/jira/browse/JBPM-764 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.2 Environment: Win XP SP2, JDK 1.5.0_06, JBoss4.0.3SP1, MySQL 5.0.18-nt-max Reporter: Hannes Stillerich Assigned To: Tom Baeyens The expression of a condition (in a decision node) gets cut up if it is too long (>255 characters), e.g. <decision name="Check Prerequisition"> <transition name="proceed" to="Planning State"> </transition> <transition name="rejected" to="Error State"> <condition expression="#{(contextInstance.variables['isCLIaffected'] and !contextInstance.variables['CLI_OK']) or (contextInstance.variables['isCAaffected'] and !contextInstance.variables['CA_OK']) or (contextInstance.variables['isCMAaffected'] and !contextInstance.variables['CMA_OK']) or (contextInstance.variables['isREGENaffected'] and !contextInstance.variables['REGEN_OK']) or (contextInstance.variables['isSGSNaffected'] and !contextInstance.variables['SGSN_OK']) or (contextInstance.variables['isRNCaffected'] and !contextInstance.variables['RNC_OK'])}"/> </transition> </decision> Of course a org.jbpm.JbpmException occures (couldn't evaluate expression) which is cause by org.jbpm.jpdl.el.ELException: Encountered "<EOF>", expected one of [".", ">", "gt", ..... But if the processdefinition doesn't get loaded from the db, in other words it is directly defined in the code, the expression string can be longer (in this case 539 characters) and the expression works fine. -- 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

19 years, 8 months

3
4
0 / 0

[JBoss JIRA] Commented: (EJBTHREE-633) OutOfBound exception during startup of EJB3 embeddable

by Ramil Israfilov (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-633?page=comments#action_12347191 ] Ramil Israfilov commented on EJBTHREE-633: ------------------------------------------ Issue is in JBOSS microcontainer http://jira.jboss.com/jira/browse/JBMICROCONT-102 get latest jboss-dependency.jar from JBOSS repository: http://repository.jboss.com/jboss/microcontainer/snapshot/lib/ > OutOfBound exception during startup of EJB3 embeddable > ------------------------------------------------------ > > Key: EJBTHREE-633 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-633 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC8 - FD > Environment: windows xp, JDK1.5_07 > Reporter: Ramil Israfilov > > We use EJB3 embeddabel RC8 for JUNIT tests of our EJBs. > After moving to RC8 version we have strange problem on JDK1.5_07 running on windows. > From junit log file: > 64952 [main] INFO org.hibernate.impl.SessionFactoryImpl - closing > 64983 [main] ERROR junit.certipost.customers.belgacom.transformation.SignEncryptSplitTest - java.lang.RuntimeException: java.lang.IndexOutOfBoundsException: Index: 7, Size: 7 > java.lang.RuntimeException: java.lang.RuntimeException: java.lang.IndexOutOfBoundsException: Index: 7, Size: 7 > at org.jboss.ejb3.embedded.EJB3StandaloneBootstrap.scanClasspath(EJB3StandaloneBootstrap.java:296) > at junit.certipost.customers.belgacom.transformation.SignEncryptSplitTest.startupEmbeddedJboss(SignEncryptSplitTest.java:204) > at junit.certipost.customers.belgacom.transformation.SignEncryptSplitTest$1.setUp(SignEncryptSplitTest.java:142) > at junit.extensions.TestSetup$1.protect(TestSetup.java:18) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.extensions.TestSetup.run(TestSetup.java:23) > at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:297) > at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:672) > at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:567) > Caused by: java.lang.RuntimeException: java.lang.IndexOutOfBoundsException: Index: 7, Size: 7 > at org.jboss.ejb3.MCKernelAbstraction.install(MCKernelAbstraction.java:95) > at org.jboss.ejb3.Ejb3Deployment.registerEJBContainer(Ejb3Deployment.java:439) > at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:486) > at org.jboss.ejb3.embedded.EJB3StandaloneDeployer.start(EJB3StandaloneDeployer.java:460) > at org.jboss.ejb3.embedded.EJB3StandaloneBootstrap.scanClasspath(EJB3StandaloneBootstrap.java:291) > ... 8 more > Caused by: java.lang.IndexOutOfBoundsException: Index: 7, Size: 7 > at EDU.oswego.cs.dl.util.concurrent.CopyOnWriteArrayList.rangeCheck(CopyOnWriteArrayList.java:752) > at EDU.oswego.cs.dl.util.concurrent.CopyOnWriteArrayList.get(CopyOnWriteArrayList.java:372) > at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:341) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:438) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:379) > at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:225) > at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:151) > at org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:79) > at org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:73) > at org.jboss.ejb3.MCKernelAbstraction.install(MCKernelAbstraction.java:91) > ... 12 more > Strange thing if we run the same test on Solaris JVM (AMD64 platform) with JDK1.5_01 we never had such error. -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-765) wrong example in configuring persistence factory

by Wenbo Zhu (JIRA)

wrong example in configuring persistence factory ------------------------------------------------ Key: JBPM-765 URL: http://jira.jboss.com/jira/browse/JBPM-765 Project: JBoss jBPM Issue Type: Bug Components: Documentation Affects Versions: jBPM 3.1.2 Environment: 3.1.2 under AS 4.0.4 Reporter: Wenbo Zhu Assigned To: Tom Baeyens The example from the user guide states: 7.2.2. The DbPersistenceServiceFactory The DbPersistenceServiceFactory itself has 3 more configuration properties: isTransactionEnabled, sessionFactoryJndiName and dataSourceJndiName. To specify any of these properties in the jbpm.cfg.xml, you need to specify the service factory as a bean in the factory element like this: <jbpm-context> <service name="persistence"> <factory> <bean factory="org.jbpm.persistence.db.DbPersistenceServiceFactory"> <field name="isTransactionEnabled"><false /></field> <field name="sessionFactoryJndiName"> <string value="java:/myHibSessFactJndiName" /> </field> <field name="dataSourceJndiName"> <string value="java:/myDataSourceJndiName" /> </field> </bean> </factory> </service> ... </jbpm-context> which should be: <jbpm-context> <service name="persistence"> <factory> <bean name="persistence.factory" class="org.jbpm.persistence.db.DbPersistenceServiceFactory"> <field name="isTransactionEnabled"> <false /> </field> .... </bean> </factory> </service> .... </jbpm-context> Also, as a side feature request, it may be useful to allow a partial configuration (bean merge maybe), that is without repeating the unchanged <service>'s for configuring the persistence for jbpm-context. Thanks. -- 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

19 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-767) ExpressionEvaluatorHandler has BeanInfo, which does not use the correct set of methods

by Kannan Ekanath (JIRA)

ExpressionEvaluatorHandler has BeanInfo, which does not use the correct set of methods -------------------------------------------------------------------------------------- Key: JBPM-767 URL: http://jira.jboss.com/jira/browse/JBPM-767 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.4 Reporter: Kannan Ekanath Assigned To: Tom Baeyens ExpressionEvaluatorHandler doesnt work in the expected way for subclasses. To quote an example consider, public void testSome() { JbpmExpressionEvaluator e = new JbpmExpressionEvaluator(); final Book book = new Book(); book.setUseful(false); VariableResolver variableResolver = new VariableResolver() { public Object resolveVariable(String pName) throws ELException { return book; } }; e.setVariableResolver(variableResolver); System.out.println(e.evaluate("#{book.isUseful}", new ExecutionContext(new Token()))); } Carefully note that useful is an attribute, isUseful is the bean getter. The above code works fine. However, if you have any subclass of a book, say for example, replace the line, final Book book = new Book(); final Book book = new MySubclassOfBook(); Now the same code gives the error, Caused by: org.jbpm.jpdl.el.ELException: Unable to find a value for "isUseful" in object of class "MySubclassOfBook" using operator "." This is because, in bean introspection BeanInfoManager.java --> method initialize(Logger logger) void initialize(Logger pLogger) throws ELException { ... Method[] methods = mBeanClass.getDeclaredMethods(); for (int i=0; i<methods.length; i++) { Method method = methods[i]; } It is using the *getDeclaredMethods()* API and not *getMethods()*. The getdeclaredmethods api gives apis declared only by that class and not inherited ones. -- 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

19 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-777) Process instance deletion issue

by Syed Arshad (JIRA)

Process instance deletion issue ------------------------------- Key: JBPM-777 URL: http://jira.jboss.com/jira/browse/JBPM-777 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1 Environment: Windows XP, Tomcat 5.5, Java 1.5_09 Reporter: Syed Arshad Assigned To: Tom Baeyens Issue: When we try to delete a process instance with associated Timers, a database exception thrown indicating referential integrity issue. When I looked into the GraphSession code, I found that it is not deleting the associated timers, which was the issue. The issue found in the method : org.jbpm.db.GraphSession.deleteProcessInstance(ProcessInstance processInstance); Fix: Modified the GraphSession class's deleteProcessInstance(ProcessInstance processInstance) to delete the associated timers as well in the method implementation: Patch code: org.jbpm.db.GraphSession.deleteProcessInstance(ProcessInstance processInstance){ ................... .................. SchedulerService schedulerService = (SchedulerService) Services.getCurrentService(Services.SERVICENAME_SCHEDULER, false); if (schedulerService!=null) schedulerService.cancelTimersByProcessInstance(processInstance); .................... ................... } -- 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

19 years, 8 months

2
1
0 / 0

RESPALDO EN LINEA, REMOTO, SIMPLE, EFICIENTE Y SEGURO, PARA WINDOWS, LINUX Y MAC, OTRO SERVICIO DE HOSTEX.CL -- SIEMPRE INNOVANDO

by Respaldo de Datos

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBFORUMS-142) JavaScript message check doesn't work for Instant reply box

by Ryszard Kozmik (JIRA)

JavaScript message check doesn't work for Instant reply box ----------------------------------------------------------- Key: JBFORUMS-142 URL: http://jira.jboss.com/jira/browse/JBFORUMS-142 Project: JBoss Forums Issue Type: Bug Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Priority: Minor Fix For: 1.0.0 Beta On TopicView there is JavaScript fuction for checking whether entered reply message in "Instant reply" box is not empty. After JSF refactoring it stopped working and throws error in web browser's javascript console. -- 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

19 years, 8 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2006