Re: CxfEndpoint and configure interceptor on bus

Hi Aki, Thanks for your reply. The problem was that the interceptor that was defined on the bus was not invoked and even not added to the interceptor chain but this was a stupid configuration error on my side :-( With CXF-2.4.4 it was working if was defined (wrong usage of the "id" attribut

CxfEndpoint and configure interceptor on bus

Hi, I've a question regarding camel-cxf in combination with interceptors configured on the CXF-bus. It seems that the behaviour has changed from CXF-version 2.4.4 to 2.4.6 but I'm not sure if it's a camel problem. I've modified a unit-test that shows the problem. I expected an interceptor that is

Re: Classpath problem with camel-cxf and OSGi

Hi, See here: http://old.nabble.com/-VOTE--Release-Apache-Camel-2.1.0-to26587866s22882.html http://old.nabble.com/-VOTE--Release-Apache-Camel-2.1.0-to26587866s22882.html for download link of version 2.1.0 -- View this message in context: http://old.nabble.com/Classpath-problem-with-camel-cxf-

Re: Does Jaxb With Spring Remoting (proxy) work ?

Hi, If I get you right the problem is that the classes generated by jaxb do not implement Serializable?! This can be changed by adding custom binding for jaxb. I haven't tried out how to use this with Camel but I guess this should be a starting point. You can also google for jaxb java class seria

Re: Problem with FileConsumer and pollEnrich

Yes, but trunk doesn't build currently ;-) ... If you commit it later, no problem. -- View this message in context: http://www.nabble.com/Problem-with-FileConsumer-and-pollEnrich-tp24795192p24895196.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Problem with FileConsumer and pollEnrich

Hi Claus, FileUtil.stripExt(...) does not exist on trunk ... -- View this message in context: http://www.nabble.com/Problem-with-FileConsumer-and-pollEnrich-tp24795192p24895089.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel Spring Remoting throwing RuntimeException question

Hi Claus I've created the JIRA issue 1888 with a patch and a test case for the problem with the Exception. For the problem with the camel-example-pojo-messaging where the camelLock files remain in the src/data dirctory on my machine. The steps as stated in readme.txt: call mvn compile camel:r

Re: Camel Spring Remoting throwing RuntimeException question

Hi Thanks for the reply. I think the test-case is slightly different than what my request was. If you change the EchoPojo to inject a dynamic proxy you will see the problem that I have (see code below). public class EchoPojo { @Produce(uri = "direct:echo") //private ProducerTemplate se

Camel Spring Remoting throwing RuntimeException question

Hello, I use a direct endpoint to access a service that throws a RuntimeException and on the calling side I get a UndeclaredThrowableException (with the nested RuntimeException deep in the stack) instead of the expected RuntimeException. Maybe I missed something and this be changed by configurat

Re: Redelivery in Loadbalancer

Hi Claus, Works fine now =) Thanks for the fix. -- View this message in context: http://www.nabble.com/Redelivery-in-Loadbalancer-tp24161904p24184289.html Sent from the Camel - Users mailing list archive at Nabble.com.

Redelivery in Loadbalancer

Hi, I'm trying to configure redelivery in the loadbalancer but I don't get the expected result. What I want to do is something like this: > loadbalancer +> route A (with maximumRedelivery=2) | +> call endpoint | +> call endpoint

Re: How to prevent routes from started twice?

Hi, I've tested it yesterday and it works fine. Thanks a lot for that. Maybe you can check my comments after your last commit to enable manual start if the shouldStartContext flag is set to false. -- View this message in context: http://www.nabble.com/How-to-prevent-routes-from-started-twice--tp

Re: How to prevent routes from started twice?

Hi Claus, I created the JIRA task https://issues.apache.org/activemq/browse/CAMEL-1711. Simple project and a logfile is attached. -- View this message in context: http://www.nabble.com/How-to-prevent-routes-from-started-twice--tp23983653p24032807.html Sent from the Camel - Users mailing list ar

Re: How to prevent routes from started twice?

I see it twice! Once for the root application context (which is correct, because its the context where the camel context is defined in) and a second time for the web application context (which I think is incorrect because it's the child context of the root). I don't know if it would work in all c

Re: How to prevent routes from started twice?

Hi Claus, I does honor but the problem is that you can't start the camel context (from another bean) if shouldStartContext is set to false, and this is the only way to prevent the execution of code that is triggered by refresh event. I'll create a JIRA ticket with a problem description. -- Vie

How to prevent routes from started twice?

Hi, I've a spring based web application that has 2 applicationContexts (the second has the first as parent). My problem is that the SpringCamelContext listens to the ContextRefreshedEvent and starts the camel context. This works fine if you have only 1 context but if the ContextRefreshedEvent o

Re: Are durable topic subscriptions destroyed?

wrote: > > 2009/3/5 akuhtz : >> >> There is currently no code to unsubscribe a durable subscriber as Camel >> uses >> the XXMessageListenerContainer classes from the spring framework and >> inside >> the spring code there is no unsubscribe code. I solved this y

Re: Are durable topic subscriptions destroyed?

Spring Issue created: http://jira.springframework.org/browse/SPR-5552 Claus Ibsen-2 wrote: > > On Thu, Mar 5, 2009 at 12:33 PM, akuhtz wrote: >> >> There is currently no code to unsubscribe a durable subscriber as Camel >> uses >> the XXMessageListenerCon

Re: Are durable topic subscriptions destroyed?

There is currently no code to unsubscribe a durable subscriber as Camel uses the XXMessageListenerContainer classes from the spring framework and inside the spring code there is no unsubscribe code. I solved this yesterday by making a copy of the (in my case) SimpleMessageListenerContainer and add