You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently only one Camel config file (META-INF/jboss-camel-context.xml) can be contained in a deployment for EAP. It would be good to follow the convention form OSGi world where one bundle can contain several Camel config files. Let's say Camel configs could be stored in META-INF/jboss/ or better in the same location as Camel Spring config files in OSGi - META-INF/spring/ (easier migration from OSGi to EAP).
Some motivation for multiple Camel config files:
To enable development of Camel configs separately by different programmers/teams.
To make integration tests of Camel on EAP easier - minimalistic test deployments containing only the appropriate Camel config file could be created and deployed on EAP with using ShrinkWrap/Arquillian.
I belive that other use-cases/reasons for doing so exists because this functionality is already provided in OSGi environment. You can name them.
Currently only one Camel config file (
META-INF/jboss-camel-context.xml
) can be contained in a deployment for EAP. It would be good to follow the convention form OSGi world where one bundle can contain several Camel config files. Let's say Camel configs could be stored inMETA-INF/jboss/
or better in the same location as Camel Spring config files in OSGi -META-INF/spring/
(easier migration from OSGi to EAP).Some motivation for multiple Camel config files:
Tracked by ENTESB-2396
The text was updated successfully, but these errors were encountered: