You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Peter Salnikov (JIRA)" <ji...@apache.org> on 2012/10/02 08:03:08 UTC
[jira] [Commented] (CAMEL-4565) Allow to send messages using a user
supplied pojo interface
[ https://issues.apache.org/jira/browse/CAMEL-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467505#comment-13467505 ]
Peter Salnikov commented on CAMEL-4565:
---------------------------------------
Hi!
I've come to the same situation, when I need to have my POJO in body instead of BeanInvocation.
Do you have any news about this improvement?
> Allow to send messages using a user supplied pojo interface
> -----------------------------------------------------------
>
> Key: CAMEL-4565
> URL: https://issues.apache.org/jira/browse/CAMEL-4565
> Project: Camel
> Issue Type: Improvement
> Reporter: Christian Schneider
>
> The basic requirement is that we want to send a user defined object to a camel endpoint. The user code for sending the object should not contain any camel code.
> So imagine a simple DTO like Person with properties name and age. I would like to use an interface like
> interface PersonSender {
> void send(Person person);
> }
> So in the use code I code get an implementation injected that I simply could call with
> sender.send(person);
> So this is quite similar to our Pojo Messaging @Produce but I donĀ“t want to send a BeanInvocation. Instead I would like to just have the Person object in the body. Ideally this should also support request / response if there is a return type.
> Additionally it should be configurable if it should send aynschronously or synchronously.
> Optionally we may also support a handler or Future for the response.
> To get the interface implementation we should support up to three variants.
> 1) Create the dynamic proxy programmatically
> 2) Define the proxy thiough a spring bean
> 3) Create and inject the proxy using the @Produce annotation (we will need a flag to switch behaviour or use a second annotation)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira