Translate Java exceptions to C++ error codes

VERIFIED FIXED

Status

Core Graveyard
Java to XPCOM Bridge
P3
enhancement
VERIFIED FIXED
19 years ago
4 years ago

People

(Reporter: Frank Mitchell, Assigned: Igor Kushnirskiy)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
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

19 years ago
Assign to self, until other help emerges.

Comment 2

18 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

Comment 3

18 years ago
Re-assigning to lead engineer of BlackConnect, Igor Kushnirskiy.
Assignee: drapeau → idk
(Assignee)

Updated

17 years ago
Status: NEW → ASSIGNED
(Assignee)

Comment 4

17 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
Last Resolved: 17 years ago
QA Contact: leila.garin → avm
Resolution: --- → FIXED

Comment 5

16 years ago
Verified according to bug 15507.
Added myself to cc list.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.