Skip to main content

Which optional package should be added to core J2SE

Jini
4% (222 votes)
JXTA
7% (408 votes)
JavaHelp
25% (1552 votes)
JAXB
7% (433 votes)
JAI
2% (126 votes)
Other
1% (39 votes)
None
55% (3348 votes)
Total votes: 6128

Comments

Commons

If there's anything I'd like to see added to the J2SE API, it's some of the Jakarta Commons stuff, in particular commons-lang, commons-io and commons-collections. These are all really just patches to the classes in java.* I can dream.....

Already too many APIs

There are already too many. The survey should rather ask which APIs could/should be /removed/ from the core spec.

Already too many APIs

Yeah, I agree and we thought of that. We couldn't do it as a survey because we didn't know which options to choose from. We're going to do that as a follow-up forum. Thanks.

none

None, at least till we have a framework which let switch to indipendent implementations of standardized apis (xml, etc...). The endorsed mechanism is ugly.

none

none should be included. At least till we won't have a framework which let core libraries replaced by third party implementations (endorsed mechanism sucks)

Add JDO

I agree with many members in the community that JDO would be a great addition to J2SE. It would allow developers to implement systems with strong persistence capabilities without the need for a J2EE application server, which can be overkill for many projects.

J2SE Lite

Sun should offer a lite version of the JDK/JRE, one that contains only:
  • java.lang
  • java.io
  • java.net
  • java.util
My 2 cents...

J2SE Lite

Hmm, I've been working with J2ME CDC and CLDC on an embedded platform, and find myself adding back J2SE functionality all the time (lang, util, etc). This is an old thread, but it still makes sense.

J2SE Lite

Of course, now there is Java SE for Embedded.

J2SE Lite

Probably need to add java.nio to that list as it is now hard to separate from io. In addition java.beans and java.math are both tiny.

None

the JVM is HUGE and a monolithic update of the whole thing is scheduled far too long apart. Plenty of people asked to seperate the JVM into different parts for a reason.. The question is misleading; the real issue is that these items are not packaged correctly if people feel that they can't use or reach them without including them in the standard distribution.

J2DE

While I voted for Jini, I would actually prefer the creation of a new Java distribution aimed at the development of distributed Java applications not based on J2EE. This J2DE (Distributed Edition) would include Jini, JXTA, and possibly other APIs that are useful for developing distributed applications, but not strongly tied to either EJB or web services.

J2DE

and toss out the org.omg packages...