Thank you! That was the case - I had to add reference into my route
blueprint:
And now it works fine.
--
View this message in context:
http://camel.465427.n5.nabble.com/ServiceMIx-Camel-JDBC-MySql-javax-sql-DataSource-not-found-tp5715323p5715332.html
Sent from the Camel - Users mailing list ar
You can use EasyMock, you just have to add your mock objects to the
"registry." Works like a charm. You do have to do some gymnastics
with your route builder test superclass to get all the syntactic sugar
you get with EasyMock. You can refer to this code if you want:
https://github.com/jwcarman
+1 for the dummy processor.
But I think using the EasyMock can set the behavior of the message
which will be used to verify the choice processor.
On Mon Jul 2 00:43:27 2012, Christian Müller wrote:
A much more simpler approach from my point of view is providing a dummy
"MyProcessor" in the re
Mock objects came about because people were sick of doing dummy objects.
Dummy objects aren't flexible enough
Sent from tablet device. Please excuse typos and brevity.
On Jul 1, 2012 12:43 PM, "Christian Müller"
wrote:
> A much more simpler approach from my point of view is providing a dummy
>
Could you solve your problem?
If not, feel free to raise a JIRA (and attach a test if possible) so we can
work on this.
Best,
Christian
On Fri, May 18, 2012 at 11:22 AM, sekaijin wrote:
> So
>
> Christian Mueller wrote
> >
> > It depends on your runtime environment, which Registry is used:
> > -
A much more simpler approach from my point of view is providing a dummy
"MyProcessor" in the registry (Simple or Spring based). Than you can test
your route logic in isolation without testing (again) your "MyProcessor".
And it's much more light weigh than using EasyMock...
Best,
Christian
On Sun,
It depends on "SomeEndpoint"...
The message exchange pattern (MEP) is bound to the exchange, not the
enpoint itself.
Each component has a default MEP which is e.g. InOnly for the File
Component, InOut for the HTTP Component, ...
This MEP is used by creating the exchange in the component which recei
Or you use a properties placeholder and provide different endpoint URI's
for your test environment.
Best,
Christian
On Sun, Jul 1, 2012 at 9:36 AM, Claus Ibsen wrote:
> Hi
>
> Yeah I suggest to read these couple of links
> http://camel.apache.org/advicewith.html
> http://camel.apache.org/mock
>
Hi
I have a route which looks like:
from("MyEndpoint").to("bean:MyProcessor").choice().when(*header("HeaderField").equals("Field1")*).when(*header("HeaderField").equals("Field2")*)
The bean MyProcessor sets the "HeaderField". In my camel junit test class I
load this exsting route. I would li
Hi
Yeah I suggest to read these couple of links
http://camel.apache.org/advicewith.html
http://camel.apache.org/mock
For example the advice with allows you to manipulate the routes before
unit testing.
And mock allows to mock endpoints by pattern, and whether to skip
sending to the target endpoin
Hi
I was reading how camel supports unit testing of an existing RouteBuilder
class.
I think this is very useful as I don't want to have to duplicate the route
in the unit test.
However, suppose the route defined in the existing RouteBuilder class
contains an endpoint that I need to mock. Is th
Hi
So if I have the following 2 routes:
from(SomeEndpoint).to("seda:endpoint");
from("seda:endpoint".to(SomeOtherpoint");
I have not specified the exchange pattern for the SEDA endpoint. Hence, does
it default to something?
Thanks
--
View this message in context:
http://camel.465427.n5.nabble
12 matches
Mail list logo
