[
https://issues.apache.org/jira/browse/CAMEL-17357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462791#comment-17462791
]
Claus Ibsen commented on CAMEL-17357:
-------------------------------------
No sorry we will not compromise the camel-bean component or anything in the
core about serialized java over rpc.
You can build custom camel components where you can add everything in this
component for such functionality.
> Make the AbstractInvocationHandler pass the method name to the exchange
> -----------------------------------------------------------------------
>
> Key: CAMEL-17357
> URL: https://issues.apache.org/jira/browse/CAMEL-17357
> Project: Camel
> Issue Type: Improvement
> Components: camel-bean
> Affects Versions: Future
> Reporter: Olaf Heyder
> Priority: Major
>
> One purpose of the _CamelInvocationHandler_ (& Friends) is to translate a
> _java.lang.reflect.Method_ to an _Exchange_ in order to eventually have the
> registered _Producer_ process that Exchange. Currently the name of the method
> gets lost when the Exchange is prepared.
> It would be helpful if the Exchange contained the method name (as a String),
> e.g. as an appropiate header. In that case it would be possible to write a
> new Camel Component "{*}jsonrpc{*}". according to Camel's design concept,
> because the [jsonrpc protocol|https://www.jsonrpc.org/] requires the name of
> the method in the request message.
> My suggestion is to attach the method name to the Exchange in method
> {{protected Object invokeProxy(final Method method, final ExchangePattern
> pattern, Object[] args, boolean binding)}}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
