Hi
I think you can do like this
public Exchange doSomething(Exchange exchange) {
...
return exchange;
}
So the @Exchange annotation is not really neeed IMHO. As its not a common class
such as java.lang.String etc.
And I also think you can do return a String etc. instead of Exchange for just
the playload in the message. But I am not 100% sure.
Med venlig hilsen
Claus Ibsen
......................................
Silverbullet
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576
Web: www.silverbullet.dk
-----Original Message-----
From: cmoulliard [mailto:[EMAIL PROTECTED]
Sent: 10. juli 2008 11:34
To: [email protected]
Subject: Annotation @Exchange planned in a future release ?
Hi,
Is it planned in a future release of Camel to also have the annotation
@Exchange available inside the bean component ?
I ask you that question because when you want inside a bean to perform by
example a in.getOut().setHeader("", ""), you need to have access to the
Exchange object. The annotation allow to receive the @Properties, @Headers
and @Body but no the exchange.
Regards,
Charles
--
View this message in context:
http://www.nabble.com/Annotation-%40Exchange-planned-in-a-future-release---tp18379161s22882p18379161.html
Sent from the Camel - Users mailing list archive at Nabble.com.
