June 2009 - jboss-dev-forums - Jboss List Archives

[Design of JBoss ESB] - Re: Problems with transmitting content from ESB to jBPM via

by camunda

Hi. First @Andre: I think what Kevin meant is, that if you use the action mep="RequestResponse" in the service you call from the process the JbpmCallback is triggered outomatically, you don't have to code that yourself. But this is a different use case. There the Callback works as expected out-of-the-box without problems. Kevin wrote : | Okay, that explains things. It is the correlation between the internal EPR and external services that we are currently missing. | +1!!! This is what I raised already a couple of times: Removing the SignalCommand befor this problem is solved. I think there we should come up with some working solution shortly and document it properly. What do you think Kevin? And for integrating jbpm 4 we should find a really decent correlation mechanism :-) Cheers Bernd View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238759#4238759 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238759

16 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: EJB 2.1 Beans in jbpm 4?

by camunda

+1 Maybe Commands are still the best way to go there (sorry Tom for insisting on liking the Commands ;-)). Or other ideas how this can be tackled via the API in a good manner? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238757#4238757 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238757

16 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Undeployment in JBosss Deployer

by camunda

Heiko. anonymous wrote : | would expect a process deployment artifact to contain all the classes and resources a process requires for execution. So, if you rely on the classloader you receive from the AS deployer framework and the the deployment artifact get's removed, then you basically leave the process in an unusable state. | Right, this is why it is suspended. So it cannot be signaled any more. anonymous wrote : | Hence it can be deleted right away, IMO. | Not right, because we just don't want to delete the unfinished process instances. anonymous wrote : | But of course, if you keep writing class information to the database and deal with classloading and scoping on your own then you don't have this problem in the beginning. But I don't believe you easily leverage advanced AS features if you keep providing custom solutions for things that the AS already provides. | This has nothing todo with it. I agree, classes should go in the ear or whatever. See answer above. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238756#4238756 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238756

16 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: EJB 2.1 Beans in jbpm 4?

by kukeltje

Oh.. yes, that is for sure the case. That is why I posted it. I'll need this in several cases in my apps. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238755#4238755 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238755

16 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Transaction interceptor changes

by heiko.braun＠jboss.com

https://jira.jboss.org/jira/browse/JBPM-2344 I consider this a blocking issue. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238754#4238754 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238754

16 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Transaction interceptor changes

by camunda

I already tackled that problem, but I saw I just send it to Tom via Mail and forgot the mailing list, sorry... Here the JIRA issue for it: https://jira.jboss.org/jira/browse/JBPM-2339 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238752#4238752 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238752

16 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Transaction interceptor changes

by heiko.braun＠jboss.com

For completeness, here's the Deployer error: | Caused by: org.jbpm.api.JbpmException: couldn't lookup 'java:comp/UserTransaction' from jndi: UserTransaction not bound: UserTransaction not bound | at org.jbpm.pvm.internal.tx.jta.JtaTransaction.lookupFromJndi(JtaTransaction.java:131) | at org.jbpm.pvm.internal.tx.jta.JtaTransaction.lookupJeeUserTransaction(JtaTransaction.java:110) | at org.jbpm.pvm.internal.tx.jta.JtaTransactionInterceptor.execute(JtaTransactionInterceptor.java:46) | at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:54) | at org.jbpm.pvm.internal.repository.DeploymentImpl.deploy(DeploymentImpl.java:91) | at org.jbpm.integration.spi.DeploymentAdaptor.deploy(DeploymentAdaptor.java:62) | | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238749#4238749 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238749

16 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Transaction interceptor changes

by heiko.braun＠jboss.com

@Tom: Btw, if you would have kept the integration tests I did provide a while ago, this would have occurred in the nightly QA. So I'd say the current integration tests are insufficient. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238748#4238748 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238748

16 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Transaction interceptor changes

by heiko.braun＠jboss.com

Most recent TX interceptor changes, break the console and the deployer: | Caused by: org.jbpm.api.JbpmException: invalid transaction state: STATUS_ACTIVE | at org.jbpm.pvm.internal.tx.jta.JtaTransactionInterceptor.execute(JtaTransactionInterceptor.java:60) | at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:54) | at org.jbpm.pvm.internal.repository.RepositoryServiceImpl.createProcessDefinitionQuery(RepositoryServiceImpl.java:77) | at org.jbpm.integration.console.ProcessManagementImpl.getProcessDefinitions(ProcessManagementImpl.java:54) | ... 45 more | | Basically you cannot run within a provided transaction context (like ejb REQUIRED semantics). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238746#4238746 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238746

16 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Undeployment in JBosss Deployer

by heiko.braun＠jboss.com

I would expect a process deployment artifact to contain all the classes and resources a process requires for execution. So, if you rely on the classloader you receive from the AS deployer framework and the the deployment artifact get's removed, then you basically leave the process in an unusable state. Hence it can be deleted right away, IMO. But of course, if you keep writing class information to the database and deal with classloading and scoping on your own then you don't have this problem in the beginning. But I don't believe you easily leverage advanced AS features if you keep providing custom solutions for things that the AS already provides. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238744#4238744 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238744

16 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums June 2009