[JBoss jBPM] - Re: Cannog get BPM-BPEL on jBoss AS 5.0
by sarishjain
Deployment was successful, but while executing the process on 5.0.1, partner service invocations are failing with this exception,
|
| org.jbpm.bpel.BpelException: no port implements the required port type: portType={http://jbpm.org/examples/ticket}TicketIssuer
| at org.jbpm.bpel.endpointref.SoapEndpointReference.selectPort(SoapEndpointReference.java:97)
| at org.jbpm.bpel.endpointref.SoapEndpointReference.selectPort(SoapEndpointReference.java:52)
| at org.jbpm.bpel.integration.jms.IntegrationControl.createCaller(IntegrationControl.java:261)
| at org.jbpm.bpel.integration.jms.JmsIntegrationService.invoke(JmsIntegrationService.java:162)
| at org.jbpm.bpel.integration.def.InvokeAction.execute(InvokeAction.java:75)
| at sun.reflect.GeneratedMethodAccessor403.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:197)
| at org.jbpm.graph.def.Action_$$_javassist_149.execute(Action_$$_javassist_149.java)
| at org.jbpm.graph.def.GraphElement.executeAction(GraphElement.java:259)
| at org.jbpm.graph.def.Node.execute(Node.java:335)
| at org.jbpm.bpel.graph.def.Activity.enter(Activity.java:123)
| at org.jbpm.graph.def.Transition.take(Transition.java:151)
| at org.jbpm.graph.def.Node.leave(Node.java:390)
| at org.jbpm.bpel.graph.def.Activity.proceed(Activity.java:241)
| at org.jbpm.bpel.graph.def.Activity.leave(Activity.java:229)
| at org.jbpm.bpel.graph.basic.Receive.messageReceived(Receive.java:53)
| at sun.reflect.GeneratedMethodAccessor399.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:197)
| at org.jbpm.bpel.graph.basic.Receive_$$_javassist_19.messageReceived(Receive_$$_javassist_19.java)
| at org.jbpm.bpel.integration.def.ReceiveAction.deliverMessage(ReceiveAction.java:98)
| at sun.reflect.GeneratedMethodAccessor396.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:197)
| at org.jbpm.bpel.integration.def.ReceiveAction_$$_javassist_92.deliverMessage(ReceiveAction_$$_javassist_92.java)
| at org.jbpm.bpel.integration.jms.StartListener.deliverRequest(StartListener.java:219)
| at org.jbpm.bpel.integration.jms.StartListener.onMessage(StartListener.java:165)
| at org.jboss.jms.client.container.ClientConsumer.callOnMessage(ClientConsumer.java:229)
| at org.jboss.jms.client.container.ClientConsumer$ListenerRunner.run(ClientConsumer.java:1043)
| at org.jboss.messaging.util.OrderedExecutorFactory$ChildExecutor.run(OrderedExecutorFactory.java:120)
| at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
| at java.lang.Thread.run(Thread.java:613)
|
|
May be some code fix is required within the BPEL source files
Not the invocation of that service (configured to be invoked as part of the workflow) worked
| Call call = createCall("http://localhost:8080/ticket/ticketIssuer","http://jbpm.org/examples/ticket","createTicket");
| String ret = (String) call.invoke(new Object[] { });
|
| System.out.println("Sent 'Hello!', got '" + ret + "'");
|
Any pointers on this one?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224770#4224770
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224770
17 years, 2 months
[JBoss jBPM] - Re: Timer on node clarification
by o_lion
Sorry
But i configure the scheduler with:
| <service name='scheduler' factory='org.jbpm.scheduler.db.DbSchedulerServiceFactory' />
|
| <bean name='jbpm.job.executor' class='org.jbpm.job.executor.JobExecutor'>
| <field name='jbpmConfiguration'><ref bean='jbpmConfiguration' /></field>
| <field name='name'><string value='JbpmJobExecutor' /></field>
| <field name='nbrOfThreads'><int value='1' /></field>
| <field name='idleInterval'><int value='1000' /></field>
| <field name='maxIdleInterval'><int value='3600000' /></field> <!-- 1 hour -->
| <field name='historyMaxSize'><int value='20' /></field>
| <field name='maxLockTime'><int value='600000' /></field> <!-- 10 minutes -->
| <field name='lockMonitorInterval'><int value='60000' /></field> <!-- 1 minute -->
| <field name='lockBufferTime'><int value='5000' /></field> <!-- 5 seconds -->
| </bean>
|
It's right?
The timer don't change the state if the time of action over timer's time.
Thanks in advanced
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224724#4224724
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224724
17 years, 2 months
[JBoss jBPM] - Re: Instance Scoped Groups
by akriel
"kukeltje" wrote :
| anonymous wrote :
| | To clarify what I'm talking about, imagine a develop new software process. In general the same groups/people will handle each task. However assume that you have multiple contractors working at your company. These contractors need to be added on a per instance basis, because they are only contributing to the specific instance, not to every new instance of the process.
|
| As mentioned before, you can use swimlanes for this
Thanks for your response.
I'm still trying to get a handle on what changes effect the process definition and which effect only the process instance. It sounds like your telling me I can add users to the specific tasks pooled actors without effecting the overall process definition. This would take the place of creating temporary groups!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224720#4224720
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224720
17 years, 2 months
[JBoss jBPM] - Re: Instance Scoped Groups
by kukeltje
anonymous wrote : I am evaluating Jbpm as a possible solution for a new project. Although in general users often belong to specific groups, it is possible on the instance level that a user may need to be added/removed from a group for that instance only.
No
anonymous wrote : Based on what I've seen looking at the jbpm source code something like this would have to be an extension, and is not currently supported. Have I missed something or is this an accurate statement?
|
It is accurate
anonymous wrote : Assuming I'm right about this not currently being supported, is this a feature the community would use? or does this seem like an uncommon requirement?
|
I would not, since I can always add the individual actorid to the pooledactors list, besides the basic groupname for the* swimalaneinstance*
anonymous wrote :
| To clarify what I'm talking about, imagine a develop new software process. In general the same groups/people will handle each task. However assume that you have multiple contractors working at your company. These contractors need to be added on a per instance basis, because they are only contributing to the specific instance, not to every new instance of the process.
As mentioned before, you can use swimlanes for this
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224708#4224708
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224708
17 years, 2 months
[JBoss jBPM] - Instance Scoped Groups
by akriel
I am evaluating Jbpm as a possible solution for a new project. Although in general users often belong to specific groups, it is possible on the instance level that a user may need to be added/removed from a group for that instance only.
Based on what I've seen looking at the jbpm source code something like this would have to be an extension, and is not currently supported. Have I missed something or is this an accurate statement?
Assuming I'm right about this not currently being supported, is this a feature the community would use? or does this seem like an uncommon requirement?
To clarify what I'm talking about, imagine a develop new software process. In general the same groups/people will handle each task. However assume that you have multiple contractors working at your company. These contractors need to be added on a per instance basis, because they are only contributing to the specific instance, not to every new instance of the process.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224704#4224704
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224704
17 years, 2 months
[JBoss jBPM] - Re: Timer on node clarification
by o_lion
Ops, my right xml process is:
<?xml version="1.0" encoding="UTF-8"?>
|
| <process-definition xmlns="urn:jbpm.org:jpdl-3.2"
| name="getIpAddressToMsisdn">
| <swimlane name="parameters"></swimlane>
|
| <start-state name="init">
| <task swimlane="parameters">
| <controller>
| <variable access="read,write,required" name="inputsBean"></variable>
| </controller>
| </task>
| <transition to="node1"></transition>
| </start-state>
|
| <node name="node1">
| <action name="callMsisdn" class="com.nsn.npc.jbpm.util.BeanActionHandler">
| <mBeanServiceName>
| com.nsn.npc.adapter:service=AlAdapter
| </mBeanServiceName>
| <methodName>
| getMsisdn
| </methodName>
| </action>
| <timer duedate="10 seconds" name="timeout" transition="to finish">
| <action></action>
| </timer>
| <transition to="finish" name="to finish"></transition>
| </node>
| <end-state name="finish"></end-state>
|
| </process-definition>
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224689#4224689
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224689
17 years, 2 months