I think this could be a binary incompatibility between the JSF jars against
which the jBPM webapp was build and the ones shipped in 4.0.3SP1. Try to build
the jBPM webapp with the dependencies you find in 4.0.3SP1. You will have to do
the same thing anyway if you want to deploy on Websphere...
I even wrote a InitializationServlet which binds the JbpmConfiguration
object to java:/jbpm/JbpmConfiguration jndi name.
(The readme file in starters kit, specifies that the jbpm service archive binds
the JbpmSessionFactory onto a jndi name. But the Mbean binds the
JbpmConfiguration object. )
Try adding ehcache-1.1.jar from lib/hibernate. You should probably move the
entire jbpm.sar directory to your JBoss installation rather than adding the
classes to every web application that uses jBPM.
The stack trace you posted seems incomplete - is there a cause printed below?
View the
Alex, Thanks for your quick reply
My ultimate aim is to run the jbpm sample webapp on Websphere. I thot it would
be better if I am able to make a war in plain vanilla jboss and then drop it
onto Websphere.
But still I am not able to get rid of all dependencies. The root cause of the
exception
