Unfortunately, one more issue.
Definition of dependencies in -service.xml has one uncomfortable consequence - application EAR is needed to be deployed exploded. I don't know how to define dependency of service to JAR within packed EAR. This issue I'll need to solve anyway, even if my ESB services will be inside the EAR archive (jbpm.esb has to define dependency on JARs, where are custom action classes for our deployed processes).
The helloworld_hibernate_action has an example of how to build an EAR and how to set it up - can you take a look at that? I'm a little confused with what you are doing here - can you take a look at that quickstart and then rephrase your questions?
Did you ever find a way to resolve these deployment issues? I am having the same type of problems of wanting to deploy me .esb archive within the ear file.
I finally manged to include an esb-archive inside the ear archive.
The trick is to read the maven ear plugin Configuration|Modules page til the end: "Adding Custom Artifact Types".
I'm using following pom:
<artifactTypeMapping type="esb" mapping="jar" />
You see the trick is to define the artifactTypeMapping, and including the esb artifact as jarModule.
Moreover the option includeApplicationXml=true gurantees that there is an esb-entry in the generated application.xml.
The unpack=true is just a matter of taste, i prefer to include the esb as exploded dir.