Re: Failed to resolve endpoint - Could not find a suitable setter for property: codec

Also you should use # to indicate it's a spring bean id to be looked up. This codec=hl7codec Should be codec=#hl7codec This is the style used in Camel 2.0 onwards. -- View this message in context: http://camel.465427.n5.nabble.com/Failed-to-resolve-endpoint-Could-not-find-a-suitable-setter-fo

Re: Failed to resolve endpoint - Could not find a suitable setter for property: codec

You need camel-hl7.jar on the classpath -- View this message in context: http://camel.465427.n5.nabble.com/Failed-to-resolve-endpoint-Could-not-find-a-suitable-setter-for-property-codec-tp2262540p2262571.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Help with filter behavior

On Mon, Aug 2, 2010 at 5:50 PM, GSegel wrote: > > Claus- Thanks for taking the time to respond! > > I upgraded to 2.4 and my issue is resolved but just to follow-up, I tried > your suggestion of using '.filter(xpath("/order[not(@test)]"))' but it still > didn't work with 2.3. > In Camel 2.3 you n

Re: Help with filter behavior

Claus- Thanks for taking the time to respond! I upgraded to 2.4 and my issue is resolved but just to follow-up, I tried your suggestion of using '.filter(xpath("/order[not(@test)]"))' but it still didn't work with 2.3. I'm seeing that using Java to define the routes is limiting but the applicat

Re: CXF Consumer Endpoint (multiple routes)

Hi You can use one route and the Content Based Router to determine which operation was invoked. There is a header on the Camel Message which the name of the operation invoked. On Mon, Aug 2, 2010 at 4:23 PM, Marco Zapletal wrote: > Hello, > > I have a CXF service with one port type, which has

Re: Help with filter behavior

I was using Camel 2.3. I switched to version 2.4 as you recommended and the error highlighting went away. With version 2.4, it now works for '.filter().xpath("/order[not(@test)]")' and also for Claus's suggestion of '.filter(xpath("/order[not(@test)]"))'. Before trying the 2.4 version, I put th

CXF Consumer Endpoint (multiple routes)

Hello, I have a CXF service with one port type, which has two operations. Is it possible to define two routes, whereby each route consumes from the same endpoint (CXF service) but from a different operation? As far as I have seen, I have to define two services (port types) with one operation e

Re: RE : Usage of server managed thread of Websphere

There is our final implementation (see attached document). Definition of the strategy into the Spring context: The local JNDI resource "wm/wasWorkManager" should be declared into the web.xml file The object from JNDI should be a commonj.work.WorkManager provided by Websphere Our exec

Re: RE : Usage of server managed thread of Websphere

On Mon, Aug 2, 2010 at 10:05 AM, chaillon wrote: > > OK... so there was a mistake into my implementation of the strategy... > > Now, my executorStrategyService works great with websphere > That's fantastic. Thanks for reporting back and confirming you can have Camel leverage threads managed by We

Re: RE : Usage of server managed thread of Websphere

OK... so there was a mistake into my implementation of the strategy... Now, my executorStrategyService works great with websphere Thanks -- View this message in context: http://camel.465427.n5.nabble.com/Re-RE-Usage-of-server-managed-thread-of-Websphere-tp2259287p2261485.html Sent from the Cam