January 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Resolved: (JBPM-756) log.debug calls are unprotected

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-756?page=com.atlassian.jira.plugi... ] Thomas Diesler resolved JBPM-756. --------------------------------- Fix Version/s: (was: jBPM 3.3.2 GA ) Resolution: Out of Date Resolve bugs older than a year as "Out of Date" > log.debug calls are unprotected > ------------------------------- > > Key: JBPM-756 > URL: https://jira.jboss.org/jira/browse/JBPM-756 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.1.2 > Environment: Window XP, Java 5 > Reporter: Dave Caruana > > Within org.jbpm.context.exe.VariableContainer there are calls to log.debug. In particular: > line 156: log.debug("create variable '"+name+"' in '"+this+"' with value '"+value+"'"); > line 160: log.debug("update variable '"+name+"' in '"+this+"' to value '"+value+"'"); > However, they are unprotected i.e. the method is called even if debug logging is not switched on. This is not too much of a problem if the variable value is of a primitive type, but sometimes, values can be complex (including their toString()). > "if (log.isDebugEnabled())" statements are missing. -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-1008) ejb deployment : avoid ClassNotFoundException on client side after unmarshalling

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1008?page=com.atlassian.jira.plug... ] Thomas Diesler resolved JBPM-1008. ---------------------------------- Fix Version/s: (was: jBPM 3.3.2 GA ) Resolution: Out of Date Resolve bugs older than a year as "Out of Date" > ejb deployment : avoid ClassNotFoundException on client side after unmarshalling > --------------------------------------------------------------------------------- > > Key: JBPM-1008 > URL: https://jira.jboss.org/jira/browse/JBPM-1008 > Project: JBoss jBPM > Issue Type: Bug > Components: Console > Affects Versions: jBPM 3.2.1 > Environment: enterprise jBPM > Reporter: Adrian Dimulescu > > Two aspects in this jira : 1: hide hibernate-specific exceptions; 2: hide hibernate-specific datatypes. > 1. The EJB client only depends on the jBPM jar (for the various Command implementations) and on the JBoss client jar. If a Hibernate exception occurs, it is wrapped by a JBPMException and rethrown. When deserialiezed on the client side (which does not have a Hibernate dependency), a ClassNotFoundException occurs. > I think the CommandServiceBean should not wrap internal implementation-specific exceptions; it should instead simply copy the stack trace and throw a new implementation-independent exception which contains the exception trace without containing the causes themselves. That typically avoids ClassNotFoundExceptions without losing exception history. > 2. The second problem is that hibernate-specific collections get serialized over the wire, here is the description of the problem : > I use the GetProcessInstancesCommand in order to experiment with querying the remote ejb. This command returns a list with ProcessInstances. A ProcessInstance is read by Hibernate from the database. As Hibernate uses specific lazy-loading-aware implementations for collections -- the ProcessInstance.instances attribute, which is declared of type java.util.Map, is actually implemented by org.hibernate.collections.PersistentMap. > Which generates class loading exception while deserializing to hibernate-unaware ejb clients. > The solution would then be for the Command implementations to return clean JDK collections, by replacing Hibernate collection with JDK standard ones. Note that IIUC only the collections must be replaced, not the collection contents too, so the "cleaning" operation should not be that expensive. Cleaning should be only done in the SLSB remote call use case -- because in-JVM callers may want to benefit lazy-loading. -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-1013) Logging out and back in seems to render an error.

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1013?page=com.atlassian.jira.plug... ] Thomas Diesler resolved JBPM-1013. ---------------------------------- Fix Version/s: (was: jBPM 3.3.2 GA ) Resolution: Out of Date Resolve bugs older than a year as "Out of Date" > Logging out and back in seems to render an error. > ------------------------------------------------- > > Key: JBPM-1013 > URL: https://jira.jboss.org/jira/browse/JBPM-1013 > Project: JBoss jBPM > Issue Type: Bug > Components: Console > Affects Versions: jBPM 3.2.1 > Environment: Fedora Core 6 + Firefox 1.5.0.12 + Sun Java 1.5.0.12 > Reporter: Micah Modell > > If you log in and leave for about fifteen minutes or so, then return and attempt to log oout and back in as another user, you get the following (ugly) jsp error: > -------------- > HTTP Status 500 - > type Exception report > message > description The server encountered an internal error () that prevented it from fulfilling this request. > exception > javax.servlet.ServletException: viewId:/sa/identities.jsf - View /sa/identities.jsf could not be restored. > javax.faces.webapp.FacesServlet.service(FacesServlet.java:249) > org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > root cause > javax.faces.application.ViewExpiredException: viewId:/sa/identities.jsf - View /sa/identities.jsf could not be restored. > com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:180) > com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248) > com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) > javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) > org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > note The full stack trace of the root cause is available in the Apache Tomcat/5.5.17 logs. > Apache Tomcat/5.5.17 > -------------- > and the following stack trace on the console: > -------------- > javax.faces.application.ViewExpiredException: viewId:/sa/identities.jsf - View /sa/identities.jsf could not be restored. > at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:180) > at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248) > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) > at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) > at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) > at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) > at java.lang.Thread.run(Thread.java:595) -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-893) JBPM_VARIABLEINSTANCE.STRINGVALUE_ is inconsistent with JBPM_LOG.OLDSTRINGVALUE_ and JBPM_LOG.NEWSTRINGVALUE_

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-893?page=com.atlassian.jira.plugi... ] Thomas Diesler resolved JBPM-893. --------------------------------- Fix Version/s: (was: jBPM 3.3.2 GA ) Resolution: Out of Date Resolve bugs older than a year as "Out of Date" > JBPM_VARIABLEINSTANCE.STRINGVALUE_ is inconsistent with JBPM_LOG.OLDSTRINGVALUE_ and JBPM_LOG.NEWSTRINGVALUE_ > ------------------------------------------------------------------------------------------------------------- > > Key: JBPM-893 > URL: https://jira.jboss.org/jira/browse/JBPM-893 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.1.4 > Environment: JBoss AS 4.0.5 GA + jBPM 3.1.4 + RHEL 4 + Oracle 10g > Reporter: Romeu Figueira > Priority: Minor > Original Estimate: 5 minutes > Remaining Estimate: 5 minutes > > The column JBPM_VARIABLEINSTANCE.STRINGVALUE_ is slated as VARCHAR2(255 char) while JBPM_LOG.OLDSTRINGVALUE_ and JBPM.NEWSTRINGVALUE_ are slated as VARCHAR2(4000). > These two values should be a match between each other. -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1947) Release bpm-spec-1.0.0.Alpha2

