October 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1742) Cleanup ExpressionAssignmentHandlerTest

by Thomas Diesler (JIRA)

Cleanup ExpressionAssignmentHandlerTest --------------------------------------- Key: JBPM-1742 URL: https://jira.jboss.org/jira/browse/JBPM-1742 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Core Engine Reporter: Thomas Diesler Fix For: jBPM 3.3.0 Cleanup left over ProcessDefinition -- 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

16 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-1741) Cleanup BusinessKeyDbTest

by Thomas Diesler (JIRA)

Cleanup BusinessKeyDbTest ------------------------- Key: JBPM-1741 URL: https://jira.jboss.org/jira/browse/JBPM-1741 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Core Engine Reporter: Thomas Diesler Fix For: jBPM 3.3.0 Cleanup left over ProcessDefinition -- 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

16 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1739) Cleanup GraphSessionDbTest

by Thomas Diesler (JIRA)

Cleanup GraphSessionDbTest -------------------------- Key: JBPM-1739 URL: https://jira.jboss.org/jira/browse/JBPM-1739 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Core Engine Reporter: Thomas Diesler Fix For: jBPM 3.3.0 Cleanup left over ProcessDefinition -- 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

16 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-1740) Cleanup TaskVariablesDbTest

by Thomas Diesler (JIRA)

Cleanup TaskVariablesDbTest --------------------------- Key: JBPM-1740 URL: https://jira.jboss.org/jira/browse/JBPM-1740 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Core Engine Reporter: Thomas Diesler Fix For: jBPM 3.3.0 Cleanup left over ProcessDefinition -- 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

16 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-1777) Unable to deploy the Hello Example in JBPM-BPEL

by Prasad Hastantram (JIRA)

Unable to deploy the Hello Example in JBPM-BPEL ----------------------------------------------- Key: JBPM-1777 URL: https://jira.jboss.org/jira/browse/JBPM-1777 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: BPEL Environment: JBOSS 4.0.5 GA, jbpm-bpel-1.1.GA Reporter: Prasad Hastantram Dear Sir, The files(hello.bpel,hello.wsdl & hello.bplex) in location $jbpm-bpel-1.1.GA\examples\hello\src\main\bpel2 are zipped in to hello.zip and is deployed in http://localhost:8080/jbpm-bpel/processes.jsp. Then i am getting the below mentioned exception 19:57:15,734 ERROR [ProblemHandler] partner link type not found (hello.bpel) at /bpws:process/bpws:partnerLinks/bpws:partnerLink 19:57:15,734 ERROR [ProblemHandler] my role not found (hello.bpel) at /bpws:proc ess/bpws:sequence/bpws:receive 19:57:16,046 ERROR [ProblemHandler] partner link does not indicate my role (hell o.bpel) at /bpws:process/bpws:sequence/bpws:reply 19:57:16,046 ERROR [[deploymentServlet]] Servlet.service() for servlet deploymen tServlet threw exception org.jbpm.bpel.xml.BpelParseException: 3 problem(s) found at org.jbpm.bpel.par.GenericArchiveParser.readFromArchive(GenericArchive Parser.java:59) at org.jbpm.jpdl.par.ProcessArchive.parseProcessDefinition(ProcessArchiv e.java:81) at org.jbpm.bpel.web.DeploymentServlet.readProcessDefinition(DeploymentS ervlet.java:169) at org.jbpm.bpel.web.DeploymentServlet.doPost(DeploymentServlet.java:95) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi lter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV alve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV alve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit yAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv e.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j ava:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j ava:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConne ctionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal ve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav a:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java :869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.p rocessConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo int.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWor kerThread.java:112) at java.lang.Thread.run(Thread.java:595) Please do the needful by helping me to resolve the same -- 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

16 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1419) decide on use of BooleanArray

by Tom Baeyens (JIRA)

decide on use of BooleanArray ----------------------------- Key: JBPM-1419 URL: https://jira.jboss.org/jira/browse/JBPM-1419 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: PVM Reporter: Tom Baeyens are we going to combine multiple boolean fields into one column ? should BooleanArray (+test) be kept or should we remove 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

16 years, 2 months

3
5
0 / 0

[JBoss JIRA] Commented: (JBPM-1448) jBPM does not initialise thread context classloader

