August 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2412) add support for ejb method invocation to java activity

by Tom Baeyens (JIRA)

add support for ejb method invocation to java activity ------------------------------------------------------ Key: JBPM-2412 URL: https://jira.jboss.org/jira/browse/JBPM-2412 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Assignee: Alejandro Guizar Fix For: jBPM 4.1 java activity is about method invocation we should add the capability to the java activity for invoking a method on an ejb. can we support ejb 2 and 3, or do we need to choose ? -- 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

3
8
0 / 0

[JBoss JIRA] Created: (JBPM-2300) jms activity

by Tom Baeyens (JIRA)

jms activity ------------ Key: JBPM-2300 URL: https://jira.jboss.org/jira/browse/JBPM-2300 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.1 add an activity that can send a jms message -- 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
14
0 / 0

[JBoss JIRA] Created: (JBPM-1914) Problem in retrieving variables of Serializable objects

by Mauro Molinari (JIRA)

Problem in retrieving variables of Serializable objects ------------------------------------------------------- Key: JBPM-1914 URL: https://jira.jboss.org/jira/browse/JBPM-1914 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.3.0 GA Reporter: Mauro Molinari Priority: Critical I have encountered a serious problem working with variables whose value is a serializable object. The problem is that sometimes (not always!) an error like the following is given when retrieving a variable: java.lang.ClassCastException: org.jbpm.bytes.ByteArray$$EnhancerByCGLIB$$cc67d06e The code is like: MySerializableClass obj = (MySerializableClass) contextInstance.getVariable("myVariable"); (of course, "myVariable" is a variable that I previously have set with a MySerializableClass object) Apart from the CGLIB awful problem with proxies, even if I extract the value from the proxy with the following: public static Object getCGLIBProxiedObject(final Object proxy) { if(proxy instanceof HibernateProxy) { final LazyInitializer initializer = ((HibernateProxy) proxy).getHibernateLazyInitializer(); return initializer.getImplementation(); } return proxy; } the problem is that the variable value is retrieved as a org.jbpm.bytes.ByteArray instead of a MyClass instance! I did some debugging and discovered that: - in org.jbpm.context.exe.VariableContainer.getVariable(String), when org.jbpm.context.exe.VariableContainer.hasVariableLocally(String) is called, Hibernate lazily retrieves a org.jbpm.context.exe.variableinstance.ByteArrayInstance instance from the database and creates it using its empty constructor - unfortunately, when a org.jbpm.context.exe.VariableInstance (extended by ByteArrayInstance) is constructed using its constructor, its converter instance variable remains null - the VariableInstance converter instance variable is set to something only when a VariableInstance is created using org.jbpm.context.exe.JbpmType.newVariableInstance(), but this is not the case when a VariableInstance is lazily loaded by Hibernate; in fact, in my case, org.jbpm.context.exe.JbpmType.newVariableInstance() is never called and the converter field of my ByteArrayInstance instance is always null! - this causes org.jbpm.context.exe.VariableInstance.getValue() to return the value given by org.jbpm.context.exe.variableinstance.ByteArrayInstance.getObject() without applying the necessary conversion (deserialization) Please note that my variable values are stored in jBPM database in JBPM_VARIABLEINSTANCE table with the CONVERTER column correctly populated with "R". I think this is a critical problem. By now, the only workaround I have found is to always apply the following utility method when retrieving variable values, before returning them to the client code: public static Object extractVariableValue(final Object rawValue) { Object result = CardinisJbpmUtilities.getCGLIBProxiedObject(rawValue); if(result instanceof ByteArray) try { result = new ObjectInputStream(new ByteArrayInputStream(((ByteArray) result) .getBytes())).readObject(); } catch(final Exception e) { throw new RuntimeException(e); } return result; } -- 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

5
21
0 / 0

[JBoss JIRA] Created: (JBPM-2345) javax/el/ExpressionFactory Linkage error

by Tom Vleminckx (JIRA)

javax/el/ExpressionFactory Linkage error ----------------------------------------- Key: JBPM-2345 URL: https://jira.jboss.org/jira/browse/JBPM-2345 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Environment: Leopard 10.5,Tomcat6, Spring 2.5 Reporter: Tom Vleminckx I'm having the following error when trying to integrate JBPM4 with spring. This is a runtime error when trying to deploy to tomcat. ----------------- SEVERE: Exception sending context initialized event to listener instance of class com.sun.faces.config.ConfigureListener java.lang.LinkageError: loader constraint violation: when resolving interfacemethod "javax.servlet.jsp.JspApplicationContext.getExpressionFactory()Ljavax/el/ExressionFactory;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, com/sun/faces/config/ConfgureListener, and the class loader (instance of org/apache/catalina/loader/StandardClassLoader) for resolved class, javax/servlet/jsp/JspApplicatonContext, have different Class objects for the type javax/el/ExpressionFactory used in the signature at com.sun.faces.config.ConfigureListener.registerELResolverAndListenerWithJsp(ConfigureListener.java:1570) at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:403) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3934) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4429) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:850) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:518) at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1288) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(Unknown Source) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(Unknown Source) at org.apache.catalina.manager.ManagerServlet.check(ManagerServlet.java:1473) at org.apache.catalina.manager.HTMLManagerServlet.doPost(HTMLManagerServlet.java:250) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454) at java.lang.Thread.run(Unknown Source) ... ------------------- -- 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

6
5
0 / 0

[JBoss JIRA] Created: (JBPM-2151) no environment to get org.jbpm.session.RepositorySession

by Heiko Braun (JIRA)

