On Thu, Oct 8, 2009 at 5:51 PM, erh 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 means th
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 means the
tarball didn't get over to repository.apache.org. :(
On Wed, Oct 7, 2009 at 7:44 PM, erh wrote:
>
>
> Claus Ibsen-2 wrote:
>>
>> On Mon, Oct 5, 2009 at 7:32 PM, erh 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
Claus Ibsen-2 wrote:
>
> On Mon, Oct 5, 2009 at 7:32 PM, erh 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 September 29th and
>
On Mon, Oct 5, 2009 at 7:32 PM, erh 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 dat
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 bi
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.
>
>
Thanks! I'll give it a shot.
eric
--
View this message in context:
http://www.nabble.com/using-methodN
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 wrote:
>
> I'm having trouble getting the methodName to work when routing to a bean
> using a route like this:
Hi
Use
To invoke the Processor which then will invoke the process(Exchange) method.
On Fri, Oct 2, 2009 at 6:01 PM, erh wrote:
>
> I'm having trouble getting the methodName to work when routing to a bean
> using a route like this:
>
>
>
>
>
> foo is a bean that implements Processor [
I'm having trouble getting the methodName to work when routing to a bean
using a route like this:
foo is a bean that implements Processor [*2], and in some routes I want it
to use the process() method, but in this case I need to use a different
entry point. According to http://camel.a
10 matches
Mail list logo