by Bernd Ruecker (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1448?page=com.atlassian.jira.plug... ] Bernd Ruecker commented on JBPM-1448: ------------------------------------- Fixed. As soon as my commit problem gets resolved I will commit it... All tests still pass... > jBPM does not initialise thread context classloader > --------------------------------------------------- > > Key: JBPM-1448 > URL: https://jira.jboss.org/jira/browse/JBPM-1448 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Reporter: Kevin Conner > Assignee: Tom Baeyens > Priority: Critical > Fix For: SOA 4.2 CP03, SOA 4.3, jBPM 3.3.0 GA > > > jBPM does not initialise the thread context classloader when executing actions within the process. > The outcome of this decision is that code executed within the context of this action will not have access to classes/resources in the par unless the action classloader is an explicit parameter. > One example of this is the RMI marshalling layer, which has an implication on JNDI lookups. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1448) jBPM does not initialise thread context classloader

by Bernd Ruecker (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1448?page=com.atlassian.jira.plug... ] Bernd Ruecker commented on JBPM-1448: ------------------------------------- My approach to implement it is adding this code ClassLoader oldCl = Thread.currentThread().getContextClassLoader(); try { Thread.currentThread().setContextClassLoader( ClassLoaderUtil.getProcessClassLoader(processDefinition)); .... existing code ... } finally { Thread.currentThread().setContextClassLoader(oldCl); } to the following methods: - Action.execute - Decision.execute - TaskController.initializeVariables - TaskController.submitParameters - AssignmentHandler.performAssignmentDelegation These are all places where the ProcessClassLoader is used and fits with all Delegation use cases I remember. > jBPM does not initialise thread context classloader > --------------------------------------------------- > > Key: JBPM-1448 > URL: https://jira.jboss.org/jira/browse/JBPM-1448 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Reporter: Kevin Conner > Assignee: Tom Baeyens > Priority: Critical > Fix For: SOA 4.2 CP03, SOA 4.3, jBPM 3.3.0 GA > > > jBPM does not initialise the thread context classloader when executing actions within the process. > The outcome of this decision is that code executed within the context of this action will not have access to classes/resources in the par unless the action classloader is an explicit parameter. > One example of this is the RMI marshalling layer, which has an implication on JNDI lookups. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-850) Tasks with mail notification (notify="yes") fail if the assigned actor has no e-mail address.

by Ronald van Kuijk (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-850?page=com.atlassian.jira.plugi... ] Ronald van Kuijk commented on JBPM-850: --------------------------------------- ok, made a test for this. Really simple, but the bcc test fails... I think this might be because the SimpleSMTPServer does not support bcc or maybe it does, but the server only receives one message. I added a test with two recipients and also one message is 'received' then by the server, since only one message is sent to it. That you cannot see the bcc is *good* :-).... So the testframework is insufficient I think. Any comments before I commit my code? > Tasks with mail notification (notify="yes") fail if the assigned actor has no e-mail address. > --------------------------------------------------------------------------------------------- > > Key: JBPM-850 > URL: https://jira.jboss.org/jira/browse/JBPM-850 > Project: JBoss jBPM > Issue Type: Patch > Components: Core Engine > Affects Versions: jBPM 3.2.0 > Reporter: Bruno Dumon > Assignee: Tom Baeyens > Fix For: jBPM 3.3.0 GA > > Attachments: noaddress_mail_patch.txt > > > In our system, it can occur users have not configured an email address, in which case they should not (and cannot) receive email notifications. So our AddressResolver implementation returns a null email address in that case. > Currently this will make jBPM try to send a mail with no recipients, causing JavaMail to raise an exception. > The attached patch (against current CVS) changes things such that a mail is not send when there are no recipients. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-850) Tasks with mail notification (notify="yes") fail if the assigned actor has no e-mail address.

by Ronald van Kuijk (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-850?page=com.atlassian.jira.plugi... ] Ronald van Kuijk commented on JBPM-850: --------------------------------------- O/T, but I'm creating a test for this and I come over things like: assertTrue(server.getReceivedEmailSize() == 1); is there a reason for this instead of using assertEquals(1, server.getReceivedEmailSize()); ???? Ohh... and cvs should of course be svn > Tasks with mail notification (notify="yes") fail if the assigned actor has no e-mail address. > --------------------------------------------------------------------------------------------- > > Key: JBPM-850 > URL: https://jira.jboss.org/jira/browse/JBPM-850 > Project: JBoss jBPM > Issue Type: Patch > Components: Core Engine > Affects Versions: jBPM 3.2.0 > Reporter: Bruno Dumon > Assignee: Tom Baeyens > Fix For: jBPM 3.3.0 GA > > Attachments: noaddress_mail_patch.txt > > > In our system, it can occur users have not configured an email address, in which case they should not (and cannot) receive email notifications. So our AddressResolver implementation returns a null email address in that case. > Currently this will make jBPM try to send a mail with no recipients, causing JavaMail to raise an exception. > The attached patch (against current CVS) changes things such that a mail is not send when there are no recipients. -- 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

16 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues October 2008