Hi, I'm reading the mailinglist for a while, but this is my first mail. I think it's a bad idea to have Java 6 as a requirement. In the scenario of running an older (non JEE 6) app server that doesn't run on Java 6, it would still be possible to use Web Beans in a similar way you use it in Tomcat. This won't work if Java 6 is a requirement. Specially in combination with JSF 2.0, which can run on non JEE 6, non Java 6 servers, it makes sense to have the same requirements for Web Beans. Hope it isn't too much trouble however... Paul Bakker drs. ing. Paul Bakker Trainer / Consultant mobiel : +31 (0)6 52 67 13 76 e-mail : paulb(a)infosupport.com Info Support De Smalle Zijde 39 3903 LM Veenendaal tel. : +31 (0)318 50 11 19 fax : +31 (0)318 51 83 59 http://www.infosupport.com/ ________________________________________ From: webbeans-dev-bounces(a)lists.jboss.org [webbeans-dev-bounces(a)lists.jboss.org] On Behalf Of Pete Muir [pmuir(a)redhat.com] Sent: 18 August 2009 19:11 To: webbeans-dev(a)lists.jboss.org Cc: ee6jboss-int(a)sun.com Subject: [webbeans-dev] Java 6? Hi all, I want to gather some feedback on whether everyone is happy if we make Java 6 a requirement for Web Beans. This will simplify the build slightly. JBoss 5.2 will require Java 6 (AFAIK), and I assume GlassFish will do as well. Anyone got strong opinions either way? Pete _______________________________________________ webbeans-dev mailing list webbeans-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/webbeans-dev Op dit e-mail bericht is de disclaimer van Info Support van toepassing, zie http://www.infosupport.com/disclaimer

This will be a problem if you try and achieve total world domination with the RI. If you want to leave doors open on the other hand... :) On 18 août 09, at 13:29, Gavin King wrote:

GlassFish v3 does indeed require Java 6 so no issue on our side although I do feel that is will limit WB's standalone use. Jerome On Aug 18, 2009, at 10:11 AM, Pete Muir wrote:

Pete, I think this is a very bad idea. From what I see in my customer base, most companies are very averse to JVM and application server upgrades and there are hardly any production JDK 6 deployments that I see right now. In fact, just a handful of customers have barely upgraded to JDK 5/Java EE 5. I think the CDI RI should remain at the Java EE 5/JDK 5 level. It would make CDI a much easier sell than telling customers they must upgrade to use it, especially in this economic climate. Just my 2 cents... Cheers, Reza ------------------------------------------------------------ Independent Consultant Author, EJB 3 in Action Expert Group Member, Java EE 6 and EJB 3.1 Resin EJB 3.1 Lite Container Lead Pete Muir wrote: