Re: DestinationResolver for Reply Messages

Update: It works. >From my point of view, it would be nice to extend camel to support provider specific JMS destination properties. I'm not yet sure how to include it. Maybe it could be done just by have the possiblity to add a "DestinationPropertyProvider" or something like this just at the place

Re: DestinationResolver for Reply Messages

I'm quite optimistic that injecting a new JmsConfiguration extends JmsConfiguration with an own JmsTemplate extending the CamelJmsTemplate would work. In the MyJmsConfiguration I've copied the createInOnlyTemplate from JmsConfiguration and just modified the line JmsTemplate template = new Ca

Re: DestinationResolver for Reply Messages

btw. I think the problem is that the destination for reply is directly read from the JMS Message in the JmsMessageHelper with message.getJMSReplyTo(); This destination (instanceof Destination) could be directly used to send the reply without the DestinationResolver. The DestinationResolver is only

DestinationResolver for Reply Messages

I need to connect to WebSphere MQ and set the correct header fields in the WMQ message header. This works fine for simple fire&forget as well as for request messages since I'm using a DestinationResolver to set all the required poperties to the destination. public Destination resolveDestinati

Re: WebSphere MQ Reply

Hi Claus I'm using 2.10.1. Since I saw, that there was a fix [ CAMEL-5464 ] in 2.10.3 dealing with jms replies I tried also with 2.10.3 with the same result. Today I will enable the debug log, to get more information about it. I'll post as soon

WebSphere MQ Reply

I have a problem with Request/Reply over WebSphere MQ. Sitation is that the Request is comming from WMQ and has to go back to WMQ. Everything works fine, the message is handeld correctly as InOut, the reply is prepared but not sent to WMQ even if there is no exception or any hint for that in the t

configure xstream instead of java serialization as default

Is it somehow possible to configure xstream as object serialization instead of the java serializiation? In my project I have various Object Messages to transfer over JMS. By default the Obects are serialized with the Java serialization. Of course I could configure the route to do marshalling and u

Re: Access XSD (Resources) in from an OSGI bundle

It is Eclipse Virgo. Claus Ibsen-2 wrote > On Wed, Oct 3, 2012 at 11:16 AM, prueegg < > patrick.rueegg2@ > > wrote: >> We are using Spring DM >> > > Yes but which OSGi container? Is it Eclipse Virgo, Apache Karaf or > something else? > > >>

Re: Access XSD (Resources) in from an OSGI bundle

We are using Spring DM Claus Ibsen-2 wrote > Hi > > What OSGi runtime do you use? > And do you use Spring-DM or Blueprint? > > Its mainly Apache Karaf / ServiceMix that is supported by Camel. > -- > Claus Ibsen -- View this message in context: http://camel.465427.n5.nabble.com/Access-XSD

Re: Access XSD (Resources) in from an OSGI bundle

Babak Vahdat wrote > // begin-quote > I checked the availability of th xsd with the following code in the same > configure() methode of my RouteBuilder() > InputStream is = > this.getClass().getClassLoader().getResourceAsStream("resources/Msg_template.xsd"); > > It works. So the resource is

Re: Access XSD (Resources) in from an OSGI bundle

Hi Christian Thanks for your answer. I've also tried it with camel 2.10.1 but it didn't work as well. The XSD is in the same bundle as our RouteBuilder. We have planned to upgrade to 2.10.1 anyway but it will take some time. If I find the time for writing a osgi integration test, I'll write it.

Access XSD (Resources) in from an OSGI bundle

Hi I have the problem, that I cannot configure a route with a validator. The route is configured in an OSGI-Bundle which should run on an Virgo Server. The Route Definition is: from(getRouteStartUri()).to("validator:classpath:resources/Msg_template.xsd").to(getRouteEndUri()); But alway get the fo

Re: Optional Endpoints

Is it possible to relate to properties in the camel context as well? All the examples I've seen are based on the properties of the exchange. -- View this message in context: http://camel.465427.n5.nabble.com/Optional-Endpoints-tp5711824p5711916.html Sent from the Camel - Users mailing list archiv

Re: Optional Endpoints

Hi Henrique Thanks for your reply. In the meantime I've found out, that an interceptor could do the job as well. The filter statement would allow me to switch on/off on the fly, where the interceptor would be more static. So I assume the filter and property solution would be the better one and

Optional Endpoints

I have a question concerning optional endpoints. Background is that I want to do something like this: from(anyActiveMQ-Queue) .bean(anyProcessingBean) .to(anotherActiveMQ-Queue) *.to(additionalFileArchiveFolder)*; // optional if the message should really go to the *additionalFileArchiveFolder *s