October 2006 - jboss-jira - Jboss List Archives

[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, 6 months

2
1
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, 6 months

3
4
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, 6 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBFORUMS-126) NewTopic on ForumsView doesn't work on IE

by Ryszard Kozmik (JIRA)

NewTopic on ForumsView doesn't work on IE ----------------------------------------- Key: JBFORUMS-126 URL: http://jira.jboss.com/jira/browse/JBFORUMS-126 Project: JBoss Forums Issue Type: Bug Affects Versions: 1.0.0 Alpha Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Priority: Minor Creating topic by NewTopic button on ForumsView is not possible when browsing Forums using IE. -- 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, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-720) PojoCache findAll api if argument is null is to find all pojos in the system

by Ben Wang (JIRA)

PojoCache findAll api if argument is null is to find all pojos in the system ---------------------------------------------------------------------------- Key: JBCACHE-720 URL: http://jira.jboss.com/jira/browse/JBCACHE-720 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: 2.0.0 E.g., findAll(null) is to find everything under the cache store. Also note that, if a POJO is multiple referenced, we should return them as well (since id is unique). -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-819) Release Beta

by Manik Surtani (JIRA)

Release Beta ------------ Key: JBCACHE-819 URL: http://jira.jboss.com/jira/browse/JBCACHE-819 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-770) Option to Not Signal a Sub-Process in the Process-State Node

by Jed Danner (JIRA)

Option to Not Signal a Sub-Process in the Process-State Node ------------------------------------------------------------ Key: JBPM-770 URL: http://jira.jboss.com/jira/browse/JBPM-770 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM 3.1.2 Environment: Feature request. Reporter: Jed Danner Assigned To: Tom Baeyens Priority: Minor I've found a case where I'd like to start a sub-process from a process but I don't want to signal it immediately. There is an external source which will handle that signalling. I've made some modifications to the ProcessState.java file, as such: Added a new class member: protected boolean signalProcess = true; Added a check in the read method: String signalText = subProcessElement.attributeValue("signal"); if (signalText!=null) { if (("no".equalsIgnoreCase(signalText)) || ("false".equalsIgnoreCase(signalText)) ) { signalProcess = false; } } Added a check in the execute method (right before the signal): if (!signalProcess) return; Added a new method: public boolean getSignalProcess() { return signalProcess; } And updated the jpdl-3.1.xsd and jpdl-3.0.xsd files (wasn't sure if I needed to do both). What I see is when the process is deployed, the read method see my new attribute and sets it to 'false' as I want. But when the process comes along and I get into the execute method the value of signalProcess is 'true'. I'm thinking there is another step I need to take but don't know what it is. If someone can take a look or provide a pointer (And finds this feature request useful) - it'd be great to have it integrated. 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-771) Auto-increment long primary keys for process definition and instance are not acceptable for the systems with decentralized database

by Andriy Gryn (JIRA)

Auto-increment long primary keys for process definition and instance are not acceptable for the systems with decentralized database ----------------------------------------------------------------------------------------------------------------------------------- Key: JBPM-771 URL: http://jira.jboss.com/jira/browse/JBPM-771 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM 3.1.3 Reporter: Andriy Gryn Assigned To: Tom Baeyens Due to different reasons (e.g. absense of the reliable communication channels) it may be necessary to support decentralized mode when there is several database servers containing partial data (e.g. one database server per region) that are replicated from time to time to the central database to build consolidated system. ProcessDefinition and ProcessInstance have now long primary key with native generator. In the scenario with decentralized database this approach will not work. Instead GUIDs could to be used as primary keys for objects that are to be consolidated to central database. It seems that currently modification required to support decentralized mode. -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-772) jbpm.war does not deploy in JBoss 4.0.5.GA

by David Owens (JIRA)

jbpm.war does not deploy in JBoss 4.0.5.GA ------------------------------------------ Key: JBPM-772 URL: http://jira.jboss.com/jira/browse/JBPM-772 Project: JBoss jBPM Issue Type: Bug Components: Web Interface Affects Versions: jBPM 3.1.3 Environment: JBoss 4.0.5.GA from jems-installer-1.2.0.BETA3.jar with EJB profile. Reporter: David Owens Assigned To: Tom Baeyens If you copy the jbpm.sar folder and the jbpm.war folder from the jbpm-3.1.3 starter kit into a JBoss 4.0.5.GA deploy directory, it will not deploy. You get this error message: 18:51:20,421 INFO [SchedulerThread] runtime exception while executing timers org.hibernate.HibernateException: Could not parse configuration: hibernate.cfg.xml at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1418) at org.hibernate.cfg.Configuration.configure(Configuration.java:1352) at org.jbpm.db.hibernate.HibernateHelper.createConfiguration(HibernateHelper.java:90) at org.jbpm.persistence.db.DbPersistenceServiceFactory.getConfiguration(DbPersistenceServiceFactory.java:68) at org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:90) at org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:74) at org.jbpm.persistence.db.DbPersistenceService.getSession(DbPersistenceService.java:78) at org.jbpm.persistence.db.DbPersistenceService.getSchedulerSession(DbPersistenceService.java:254) at org.jbpm.JbpmContext.getSchedulerSession(JbpmContext.java:529) at org.jbpm.scheduler.impl.SchedulerThread.executeTimers(SchedulerThread.java:104) at org.jbpm.scheduler.impl.SchedulerThread.run(SchedulerThread.java:71) Caused by: org.dom4j.DocumentException: org.dom4j.DocumentFactory Nested exception: org.dom4j.DocumentFactory at org.dom4j.io.SAXReader.read(SAXReader.java:484) at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1408) ... 10 more Which is caused by a ClassCastException from the SAXReader. After removing the dom4j-1.6.1.jar from jbpm.war\META-INF\lib the war will deploy. -- 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, 6 months

2
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 October 2006