Given that this is big addition to app server i don't think it should be present in WildFly codebase.
This subsystem introduces handful of dependencies that would greatly increase our distribution size and potentially cause problems because of bundled Spring.

I think we should split out this new Camel subsystem together with OSGI & friends to its on repository (project maybe?)
and that they should be provided as add-ons/layers to core application server.
This is same thing that many other projects like CapeDwarf, TorqueBox, Gatein, Escalante, Teiid and many more are already doing.

It would also make sense that we would in the end provide two bundles to be downloaded from WildFly website, one with default "core" application server and another with many bundled addons/layers that users could use.

This way I think we should satisfy all needs from both teams.

To be fair, I am not saying this new subsystem not good addition to what we need to provide users, but I just don't think it should be part of core WildFly.

We also discussed in past that we should split many other functionalities in to similar layers/add-ons and really have WildFly core and lets say EE7 layer. but that is subject for some other time.


On Wed, Apr 24, 2013 at 1:15 PM, Thomas Diesler <> wrote:
Hi Folks,

I'm happy to announce that the initial Camel subsystem is now available


Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat

jboss-as7-dev mailing list