[ http://jira.jboss.com/jira/browse/JBREM-93?page=comments#action_12316811 ] Ovidiu Feodorov commented on JBREM-93: --------------------------------------
Yes, I guess I can use getCause() to get the original exception. Is this behaviour documented somewhere, so I can rely on it? Won't it change accross releases? If I didn't look in the code, I had no way of knowing I can do that. Since I wasn't able to find it documentated, I was reluctant to use it. On the other hand, if you have handleCallback() returning an Object, the interface would be much more intuitive. Any chance to include this is any of your upcoming releases? > Callback handler returning a generic Object > ------------------------------------------- > > Key: JBREM-93 > URL: http://jira.jboss.com/jira/browse/JBREM-93 > Project: JBoss Remoting > Type: Feature Request > Components: callbacks > Reporter: Ovidiu Feodorov > Assignee: Tom Elrod > Priority: Optional > > > InvokerCallbackHandler.handleCallback() returns void. However, is is able to > throw a HandleCallbackException that ultimately reaches the calling party. > I was wondering if it is a big deal to have handleCallback() returning a > generic Object. This would make the handleCallback()'s semantics more > flexible. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
