I'm here backing up Pete (biased from the actual work I did for WB). ;-)
Why this limit?
It's against what we did in the past.
We have a working, but very prototype env, heavily demanded from the
community.
== perfect ;-)
And it shouldn't/doesn't interfere with any other deployment.
== nothing but (WB) community ++
I agree we need some test in the AS testsuite - I'll work on that with
the guys (as I did for Seam).
But apart from that, I'm waiting for more reasonable arguments. ;-)
ps: if you ask me, I would include Bob's work in some new AS config from
default - e.g. rails configuration
Pete Muir wrote:
Do you have a reasoned argument (other than a needing a quick power
trip) about why we should not be pushing new software that we develop
into JBoss AS (clearly marked as a technology preview), to allow early
access and increase the feedback we get?For example, EJB3 was optionally
included in JBoss 4.0.x.
Reading between the lines, I hope that this will address your concerns:
First, please see
https://jira.jboss.org/jira/browse/JBAS-6371 - you can
see that I am suggesting 5.1 as the place to introduce WB.
Second, as I stated earlier (obviously not clearly enough) we built the
integration such that none of the WB libraries are included in the AS or
application classpath unless the deployment is a Web Beans deployment
(as marked by a {META-INF|WEB_INF}/web-beans.xml). Of course, this
doesn't apply to the WB deployers which deploy the app, and push the WB
libraries onto the app classpath. Thus, whether or not WB is stable,
shouldn't affect non-web-bean apps applied to the AS.
On 14 Jan 2009, at 22:11, David M. Lloyd wrote:
> Dimitris, you worded that wrong. You should have said:
>
> "We are ABSOLUTELY NOT integrating Web Beans into 5.0.1. But I will
> ALLOW you to merge a STABLE implementation into 5.1."
>
> Let them know who's boss. :-)
>
> - DML
>
> On 01/14/2009 04:03 PM, Dimitris Andreadis wrote:
>> Shouldn't we leave the webbeans integration for 5.1? (Branch_5_x)
>>
>> 5.0.1 is a bug fixing release...
>> Scott Stark wrote:
>>> In going through the integration of the current webeans 1.0.0.Alpha1
>>> RI with the jbossas-5.0.0.GA release, the number guess example fails
>>> to deploy on startup with:
>>>
>>> Caused by: java.lang.NullPointerException
>>> at
>>>
org.jboss.webbeans.integration.jbossas.ejb3.EjbDiscoveryEnvironment.lookup(EjbDiscoveryEnvironment.java:123)
>>>
>>> at
>>>
org.jboss.webbeans.integration.jbossas.ejb3.EjbDiscoveryEnvironment.<init>(EjbDiscoveryEnvironment.java:41)
>>>
>>> at
>>>
org.jboss.webbeans.integration.jbossas.WebBeanDiscoveryImpl.<init>(WebBeanDiscoveryImpl.java:25)
>>>
>>> ... 65 more
>>> 10:30:59,909 INFO [WebBeansBootstrap] Starting Web Beans RI
>>> 1.0.0.ALPHA1
>>> 10:30:59,909 ERROR [[/webbeans-numberguess]] Exception sending
>>> context initialized event to listener instance of class
>>> org.jboss.webbeans.servlet.WebBeansListener
>>>
>>> So I guess we need to focus on web beans integration tests as well.
>>>
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/jboss-development
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jboss-development
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development