Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 160739 - Some JRE profiles don't seem correct
Summary: Some JRE profiles don't seem correct
Status: RESOLVED DUPLICATE of bug 188304
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: equinox.framework-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 170391 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-10-12 15:46 EDT by Pierre Carlson CLA
Modified: 2007-11-30 09:12 EST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pierre Carlson CLA 2006-10-12 15:46:14 EDT
I think the J2SE 5 JRE profile is not totally complete.  I found the following packages are not being exported via the profile:

org.w3c.dom.css
org.w3c.dom.html
org.w3c.dom.ranges
org.w3c.dom.stylesheets
org.w3c.dom.traversal
org.w3c.dom.views

Both the Sun and the IBM JREs have these packages.  I cannot browse to the these packages in the Sun JavaDoc site, but when I search for them, I get links to the Sun JavaDoc site.  For example:
http://java.sun.com/j2se/1.5.0/docs/guide/plugin/dom/org/w3c/dom/css/package-summary.html
Comment 1 Thomas Watson CLA 2007-01-15 11:11:05 EST
*** Bug 170391 has been marked as a duplicate of this bug. ***
Comment 2 David Williams CLA 2007-01-15 14:03:49 EST
To follow-up on the comment in dup'd bug 170391, to "survey all major JRE's" is certainly one data point, and a nice sanity check, but I might also suggest 
http://java.sun.com/j2se/1.5.0/docs/ 
as another. While it would be a lot of work to step through all the spec's mentioned there, that does seem to be the "official source" of what's in J2SE 1.5. 

There's a similar one for 1.6. 
http://java.sun.com/javase/6/docs/

In the meantime, seems DOM ones are the only ones reported as bugs so far, so ... perhaps those could be fixed. 

Perhaps, too, if this is known to be an error prone report, perhaps some work could be done so "unknown" API's specifically from the EE could be reported as "discouraged acess" ... since "restricted access" is a lot worse. 

Comment 3 David Williams CLA 2007-01-15 14:11:32 EST
Oh, and another thing that would help improve the situation, if indeed it is impossible to have a well defined set of API's for an EE, would be to allow more user control over the access rules for the EE, that is, to provide some GUI so they could modify the whole EE for their whole development environment. As it is now, I have to go in project-by-project and say these special cases are "accessible". 

Comment 4 Walter Harley CLA 2007-03-02 16:42:13 EST
The "javax.annotation.processing" and "javax.lang.model.**" packages, which are related to JSR-269, are also missing.  This means that annotation processors written to the new Java 6 standard get restricted access errors unless a specific 1.6 JDK, rather than a J2SE-1.6 execution environment, is on the classpath.
Comment 5 Thomas Watson CLA 2007-03-02 17:03:22 EST
The "javax.annotation.processing" and "javax.lang.model.**" packages, along with a bunch of other packages new to 1.6, have been released to the JavaSE-1.6 profile in bug 173618.
Comment 6 Walter Harley CLA 2007-03-02 21:29:38 EST
Ok, thanks.  Thought so but I couldn't find the right bug report.
Comment 7 Thomas Watson CLA 2007-11-30 09:12:03 EST
This should make Pierre happy.

*** This bug has been marked as a duplicate of bug 188304 ***