The general consensus appears to be no - so we'll go with that :-)
Regarding Reza's point about EE5/EE6 compatiblity, we have maintained
EE5 compatiblity in nearly all places. Obviously some features, such
as EJB singletons won't be available, and others such as EJB timeout
method won't work in the 1.0.0 release (if I receive sufficient
requests to enable this, we will).
However, given that it is a reasonably large task to fullly integrate
Web Beans into the EJB (+JPA + JTA etc.) container, I suspect most
people who want to use Web Beans outside of EE6 will either use a
container which supports it natively like JBoss AS 5.2 or without the
EJB etc. support in Tomcat. We plan to provide JPA support as an addon
in Tomcat.
On 18 Aug 2009, at 20:46, Reza Rahman 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:
> 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
>
>
>