Jesse beat me to it, but this is what I had typed up. :) Please read anyway.
Currently, this is the advised way to retrieve the target entity and method. However, your questions brings up a good point. Retrieving this information by way of an attribute on the MessageContext rightfully makes you, and other developers cautious. Would you mind opening a jira to improve this? I think we should probably have an API call on the MessageContext to directly retrieve the SearchResult object. mike On Fri, Nov 19, 2010 at 1:33 PM, fishrick <[email protected]> wrote: > > We have a handler where we want to get the Entity and the method that is > going to be invoked. We found the SearchResult attribute and can get the > Entity and method that is going to be invoked from that. But we are a little > leary of using an attribute since we don't know if that will change in the > future... > -- > View this message in context: > http://apache-wink-users.3471013.n2.nabble.com/What-is-the-best-way-in-a-handler-to-get-the-Entity-and-method-that-is-going-to-be-invoked-tp5756400p5756400.html > Sent from the Apache Wink Users mailing list archive at Nabble.com. >
