Hi all,
i like to deploy camel-routes and features inside the deploy directory.
A deployment look like the following:
- a feature.xml which contain bundles like Apache Camel, Spring with a start
level definition.
- and many xml camel-routes which contain configurations for my components.
Now
I've seen lots of problems when using spring-dm, some of them do not
have any clean solution *at all*, especially when using custom
namespace handlers such as camel. That's why I've been advocating for
using blueprint instead, which works way better.
Camel support for blueprint is much better
One solution I can come up with which might not be graceful but
working is that in your xml camel-routers hold a osgi reference
exposed by the camel component you want to wait, this can ensure the
camel components fully started before your customer router bundle.
For example if you need
'm just now moving a project to blueprint, here is an example camel setup that
works really well (Thanks jgenender)
This is using aries JNDI/transaction and persistence.
?xml version=1.0 encoding=UTF-8?
blueprint default-activation=lazy
