Closed
Bug 15510
Opened 25 years ago
Closed 23 years ago
Translate Java exceptions to C++ error codes
Categories
(Core Graveyard :: Java to XPCOM Bridge, enhancement, P3)
Core Graveyard
Java to XPCOM Bridge
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: frankm, Assigned: blackconnect)
Details
If a Java object throws an exception during a C++ XPCOM proxy's method call, the proxy should detect the exception and convert it into an appropriate NSRESULT. If the exception is a standard Java exception, the proxy may translate it to an equivalent, e.g. OutOfMemoryError becomes NS_ERROR_OUT_OF_MEMORY.
Reporter | ||
Comment 1•25 years ago
|
||
Assign to self, until other help emerges.
Comment 2•24 years ago
|
||
Frank Mitchell no longer works at Sun and his email is bouncing. Reassigning his 21 bugs to george for reassignment.
Assignee: frankm → drapeau
Status: ASSIGNED → NEW
Re-assigning to lead engineer of BlackConnect, Igor Kushnirskiy.
Assignee: drapeau → idk
Assignee | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 4•23 years ago
|
||
this bug fixed with http://bugzilla.mozilla.org/show_bug.cgi?id=15507 closing as fixed. For all java exceptions we are using NS_ERROR_FAILURE status.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
QA Contact: leila.garin → avm
Resolution: --- → FIXED
Comment 5•23 years ago
|
||
Verified according to bug 15507. Added myself to cc list.
Status: RESOLVED → VERIFIED
Updated•10 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•