Hello,
I am trying to use Camel using the pure Java approach (Java DSL, no DI
framework, no URI Strings).
My approach so far is like the simplistic sample below, but I am not sure
if it uses proper practices.
Can you please let me know if/what problems you see with this approach?
Is there maybe
Hi everyone,
I calculated a message digest value using DigestUtils.sha1Hex(String value),
which gave me a long string of about 40 characters (e.g
dd543d3bcb28e577313f8b945f29a9be7a43c5fd).
I needed to pass this messageDigest value to my internal camel component
which in turn is supposed to write
That brought me on the right track:
@Before
public void setupContext() throws Exception{
// Disable timer route so it can not pop while running tests
context().stopRoute("metar-provider-timer");
context.getRouteDefinition("metar-provider-formatter").adviceWith(con
OK I simplified the test (removed xml read, set header with xpath etc) and got
the test pass.
I used "mockEndpointsAndSkip" in the setup and "getMockEndpoint" instead of an
instance variable mock.
Hope you can adapt it for your (complete) case.
Stephan
@Produce(uri = "direct:METARformatte
Hallo Stephan,
yes I already tried and just had another run, does not change a thing
(also tried with completely different mock endpoint just to be sure).
Let me also use this opportunity to attach a few lines from the unittest run:
[ main] BlueprintCamelContext
Just a quick guess to try: have you tried to replace the "to(output)" with
"to("mock:outputFromFormatter")"?
Cheers
Stephan
-Ursprüngliche Nachricht-
Von: Lukas Winkler [mailto:winklerlu...@gmail.com]
Gesendet: Mittwoch, 2. August 2017 11:10
An: users@camel.apache.org
Betreff: AdviceWi
Dear list,
starting out with Camel and run into a problem when trying to test
part of my camel context.
Please find the test code as well as a snipped of the 'to test' route
in the following gist:
https://gist.github.com/ingwinlu/bb047cc409fb295b8d74b617ae04008c
>From the logs that are running I
