Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide multiple Camel config files per deployment #206

Closed
trohovsky opened this issue Dec 18, 2014 · 0 comments
Closed

Provide multiple Camel config files per deployment #206

trohovsky opened this issue Dec 18, 2014 · 0 comments
Assignees
Labels
Milestone

Comments

@trohovsky
Copy link

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.

Tracked by ENTESB-2396

@tdiesler tdiesler modified the milestone: 2.2.0 Jan 27, 2015
@tdiesler tdiesler changed the title Provide multiple Camel config files per deployment on EAP Provide multiple Camel config files per deployment Feb 3, 2015
@tdiesler tdiesler self-assigned this Feb 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants