Ah I understand better now :D
But the way I see it, if you could work out more complex stuff in your
routes (other than setting headers), things become more interesting.
But at the end of the day, this proposal will make things easier for the
developer community, I think the business analyst
This is a pretty neat idea, I was actually around when you were explaining
your need.
Thing is we are not really far from what you want to achieve if we use the
bean component or if the proxy pattern is applied.
It all boils down the extent to which you want to make things easier for the
users.
The webconsole is not picking your routes because you're not telling it to :D
If you only change the packaging of your pom to war and add the camel-web
dependency,
the application context will load a provided sample applicationContext.xml,
but if you already provide a web application folder
Hello Community,
When I run the following
mvn archetype:generate -DarchetypeGroupId=org.apache.camel.archetypes
-DarchetypeArtifactId=camel-archetype-java -DarchetypeVersion=2.1.0
-DgroupId=com.corp.projects -DartifactId=camel-jira-ws
Everything looks ok, but glancing at the generated pom.xml in
Use templating instead, in Camel, among the components available in Camel,
try Velocity:
http://camel.apache.org/velocity.html
titexe wrote:
Hello,
I want to generate an XML File based on the fiels of the header of Message
and the body of message.
An example of the file that i want to
Hello Camel Riders,
I wanted to tryout some of the examples bundled with the current
downloadable distribution of Camel (2.0.0)
Maven fails, but I have pinpointed the culprit; in each example, the parent
pom (which can be found in the examples directory) is referenced this way:
, 2009 at 6:52 AM, Ryadh Amar
magnetic.gan...@gmail.comwrote:
Hello Camel Riders,
I wanted to tryout some of the examples bundled with the current
downloadable distribution of Camel (2.0.0)
Maven fails, but I have pinpointed the culprit; in each example, the
parent
pom (which can be found
Hi,
You can use the following, using the onException construct:
=
onException(javax.naming.NamingException.class).maximumRedeliveries(3)
.to(seda:errors);
