[ mx4j-Bugs-1219367 ] RMIConnector cannot unmarshal custom Notifications
"SourceForge.net" <[email protected]>
| Newsgroups | gmane.comp.java.mx4j.devel |
|---|---|
| Message-ID | <[email protected]> |
Bugs item #1219367, was opened at 2005-06-13 00:24 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=450647&aid=1219367&group_id=47745 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: JSR 160 Implementation Group: Release 3.0.1 Status: Open Resolution: None Priority: 5 Submitted By: Simone Bordet (simonebordet) Assigned to: Simone Bordet (simonebordet) Summary: RMIConnector cannot unmarshal custom Notifications Initial Comment: As reported by [email protected], MX4J's JSR 160 RMI connector is not able to unmarhsal custom notifications (subclasses of jmx.Notification) emitted by MBeans. This is due to the fact that the context classloader is not set properly in the notification fetcher thread. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=450647&aid=1219367&group_id=47745 ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20