Bug 153848 - [sec] Support for JCA classes provided from bundles
Summary: [sec] Support for JCA classes provided from bundles
Status: NEW
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Incubator (show other bugs)
Version: 3.4   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: equinox.incubator-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 196988 199757 199760
Blocks: 199330
  Show dependency tree
 
Reported: 2006-08-14 21:38 EDT by Matt Flaherty CLA
Modified: 2019-09-06 16:18 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Flaherty CLA 2006-08-14 21:38:47 EDT 
In order to provide implementations of JCA (Java Crytography Architecture) artifacts (ie: KeyStore, TrustManagerFactory, etc), Eclipse needs to provide a way to contribute them via extension points or services and then proxy method calls from the classloaders that JCA requires (ie: not change the programming model of Java security by requiring ContextClassloader manipulation).
Comment 1 Philipe Mulet CLA 2007-03-26 10:02:12 EDT 
Is anything planned for 3.3 ?
Comment 2 Jeff McAffer CLA 2007-03-26 10:17:10 EDT 
no contributions related to security are happening in 3.3
Comment 3 Thomas Watson CLA 2008-05-16 11:14:00 EDT 
Code has been contributed to the incubator.  Our investigations have determined that the need for an additional framework above and beyond what the JVM provides is unnecessary.  Removing milestone.  Matt, should this be closed as wontfix?
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:18:47 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.