no environment to get org.jbpm.session.RepositorySession -------------------------------------------------------- Key: JBPM-2151 URL: https://jira.jboss.org/jira/browse/JBPM-2151 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: jBPM 4.0.0.Beta1 Caused by: org.jbpm.JbpmException: no environment to get org.jbpm.session.RepositorySession at org.jbpm.env.Environment.getFromCurrent(Environment.java:195) at org.jbpm.env.Environment.getFromCurrent(Environment.java:188) at org.jbpm.pvm.internal.model.ExecutionImpl.getProcessDefinition(ExecutionImpl.java:1026) at org.jbpm.pvm.internal.model.ExecutionImpl.getProcessDefinition(ExecutionImpl.java:79) at org.jbpm.integration.console.ModelAdaptor.adoptExecution(ModelAdaptor.java:66) at org.jbpm.integration.console.ProcessManagementImpl.adoptTopLevelExecutions(ProcessManagementImpl.java:123) at org.jbpm.integration.console.ProcessManagementImpl.getProcessInstances(ProcessManagementImpl.java:104) -- 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

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-2492) GetOutcomes returns an additional Outcome than what is already specified than the

by Shekhar Vemuri (JIRA)

GetOutcomes returns an additional Outcome than what is already specified than the ---------------------------------------------------------------------------------- Key: JBPM-2492 URL: https://jira.jboss.org/jira/browse/JBPM-2492 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0.CR1 Reporter: Shekhar Vemuri Fix For: jBPM 4.1 Description is below: It was decided in a discussion in the forum(referenced in this issue) that we would not add the additional transition to the list of transitions that are available as part of completing a task. Problem: Is there a particular reason for why GetOutComes does this? Code: Set<String> outcomes = new HashSet<String>(); outcomes.add(Task.STATE_COMPLETED); .. logic to add other transitions specified in the activity. When the TaskService.getOutComes(long taskDbId) is called with a task id it returns completed as an entry in the list of Transitions that will eventually be shown to the user. But this particular transition is not even being modeled in the process_definition. There are other places in the code, where in if a transition/outcome name is not specified then the transition is assumed to the 'completed' and special handling is done, Code: if (Task.STATE_COMPLETED.equals(signalName)) { if (outgoingTransitions.size()==1) { transition = outgoingTransitions.get(0); } else { transition = activity.getDefaultOutgoingTransition(); } } The above snippet is from TaskActivity. What is the reasoning behind adding this to the transitions that can be taken out of a Task node? _________________ -- 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
8
0 / 0

[JBoss JIRA] Created: (JBPM-2006) drools integration

by Tom Baeyens (JIRA)

drools integration ------------------ Key: JBPM-2006 URL: https://jira.jboss.org/jira/browse/JBPM-2006 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Priority: Minor Fix For: jBPM 4.0.0.Beta2 * exclusive condition evaluation * configurable process variables to submit as facts * make process variables available as rules global variables * investigate logging integration * investigate joint deployment of rules in process archive -- 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

5
18
0 / 0

[JBoss JIRA] Created: (JBPM-2508) report initialization crashes the console

by Tom Baeyens (JIRA)

report initialization crashes the console ----------------------------------------- Key: JBPM-2508 URL: https://jira.jboss.org/jira/browse/JBPM-2508 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Console Reporter: Tom Baeyens Assignee: Heiko Braun Fix For: jBPM 4.2 First time when the reports are accessed, the request times out and the console cannot show the reports. Reports cannot be made visible afterwards. Workaround: log out and log back in. -- 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
8
0 / 0

[JBoss JIRA] Created: (JBPM-2143) jBPM creates two indices for each foreign key column on MySQL

by Jiri Pechanec (JIRA)

jBPM creates two indices for each foreign key column on MySQL ------------------------------------------------------------- Key: JBPM-2143 URL: https://jira.jboss.org/jira/browse/JBPM-2143 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.2.5.SP5 Reporter: Jiri Pechanec The SQL scripts for MySQL contains two independent index creations for each indexed foreign key column - see sample create index IDX_LOG_SOURCENODE on JBPM_LOG (SOURCENODE_); alter table JBPM_LOG add index FK_LOG_SOURCENODE (SOURCENODE_), add constraint FK_LOG_SOURCENODE foreign key (SOURCENODE_) references JBPM_NODE (ID_); -- 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

2
7
0 / 0

[JBoss JIRA] Created: (JBPM-2491) Deleting a ProcessInstance having a running Sub-ProcessInstance fails

by Flavio Donzé (JIRA)

Deleting a ProcessInstance having a running Sub-ProcessInstance fails --------------------------------------------------------------------- Key: JBPM-2491 URL: https://jira.jboss.org/jira/browse/JBPM-2491 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0 Reporter: Flavio Donzé When trying to delete a ProcessInstance using ExecutionService.deleteProcessInstance() an SQLException is thrown if the ProcessInstance has a running Sub-ProcessInstance. Trying to delete the Sub-ProcessInstance first doesn't work either. The problem here are the foreign key constraints: Deleting the super process: org.postgresql.util.PSQLException: ERROR: update or delete on table "jbpm4_execution" violates foreign key constraint "fk_exec_superexec" on table "jbpm4_execution" Detail: Key (dbid_)=(176) is still referenced from table "jbpm4_execution". Deleting the sub process: org.postgresql.util.PSQLException: ERROR: update or delete on table "jbpm4_execution" violates foreign key constraint "fk_exec_subpi" on table "jbpm4_execution" Detail: Key (dbid_)=(179) is still referenced from table "jbpm4_execution". Maybe loosen up the sub>super constraint? -- 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, 1 month

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues August 2009