This is most likely due to a different deployment structure (and also an open JIRA task,
see JBPM-836). I suppose you have jbpm-enterprise.ear and jbpm-console.war (or your custom
jbpm web app) deployed separately, ie not in a nested structure. Deploy the war nested
inside the ear and the local reference to TimerServiceBean can be resolved.
Regards, Martin
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043619#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...