SOA Platform ships at least 2 jbpm-jpdl.jars:
- seamfp\lib\jbpm-jpdl.jar - this one is included with any MySeamApp.ear that is created
- jboss-as\server\default\deploy\jbpm.esb\jbpm-jpdl.jar - this one is already "in container"
If you take Seam DVDStore and include a use of EsbNotifier or EsbActionHandler in its JPDL (e.g. ordermanagement1.jpdl.xml) like so:
<action name="ShipItAction" class="org.jboss.soa.esb.services.jbpm.actionhandlers.EsbNotifier">
The result is a classcastexception since we have two copies of jBPM