The first preview release of the Java EE 6 Tutorial was released yesterday.
Get it by installing the Java EE 6 SDK Preview and ugprading the Java EE 6 Tutorial package using the Update Tool.
We've got a bunch of new material and examples in this release, including:
- JavaServer Faces 2.0, including Facelets, an XHTML-based display technology that is much easier than JSP.
- JAX-RS 1.1, the RESTful web services API.
- EJB 3.1, which really simplifies EJB development, and allows you to package enterprise beans within web applications.
- The Java Persistence API 2.0, with support for collections (including Maps) within entities, mixed field/property access, and orphan removal for one-to-many and one-to-one relationships.
- Servlet 3.0, which now uses annotations to truly make the web.xml deployment descriptor optional.
Our examples are developed as a java.net project, so if you find bugs or want to file enhancement requests we'd love to hear about them.
Our mailing lists provide another way of giving feedback, and are also good places to start if you're interested in contributing source code or material for the Java EE 6 Tutorial.

But don't you think there should be more whitespace for the left menu? I mean, who wants to read the content after all, it's the left menu that's important today here in the 1980's with our little 15" 800x600 monitors.
http://imgur.com/9i83I.png
Posted by Mikael Gueck on August 03, 2009 at 02:29 AM PDT #
Mikael: We actually don't have direct control of the HTML output, since we author the tutorial in SGML and use conversion tools to produce the HTML and PDF.
But yeah, the layout in your setup is pretty unusable. I've forwarded on your comment to Sun's documentation tools team to see what they have to say.
On a personal note, I would have *loved* a 15" 800x600 monitor for my Commodore 128 in the '80s....
Posted by Ian Evans on August 03, 2009 at 02:22 PM PDT #
I went the Telmac - Spectrum - XT - AT route in the 80s. I think we got SVGA still during that decade, not that I was an early adopter.
Sorry for the snark, but it just seemed so foolish that I couldn't fix the problem myself because the documentation license is so much more stringent than the open source licence which governs the actual software which is described in the documentation.
Posted by Mikael Gueck on August 03, 2009 at 03:50 PM PDT #
Our (excellent, btw) tools team is looking into this with a possible fix for the next update. Would you be willing to test the HTML to see if it works on your setup? My biggest monitor is nowhere near the resolution of yours.
As for the documentation license, the examples are BSD licensed, but Sun holds the copyright on the actual documentation, and we're not really prepared to license the docs under, for example, the Gnu Documentation License or Creative Commons licenses. Some of that is due to third-party business relationships we have, some of it is institutional inertia. Mostly, the community hasn't asked for or demanded it, and we haven't seen a lot of interest in contributing to or modifying our docs.
Disclaimer for the jumpy: the above opinions are my own; I don't speak for Sun, I write for them.
Posted by Ian Evans on August 04, 2009 at 12:16 PM PDT #
Sure, I'd love to help. I understand the problem, having worked in my share of large organizations.
However, I try to do something when I notice these kinds of problems, because since people and things are how they are, if I don't do something then probably no-one else will either.
Posted by Mikael Gueck on August 06, 2009 at 05:42 AM PDT #