You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Frank Barnaby (JIRA)" <ji...@apache.org> on 2007/07/26 22:02:03 UTC
[jira] Created: (RIVER-76) RemoteEventData should propagate
exceptions
RemoteEventData should propagate exceptions
-------------------------------------------
Key: RIVER-76
URL: https://issues.apache.org/jira/browse/RIVER-76
Project: River
Issue Type: Improvement
Components: com_sun_jini_mercury
Affects Versions: jtsk_2.1
Reporter: Frank Barnaby
Priority: Minor
Bugtraq ID [6242889|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6242889]
{{RemoteEventData}} currently swallows marshalling exceptions and sets the event to null. This results in packaging a "null" event across to the client, which is ignored. It would be more efficient to propagate the exception to the caller and not include it in the set of events that gets passed to the client.
Recommended per code review of bug [6230044|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6230044] .
On the client-side should probably propagate the unmarshalling {{IOException}} there too and just skip over the event.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.