Native proxy for nsIComponentManager

RESOLVED FIXED

Status

Core Graveyard
Java to XPCOM Bridge
P3
enhancement
RESOLVED 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
Because of security concerns, we cannot the generic bridge for
nsIComponentManager.  We must write a custom proxy using JNI and native code,
with at least the same capabilities and security of nsIXPCComponents and the
JavaScript Components object.
(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
(Assignee)

Comment 3

18 years ago
We will ensure security.
I will use bridge for accesing ComponentManager
Assignee: drapeau → idk
(Assignee)

Comment 4

18 years ago
I am closing as fixed
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.