On Thu, Oct 8, 2009 at 5:51 PM, erh ehas...@transunion.com wrote:
Claus Ibsen-2 wrote:
Thanks I can see its the new OSGi blueprint support that causes some
maven issues.
Will disable this until blueprint works completely.
Well, the build worked, but some tests failed, and I guess that
On Mon, Oct 5, 2009 at 7:32 PM, erh ehas...@transunion.com wrote:
Claus Ibsen-2 wrote:
Hi
I have just backported a fix for CAMEL-1878 to 1.x as well.
You are welcome to try with a new 1.6.2-SNAPSHOT whether it fixes your
bean problem.
Do the snapshots get built automatically? The
Claus Ibsen-2 wrote:
On Mon, Oct 5, 2009 at 7:32 PM, erh ehas...@transunion.com wrote:
Do the snapshots get built automatically? The dates on the files in the
1.6.2-SNAPSHOT directory are a bit odd. The md5 and sha1 files have a
timestamp from October 4th, but the tarballs are from
Claus Ibsen-2 wrote:
Hi
I have just backported a fix for CAMEL-1878 to 1.x as well.
You are welcome to try with a new 1.6.2-SNAPSHOT whether it fixes your
bean problem.
Do the snapshots get built automatically? The dates on the files in the
1.6.2-SNAPSHOT directory are a bit odd.
Hi
I have just backported a fix for CAMEL-1878 to 1.x as well.
You are welcome to try with a new 1.6.2-SNAPSHOT whether it fixes your
bean problem.
On Fri, Oct 2, 2009 at 6:01 PM, erh ehas...@transunion.com wrote:
I'm having trouble getting the methodName to work when routing to a bean
using
Hi
Use processRef ref=foo/
To invoke the Processor which then will invoke the process(Exchange) method.
On Fri, Oct 2, 2009 at 6:01 PM, erh ehas...@transunion.com wrote:
I'm having trouble getting the methodName to work when routing to a bean
using a route like this:
route
from
