bean invocation is deprecated in 2.15

[suneshkumar <su...@gmail.com>]

Hi Guys

I am trying to use the following routing, but unfortunately the bean
invocation is now deprecated in when, can anyone help me how I can achieve
the below without using the deprecated methods?

    from(utpStpResponseQueue)
      .choice
      .when(bean(smlSkipMessageHandler, "skipHandler(${body},
${headers})")).stop      
      .otherwise.bean(transformer, "transform(${body},
${headers})").to(stpResponseTopic)
      .endChoice


.when(bean --> this is the bean invocation which is deprecated

Thanks!

Sunesh




--
View this message in context: http://camel.465427.n5.nabble.com/bean-invocation-is-deprecated-in-2-15-tp5770651.html
Sent from the Camel - Users mailing list archive at Nabble.com.

RE: bean invocation is deprecated in 2.15

["Goodwin, Matthew" <Ma...@railinc.com>]

Instead of bean using method:

method(smlSkipMessageHandler, "skipHandler(${body},${headers})")


-----Original Message-----
From: suneshkumar [mailto:suneshkumar@gmail.com]
Sent: Thursday, August 13, 2015 6:06 AM
To: users@camel.apache.org
Subject: bean invocation is deprecated in 2.15

Hi Guys

I am trying to use the following routing, but unfortunately the bean invocation is now deprecated in when, can anyone help me how I can achieve the below without using the deprecated methods?

    from(utpStpResponseQueue)
      .choice
      .when(bean(smlSkipMessageHandler, "skipHandler(${body},
${headers})")).stop
      .otherwise.bean(transformer, "transform(${body},
${headers})").to(stpResponseTopic)
      .endChoice


.when(bean --> this is the bean invocation which is deprecated

Thanks!

Sunesh




--
View this message in context: http://camel.465427.n5.nabble.com/bean-invocation-is-deprecated-in-2-15-tp5770651.html
Sent from the Camel - Users mailing list archive at Nabble.com.

________________________________

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.