[SM-1977] Support exploded JBI artifacts

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Fix Version/s: 3.4.0
• Component/s: servicemix-core
• Assignee: Jean-Baptiste Onofré
• Reporter: Jean-Baptiste Onofré
• Created: 17/Sep/10 06:48
• Updated: 10/Mar/11 08:57
• Resolved: 18/Feb/11 10:43

Description

For example, in JBoss application server, you can deploy JEE artifacts in an exploded format.
In place of deploying a file my.ear or my.war, you can deploy a directory my.ear or my.war. The JBoss deployer is able to see in the resource is a ZipEntry or a Directory.

I could be interesting to do the same in the ServiceMix and NMR deployer around JBI artifacts.
The users could be able to deploy a sa.zip directory containing su.zip directories.

Like this, it's possible to easily change the xbean.xml without repackaging and regenerating the zip files.

To achieve this, we need:

• to upgrade the deployer in ServiceMix 3 and NMR to detect if the artifact is a ZipEntry or a directory
• to upgrade the jbi-maven-plugin to provide an exploded JBI artifact (without the zip packaging)