[jBPM Users] - Re: Problem moving from 4.1 to 4.2 using Spring configuratio
by saraswati.santanu
Suganda,
It will be helpful if you can upload a sample jpdl you want to execute and a small code snippet that can deploy and start that flow.
It is difficult to conclude anything by looking at the stack trace. But the root of the exception suggests some missing tables.
| Factory method [public org.jbpm.api.ProcessEngine org.jbpm
| .pvm.internal.cfg.SpringConfiguration.buildProcessEngine()] threw exception; nested exception is org
| .jbpm.api.JbpmException: no jBPM DB schema: no JBPM4_EXECUTION table. Run the create.jbpm.schema t
| arget first in the install tool.
|
So make sure that the schema for JBPM is created properly.
As for spring-transaction-interceptor, I would say it is okay to use current=false. In fact I prefer not to set current=true. current=true expects a transaction to be present, while as current=false creates a transaction if it does not exists, and uses the existing one if already exists. In short current=true means propagation behaviour MANDATORY and current=false means propagation behaviour REQUIRED.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268619#4268619
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268619
14 years, 7 months
[JBoss Web Services Users] - Failed to load org.jboss.wsf.spi.invocation.WebServiceContex
by pa12399
Hi
I updated the WS native stack on JBoss 4.2.3 with jbossws-native-3.1.1GA. I am trying to deploy my webservices and I am getting all exceptions in server.log
2009-12-02 13:33:40,372 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider] provide SPI 'class org.jboss.wsf.spi.management.ServerConfigFactory'
2009-12-02 13:33:40,373 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider] class org.jboss.wsf.spi.management.ServerConfigFactory Implementation: org.jboss.wsf.framework.management.ServerConfigFactoryImpl@4d4d5e
2009-12-02 13:33:40,373 DEBUG [org.jboss.wsf.stack.jbws.WSDLFilePublisher] Publish WSDL file: file:/opt/vzw/webserver/jboss-4.2.3.GA/server/provapi-ws/tmp/jbossws/OnstarServiceRequestsService403.wsdl
2009-12-02 13:33:40,431 INFO [org.jboss.wsf.stack.jbws.WSDLFilePublisher] WSDL published to: file:/opt/vzw/webserver/jboss-4.2.3.GA/server/provapi-ws/data/wsdl/OnstarWebService.war/OnstarServiceRequestsService403.wsdl
2009-12-02 13:33:40,448 DEBUG [org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl] ServiceEndpointInvokerDeploymentAspect:Create
2009-12-02 13:33:40,467 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider] provide SPI 'class org.jboss.wsf.spi.invocation.WebServiceContextFactory'
2009-12-02 13:33:40,472 ERROR [org.jboss.deployment.MainDeployer] Could not start deployment: file:/opt/vzw/webserver/jboss-4.2.3.GA/server/provapi-ws/deploy/OnstarWebService.war
java.lang.IllegalStateException: Failed to load org.jboss.wsf.spi.invocation.WebServiceContextFactory: org.jboss.wsf.container.jboss42.WebServiceContextFactoryImpl
at org.jboss.wsf.spi.util.ServiceLoader.loadFromServices(ServiceLoader.java:97)
at org.jboss.wsf.spi.util.ServiceLoader.loadService(ServiceLoader.java:59)
at org.jboss.wsf.framework.DefaultSPIProvider.loadService(DefaultSPIProvider.java:155)
at org.jboss.wsf.framework.DefaultSPIProvider.getSPI(DefaultSPIProvider.java:140)
at org.jboss.ws.core.server.ServiceEndpointInvoker.(ServiceEndpointInvoker.java:101)
at org.jboss.wsf.stack.jbws.ServiceEndpointInvokerDeploymentAspect.create(ServiceEndpointInvokerDeploymentAspect.java:56)
at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy41.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor50.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268617#4268617
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268617
14 years, 7 months
[jBPM Users] - Re: How to suspend Join Execution
by pradeep.gulla
Hi Santanu,
The code: taskService.deleteTask(task.getId()); throwing exception
tasks related to an execution must be completed. they cannot just be deleted
My Implementation:
Process XML:
| <process name="test_workflow" version="4" xmlns="http://jbpm.org/4.0/jpdl">
| <start g="15,390,80,40">
| <transition to="validate approval sequence"/>
| </start>
| <decision name="validate approval sequence" expr="${approvalSequence}">
| <transition name="parallel" to="assign parallel tasks"/>
| <transition name="seqential" to="first sequential Task"/>
| </decision>
| <fork name="assign parallel tasks">
| <transition to="first parallel task"/>
| <transition to="second parallel task"/>
| <transition to="third parallel task"/>
| </fork>
| <task name="first parallel task">
| <transition to="wait"/>
| <transition name="rework" to="disable all active tasks"/>
| </task>
| <task name="second parallel task">
| <transition to="wait"/>
| <transition name="rework" to="disable all active tasks"/>
| </task>
| <task name="third parallel task">
| <transition to="wait"/>
| <transition name="rework" to="disable all active tasks"/>
| </task>
| <join name="wait">
| <transition to="first sequential task"/>
| </join>
| <task name="first sequential Task">
| <transition name="approve" to="second sequential Task"/>
| </task>
| <task name="second sequential Task">
| <transition name="approve" to="stop"/>
| </task>
| <!-- Should disable all active parallel tasks -->
| <custom name="disable all active tasks" class="ReworkHandler">
| <transition to="rework task"/>
| </custom>
| <task name="rework task">
| <transition name="restart" to="validate approval sequence"/>
| </task>
| <end name="stop"/>
|
Handler class:
| public class ReworkHandler implements ExternalActivityBehaviour{
| public void execute(ActivityExecution execution) {
| ..................
| taskService.deleteTask(task.getId());
| }
| }
Am I' missing anything ??
.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268608#4268608
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268608
14 years, 7 months
[jBPM Users] - Re: Variable missing in assignment handler
by nizzy
"Implicit is possible by extending and overriding the subprocess node implementation."
--
Why are super-process variables not by default copied into the sub-process?
Am I missing something or is this not the behaviour what most people require, should it not be included as part of Jboss JBPM core functionality?
It may just be the way we use JBPM but I always want the super-process variables to be available to the sub-process, without having to worry about overriding SubprocessNode implementation!
Indeed it is counter-intuitive that they are not available.
Defining them in the process definition is IMO not the best way to achieve this; since a dependecny is introduced between the business logic layer and the process definition xml.
I assume there is a very good reason for this limitation?
Could someone enlighten me please!!!!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268592#4268592
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268592
14 years, 7 months