Hi,
The camel-console standalone bundle is too big and we don't ship it in
the apache-camel kit.
You can download the bundle here[1]
[1]
http://mvnrepository.com/artifact/org.apache.camel/camel-web-standalone/2.7.1
Willem
On 4/19/11 8:41 AM, vcheruvu wrote:
Hi Claus,
I have followed the
Hi,
You are using the producerTemplate to send the message, and there is no
any camel route involved.
If you want to test the camel route with the error handler you can add
route like this
from("direct:start").to("activemq:queue:myqueue");
Willem
On 4/19/11 6:03 AM, Jim Newsham wrote:
Hi,
What I forgot to write:
from("jms") should be from("jms:queuename").
Some small explanation how your servicebean behaves in this. If the
method call succeeds the message is automatically committed and so
removed from the queue. If the method call throws an exception the
message is automatical
Hi Alph,
your problem seems to really cry for jms. So if you do not absolutely
have to use soap/http for your webservice I advise to do the following.
I am not exactly sure how to do the database polling but you ssound as
if you know how to do it. So I absstract this away. As your service is
Looking for advice on the best way to tackle the following...
Need a process to:
+ poll a database table for the arrival of a new record
+ transform the record to the XML appropriate for a document-literal SOAP
webservice
+ send to the webservice
All this is relatively easy; here are the issues:
Hi Claus,
I have followed the camel web-console
(http://camel.apache.org/web-console.html) web page that you mentioned in
the previous post. As per the instructions on the web page, I cannot find
the camel-web-standalone.jar file in the 2.7.1 zip file . Is the
camel-webconsole webpage out of date
Hi,
We are using Camel 2.5.0 and ActiveMQ 5.4.1. In our application, we see
that failure to obtain a jms connection from the connection pool results
in an unhandled exception which bubbles up to the caller, instead of it
being handled by one of the global exception handlers that we have
con
Hello everyone
We are trying to get camel running as an OSGI bundle in Virgo - more or
less successfully. Our first attempt was to simply add camel-core and
camel-spring as dependencies (version 2.7.1) to the pom.xml of our osgi
web application
org.apache.camel
camel-core
org.apache.camel
Hi Claus,
That's exactly what I use. I use recipient list pattern. That's working as
expected.
The problem I am having is on the actual transport using HTTP component.
User A is using an authenticated connection of User B to the same endpoint.
It's a backend webserivce. I am okay to reestablish
Great. That looks like just what I need.
Thanks.
--
Erlend
On Apr 18, 2011 4:23 PM, "James Strachan" wrote:
> On 18 April 2011 15:14, Erlend Hamnaberg wrote:
>> Hello list.
>>
>> I am trying to use concurrent consumers pattern with JMS.
>>
>> The use case is:
>>
>> Messages from each sender nee
On 18 April 2011 15:14, Erlend Hamnaberg wrote:
> Hello list.
>
> I am trying to use concurrent consumers pattern with JMS.
>
> The use case is:
>
> Messages from each sender needs to be kept in order.
>
> Sender A, B and C.
>
> Messages sent:
>
> A1, B1, C1, B2, A2, C2, C3, A3, B3
>
> Output:
> A
Hello list.
I am trying to use concurrent consumers pattern with JMS.
The use case is:
Messages from each sender needs to be kept in order.
Sender A, B and C.
Messages sent:
A1, B1, C1, B2, A2, C2, C3, A3, B3
Output:
A1, A2, A3
B1, B2, B3
C1, C2, C3
Is there a way in Camel to ensure that th
When you need a dynamic uri for an endpoint you should use the
recipient list EIP pattern.
http://camel.apache.org/recipient-list.html
On Mon, Apr 18, 2011 at 4:44 AM, manoj.sahu wrote:
> Hi Ashiwin,
> Thanks for your response. Unfortunately I cannot do that. First of all the
> remote server i
13 matches
Mail list logo