by Thomas Diesler (JIRA)

Release bpm-spec-1.0.0.Alpha2 ----------------------------- Key: JBPM-1947 URL: https://jira.jboss.org/jira/browse/JBPM-1947 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: API Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: BPM Spec 1.0.0 Alpha1 -- 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

17 years, 3 months

1
5
0 / 0

[JBoss JIRA] Created: (JBPM-1825) Example not correct or ProcessDefinition.parseXmlString throw exception

by Tom Eugelink (JIRA)

Example not correct or ProcessDefinition.parseXmlString throw exception ----------------------------------------------------------------------- Key: JBPM-1825 URL: https://jira.jboss.org/jira/browse/JBPM-1825 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: API, Documentation Affects Versions: jBPM 3.2.3 Environment: WindowsXP SP3, Eclipse 3.4.1 Reporter: Tom Eugelink The "Hello World" example uses a jbpm.cfg.xml and works correct. The second example "database" gets and exception in the ProcessDefinition.parseXmlString line as soon as the jbpm.cfg.xml is missing. From the example code it seems that this should not happen, especially since the second example features code-driven configuration (not programmatic configuration). Anyhow; either the documentation is wrong or the ProcessDefinition.parseXmlString method. -- 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

17 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-1697) Task Type Send

by Thomas Diesler (JIRA)

Task Type Send -------------- Key: JBPM-1697 URL: https://jira.jboss.org/jira/browse/JBPM-1697 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: API Reporter: Thomas Diesler -- 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

17 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBPM-1698) Task Type Receive

by Thomas Diesler (JIRA)

Task Type Receive ----------------- Key: JBPM-1698 URL: https://jira.jboss.org/jira/browse/JBPM-1698 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: API Reporter: Thomas Diesler Fix For: JBossBPM-API-1.0.0.Alpha -- 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

17 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-1703) Activity OutputSets

by Thomas Diesler (JIRA)

Activity OutputSets ------------------- Key: JBPM-1703 URL: https://jira.jboss.org/jira/browse/JBPM-1703 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: API Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossBPM-API-1.0.0.Alpha -- 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

17 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-1702) Activity InputSets

by Thomas Diesler (JIRA)

Activity InputSets ------------------ Key: JBPM-1702 URL: https://jira.jboss.org/jira/browse/JBPM-1702 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: API Reporter: Thomas Diesler -- 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

17 years, 3 months

1
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues January 2009