the problem posted by zoe occurs on what seems to be a jpdl process, so let me
focus on dhanush's problem first.
dhanush, when you say "api mode" are you invoking methods outside the
enterprise app (i.e. code not deployed inside jbpm-bpel.ear)? if you are, then
your app's ENC will not contain t
No Guys.
I am still having the Class Cast Exception. Any help is appreciated.
The problem is that my process instance is never shown as ended because of this
exception.
thanks
Dhanush
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241400#4241400
Reply to
I am also seeing the "org.jbpm.JbpmException: ejb timer entity lookup"
exception but it appears to be some sort of bootstrap issue. My process
definition has a decision node where one possible path goes to a task-node with
a task that has a timer. The other path does not have any timers. This
Were you able to resolve this error? Does anyone knows a solution to this
problem?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224792#4224792
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224792
_
Ok. I did some more research, added in web.xml of my application this snippet
| ejb/LocalTimerEntityBean
| Entity
| org.jbpm.ejb.LocalTimerEntityHome
| org.jbpm.ejb.LocalTimerEntity
| TimerEntityBean
|
and then added
Hi,
I got one more additional information here:
When I run the BPEL WS from SOAP-UI, the object of
EntitySchedulerServiceFactory is having its timerEntityHomeJndiName as
"java:comp/env/ejb/LocalTimerEntityBean" and the timerEntityHome object is
populated.
When I run the BPEL WS through API,
