Hi Jim,
I am not sure if it is possible to simply send a temp queue name around.
The jms server somehow manages who may access a temp queue. I guess when
you set replyto on a message to the temp queue this will allow the
receiver of the message to respond on this queue. If you simply send the
Hi
The problem is that you are using 0 as the pool size.
.threads(0)
If you use 1 or larger it should work
I will fix the issue so you can define 0 as the pool size.
On Mon, Oct 11, 2010 at 7:50 PM, serega wrote:
>
> Hi.
> Here is the scenario:
> public static void main(String[] args) thr
Try with a newer version of Camel.
On Tue, Oct 12, 2010 at 12:19 AM, SwenVogel wrote:
>
> Hi,
>
> i want to handle exceptions in an routing slip with the deadLetterChannel.
>
> The problem is that there are no re-deliveries attempts if an exception
> occurs.
>
>
> Im using Camel version 2.2.0
>
We wanted a queue scoped to the lifetime of the connection, and scoped
to a single jms client, so temporary jms queues are a pretty good fit.
When the connection dies, the queue and its contents can be
automatically discarded. No ACL needed for the queue. etc. It's
essentially a one-way e
Hi,
I am not sure what you are trying to do, but why not have a named queue and
a Correlation Id to map requests to responses. This way you do not have to
worry about time taken by the overall transaction to complete.
Passing around temporary queue names around is highly unusual since by
definit
Hi,
You can add a registry in the following way.
In the link below the CamelContextSupport class creates a
DefaultCamelContext using a registry. You can do the same.
https://svn.apache.org/viewvc/camel/trunk/components/camel-test/src/main/java/org/apache/camel/test/CamelTestSupport.java?view=ma
Hi,
i want to handle exceptions in an routing slip with the deadLetterChannel.
The problem is that there are no re-deliveries attempts if an exception
occurs.
Im using Camel version 2.2.0
For example the following code never retries:
from("file://c:/camel/work/input?delay=1")
.erro
The documentation on jms temporary destinations is very sparse. I'm
struggling to understand how I can use a jms temporary queue with Camel,
outside the use case of request/reply, which Camel already handles
automatically.
I want to create a route which receives messages on a temporary jms
Note that only the JMS component - like a few other components - has a
dependency on Spring. Camel's API (packaged in camel-core) isn't at all
coupled to Spring, it uses the http://camel.apache.org/injector.html
Injector to abstract from the underlying IoC framework (Spring, Guice,
etc).
-
Hi.
Here is the scenario:
public static void main(String[] args) throws Exception {
BasicConfigurator.configure();
CamelContext context = new DefaultCamelContext();
context.addRoutes(new RouteBuilder() {
public void configure() throws Exception {
> Thank you for your response.
> I've already seen that the stacktrace is available in the Http body.
> I hoped that the exception would be raised as the spring http exporter does.
Please reply to the public mailing list and not directly to me.
In terms of such a feature (to let camel be able to
Hi,
Camel JMS component is tightly coupled with Spring JmsTemplate, which is
rather bad news. Given that Spring with its classloader hack tries to
resolve the namspace handler and fails miserably. It is just not meant for
OSGi setup.
Even if we try to move to Apache Aries Blueprint we still cannot
Hi
The remote server sends back the HTTP status 500.
And whatever it sends back is usually plain/text
And hence there is no remote stacktrace serialized in the HTTP body.
The Camel servlet/jetty component will by default send back the
exception message + stacktrace as String
which you can get fr
Hi Willem,
I just tested 2.5-SNAPSHOT on the CXF Jetty and OSGi transports with the
inclusion of the publishedEndpointUrl property. All worked as expected.
Thanks for your efforts on this!
Regards,
Scott Christopher.
On 10/10/2010, at 2:38 PM, Willem Jiang wrote:
> Hi Scott,
>
> I co
When I define a method in an interface that returns a checked exception and
use camel:proxy via a http component I get a HttpOperationFailedException at
the client and I cannot access the exception that was raised at the server.
This is my servlet:
http://camel.apache.org/schema/spring";>
I'm not sure it will solve your issue but try to remove the (" ") from the
expression.
Documentation is available http://camel.apache.org/simple.html here .
--
View this message in context:
http://camel.465427.n5.nabble.com/Spring-DSL-Choice-does-not-work-tp3207085p3207127.html
Sent from the C
16 matches
Mail list logo
