June 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1883) Provide an initial implementation of a AS4 deployer

by Thomas Diesler (JIRA)

Provide an initial implementation of a AS4 deployer --------------------------------------------------- Key: JBPM-1883 URL: https://jira.jboss.org/jira/browse/JBPM-1883 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Productization Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: jBPM 3.3.1 GA -- 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

14 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-2172) integrate jboss identity component

by Tom Baeyens (JIRA)

integrate jboss identity component ---------------------------------- Key: JBPM-2172 URL: https://jira.jboss.org/jira/browse/JBPM-2172 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Jeff Yu Fix For: jBPM 4.0.0.GA -- 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

14 years, 11 months

2
20
0 / 0

[JBoss JIRA] Created: (JBPM-2329) re-introduce timers in the userguide

by Tom Baeyens (JIRA)

re-introduce timers in the userguide ------------------------------------ Key: JBPM-2329 URL: https://jira.jboss.org/jira/browse/JBPM-2329 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.1 change jpdpl schema of the timers: from <on event="timeout"> <timer duedate="10 minutes"/> <event-listener class="org.jbpm.examples.timer.event.Escalate" /> </on> to <timer duedate="10 minutes" fire-event="timeout"> <event-listener class="org.jbpm.examples.timer.event.Escalate" /> </timer> and re-introduce the timers back in the userguide -- 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

14 years, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPM-1987) create optimistic locking test

by Tom Baeyens (JIRA)

create optimistic locking test ------------------------------ Key: JBPM-1987 URL: https://jira.jboss.org/jira/browse/JBPM-1987 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.0.0.Beta1 create a test that produces an optimistic locking failure. this will 1) verify that the db isolation works correctly 2) allow us to see how this gets logged. (in jbpm 3, a lot of people complained because there were still SOSEs in the logs) -- 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

14 years, 11 months

2
9
0 / 0

[JBoss JIRA] Created: (JBPM-2117) get schema reviewed by real dba

by Tom Baeyens (JIRA)

get schema reviewed by real dba ------------------------------- Key: JBPM-2117 URL: https://jira.jboss.org/jira/browse/JBPM-2117 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.0.0.CR1 gert leenders might know someone that might be willing to have a look at 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

14 years, 11 months

3
14
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-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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues June 2009