You can use the same API (ProducerTemplate and ConsumerTemplate) that
you found.
Willem
honno wrote:
Yes.We can send and receive messages to the remote camel server with some
components(camel-jms,camel-cxf...),but i want to kown that which camel
client api i can use to access remote camel serv
On Thu, Dec 24, 2009 at 8:06 AM, honno wrote:
>
> Yes.We can send and receive messages to the remote camel server with some
> components(camel-jms,camel-cxf...),but i want to kown that which camel
> client api i can use to access remote camel server.
>
Check out this tutorial on Spring Remoting o
Hi
Works fine for me.
Did a
svn up
rm -rf repository in my m2 directory
disabled my current settings.xml by moving it to .backup name
stopped nexus, eg. just plain vanilla maven 2.0.9 on jdk 1.5
mvn clean install -Dtest=flase
from the CAMEL root dir
Waited a long time :)
[INFO] ---
On Thu, Dec 24, 2009 at 12:12 AM, tide08 wrote:
>
> It looks like camel-cache processor are not released? I did unjar camel-cache
> 2.1.0 jar, it does not have processor (ex: CacheBasedTokenReplacer) classes,
> and on exploding source jar it does seem to have processor sources.
>
> Are those missi
Hi,
> Works fine for me.
>
> Did a
> svn up
> rm -rf repository in my m2 directory
> disabled my current settings.xml by moving it to .backup name
> stopped nexus, eg. just plain vanilla maven 2.0.9 on jdk 1.5
>
> mvn clean install -Dtest=flase
> from the CAMEL root dir
>
> Waited a long time :)
>
On Thu, Dec 24, 2009 at 12:12 AM, tide08 wrote:
>
> It looks like camel-cache processor are not released? I did unjar camel-cache
> 2.1.0 jar, it does not have processor (ex: CacheBasedTokenReplacer) classes,
> and on exploding source jar it does seem to have processor sources.
>
> Are those missi
On Thu, Dec 24, 2009 at 10:42 AM, Kevin Jackson wrote:
> Hi,
>
>> Works fine for me.
>>
>> Did a
>> svn up
>> rm -rf repository in my m2 directory
>> disabled my current settings.xml by moving it to .backup name
>> stopped nexus, eg. just plain vanilla maven 2.0.9 on jdk 1.5
>>
>> mvn clean instal
I'm sending high volume/small messages to an AMQ topic using the following
API inside of a Camel (2.1) processor...
exchange.getContext().createProducerTemplate().sendBodyAndHeaders("activemq:topic:portal",
messageXML, headers);
I get this warning message every few minutes (stack trace below).
