Page History

...

We continue from part 4 where we have the routing in place. However as you might have noticed we aren't quiet there yet with a nice solution, we are still coding to much. In this part we will look into to address these two concerns:

• Starting Camel automatically
• Using CXF directly

Starting Camel automatically

...

There are two solutions to this

• using spring bean
• package scanning

Using a spring bean we just declare the route builder using a regular spring bean:

...

So now we have two spring XML files

• cxf-config.xml
• camel-config.xml

And since cxf-config.xml is dependent on camel-config.xml we need to have correct ordering in our web.xml where we have defined the XML files to load by Spring. So we set the camel-config.xml before the cxf-config.xml so Spring have created the SpringCamelContext and registered it in its registry with the id = camel.

...

Okay now we are ready to turn our attention to using CXF directly in Camel routing. So we zap ReportIncidentEndpointImpl as we no longer need this code. So what's left is:

• FilenameGenerator.java
• ReportIncidentRoutes.java
  And that is all what's needed, well for now...

The goal is to replace the previous staring endpoint ("direct:start") to the new starting CXF endpoint.

...

In the next part's look at using XML to create the route instead of Java code. Then it might be even more readable by non developers.

Links

• Introduction
• Part 1
• Part 2
• Part 3
• Part 4
• Part 5
• Part 6