You should also have a look into the Camel OSGI integration tests [1] which
use pax exam to test Camel in an OSGI environment.
[1]
https://svn.apache.org/repos/asf/camel/trunk/tests/camel-itest-osgi/src/test/java/org/apache/camel/itest/osgi/
Best,
Christian
On Wed, May 9, 2012 at 8:44 AM, Claus
On Tue, May 8, 2012 at 8:14 PM, James Carman wrote:
> Can we introduce this advice using blueprint XML? I'm trying to set up
> simple examples that the testing folks can use to add this stuff into
> existing routes. Is that possible?
>
Yes from Camel 2.10 onwards we got a camel-test-blueprint c
Can we introduce this advice using blueprint XML? I'm trying to set up
simple examples that the testing folks can use to add this stuff into
existing routes. Is that possible?
--
View this message in context:
http://camel.465427.n5.nabble.com/Integration-Testing-Best-Practices-tp5691310p5695537
We are using Jenkins for our continuous integration. We have not set it up
to auto-deploy anything to the integration environment as of yet (guidance
on that with ServiceMix/OSGi would be helpful :). We are merely using it to
run our unit tests, deploy snapshots to Nexus, and publish build inform
Hi James,
I am working through the exact same issue as you are now. One thing that
has been really worthwhile to look into is 'adviceWith':
http://camel.apache.org/advicewith.html
You can weave around particular endpoints and either replace the endpoint or
intercept the messages in and out of th
