I just heard from Arun Gupta, and he wants us to have the following pre-installed:
- JDK 1.6 U20+
- NetBeans 6.9 "All" version

While it is certainly possible for people to use Eclipse or any other IDE with GlassFish 3/Java EE 6, for the purposes of this workshop, it will be easier if everyone is on the same platform.

The project snapshot from the first day is available here:
http://files.meetup.com/930480/HelloWorld-JavaEE6-Day1-Pr...

Given that some people had problems locating the correct download with the MeetUp blerb given, may I suggest the following sentence instead please? ...

Download at http://netbeans.org/downloads/index.html , in the Bundles table choose the download button at the bottom of the right-most column called All, button noted as Free and 319M, push this button and complete the download and install; needs about .9 gig of disk space.

Anyone want to carpool and split street parking cost? I'm leaving Colma around 5pm, and can pick you up if you are conveniently along the way.

Looking for carpool... Is anyone going to Berkeley area after the meeting?

Here is the final version of the HelloWorld project that Arun sent to us:
http://files.meetup.com/930480/HelloWorld-JavaEE6-Final-P...

From Design pattern point of view, Is it a good practice to do every thing in your managed bean's and get rid of your DAO and Service layer?

Gavin King in his Seam Implementation said that , its overkill of patterns.

Just want to know what other people think about it and Do we really require those traditional layers for a solid application(Easy to maintain , scalable and lot more things)

Layers alone are not always meaningful. Since so many of the systems we build are wonderfully layered, yet *tightly coupled*.

More 'managed' beans? How do you de-couple and test one of those? Isn't this why the Spring framework came along, to challenge the largesse of enterprise Java?

Managed Beans are simple plain POJO beans and are injectable . You can always provide Mock dependancies when writing Unit tests for them.

For example you can configure 2 persistence units one for testing (in memory database) and other one for real database. In your unit test class , inject appropriate persistence Unit.

I find it interesting that so much of coding has been taken out of code. Spring is fascinating in that it'd rather write an external config file than solve the problem in application code. I suppose i'm not understand what's better about this, apart from job security for the maintainers. J2EE6 isn't nearly as twisty, but the extensive use of annotations seems to take us, in some ways, away from configurable code and back toward hardcoded constants...

Thanks, @gurpreet. POJOs are what I am after. Yes I would like to see an example persistence.xml that accomplishes this.. even if to-day it only works with Hibernate/JPA and EntityManager.

Great meetup - thank you Arun. Are the slides available somewhere?