<div dir="ltr">In this case, the spec section 5 will just need to be updated then.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 5, 2015 at 6:06 AM, Jozef Hartinger <span dir="ltr"><<a href="mailto:jharting@redhat.com" target="_blank">jharting@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
No, it's not the case that "all CDI 1.0 implementor checks all jars
having beans.xml and then merge the classes to the module bean
archive". Some CDI 1.0 implementations implement the spec properly
including the fine granularity of Chapter 12, some don't and since
the TCK for CDI 1.0 is does not test much in this area it allows
both groups to pass. That was fixed in subsequent TCK releases.<div><div class="h5"><br>
<br>
<div>On 05/04/2015 11:52 PM, Emily Jiang
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">ah. ok. For cdi 1.0, if all the implementor checks
all jars having beans.xml and then merge the classes to the
module bean archive, this will be fine. I think a spec issue
will be raised to update section 5.<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, May 4, 2015 at 8:59 AM, Mark
Struberg <span dir="ltr"><<a href="mailto:struberg@yahoo.de" target="_blank">struberg@yahoo.de</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The
CDI-1.0 TCK initially did not check anything in that regard.
A test got added in a _very_ late version. This was in fact
released AFTER CDI-1.1 was published if I remember
correctly. So this version is not even part of the EE6 TCK…<br>
<br>
LieGrue,<br>
strub<br>
<div>
<div><br>
> Am 04.05.2015 um 09:07 schrieb Jozef Hartinger <<a href="mailto:jharting@redhat.com" target="_blank">jharting@redhat.com</a>>:<br>
><br>
> Yes, chapter 5 is a bit confusing when it comes to
composite Java EE modules. Comments inline:<br>
><br>
> On 05/03/2015 12:20 AM, Emily Jiang wrote:<br>
>> I agree with Mark. I am confused about section
5 and section 12. Weld-2 leaves the work of specifying
the bean archive to the integrator. I am wondering how
the new version of app server using Weld-2 can pass the
CDI 1.1/1.2 CTS at all if the integrator creates its
bean archives based on section 12.<br>
> The TCK for CDI 1.0, 1,1 and 1.2 expect Chapter 12
to be implemented. Therefore, implementing bean archive
as defined in Chapter 12 is the right approach for a
Weld integrator.<br>
>><br>
>> I am guessing CDI 1.1/1.2 cts, the updated
version of CDI 1.0(?), is based on section 5. Can
someone confirm? The spec needs to be updated to remove
the conflict between section 5 and section 12.<br>
>> ---------- Forwarded message ----------<br>
>> From: Emily Jiang <<a href="mailto:emijiang6@googlemail.com" target="_blank">emijiang6@googlemail.com</a>><br>
>> Date: Sat, May 2, 2015 at 10:21 PM<br>
>> Subject: Re: [cdi-dev] bean archives<br>
>> To: Mark Struberg <<a href="mailto:struberg@yahoo.de" target="_blank">struberg@yahoo.de</a>><br>
>><br>
>><br>
>> I agree with Mark. I am confused about section
5 and section 12. Weld-2 leaves the work of specifying
the bean archive to the integrator. I am wondering how
the new version of app server using Weld-2 can pass the
CDI 1.1/1.2 CTS at all if the integrator creates its
bean archives based on section 12.<br>
>><br>
>> I am guessing CDI 1.1/1.2 cts, the updated
version of CDI 1.0(?), is based on section 5. Can
someone confirm? The spec needs to be updated to remove
the conflict between section 5 and section 12.<br>
>><br>
>> On Sat, May 2, 2015 at 3:47 PM, Mark Struberg
<<a href="mailto:struberg@yahoo.de" target="_blank">struberg@yahoo.de</a>>
wrote:<br>
>> Actually the rules are still not clear. Section
5 and 12 contradict each other. The EE6 RI, JBossAS6 and
TomEE and WAS did behave like in section 5 (1 BDA per
ee-module) whereas Weld-2 behaves like in section 12.<br>
>><br>
>> LieGrue,<br>
>> strub<br>
>><br>
>><br>
>><br>
>> On Saturday, 2 May 2015, 10:13, Antoine
Sabot-Durand <<a href="mailto:antoine@sabot-durand.net" target="_blank">antoine@sabot-durand.net</a>>
wrote:<br>
>><br>
>><br>
>> Hi Emily,<br>
>><br>
>> The rules) apply to each jar (archive). There
is no merging, thus an app can contain three types of
archives :<br>
>> Non bean archives,<br>
>> Implicit bean archives,<br>
>> Explicit bean archives.<br>
>><br>
>> Antoine Sabot-Durand<br>
>><br>
>><br>
>> Le 1 mai 2015 à 23:03, Emily Jiang <<a href="mailto:emijiang6@googlemail.com" target="_blank">emijiang6@googlemail.com</a>>
a écrit :<br>
>><br>
>>><br>
>>> I have a question on bean archives.<br>
>>><br>
>>> For the jars under web-inf\lib, are they
individual bean archives or they should be merged with
web-inf\classes files and use the beans.xml under
web-inf\ to form one bean archive?<br>
>>><br>
>>><br>
>>> If they are merged together to form one
bean archive, what will happen if they have their own
beans.xml under Meta-inf dir?<br>
>>><br>
>>> Below is the what spec says, but it does
not mention the jar under web-inf\lib. The spec should
make this situation clear.<br>
>>><br>
>>> In the CDI1.2 spec:<br>
>>> When determining which archives are bean
archives, the container must consider:<br>
>>> • Library jars, EJB jars or application
client jars<br>
>>> • The WEB-INF/classes directory of a war<br>
>>> • Directories in the JVM classpath<br>
>>> The container is not required to support
application client jar bean archives.<br>
>>> A Java EE container is required by the Java
EE specification to support Java EE modules. Other<br>
>>> containers may or may not provide support
for war, EJB jar or rar bean archives.<br>
>>> The beans.xml file must be named:<br>
>>> • META-INF/beans.xml , or,<br>
>>> • in a war, WEB-INF/beans.xml or
WEB-INF/classes/META-INF/beans.xml.<br>
>>><br>
>>><br>
>>><br>
>>> --<br>
>>> Thanks<br>
>>> Emily<br>
>>> =================<br>
>>> Emily Jiang<br>
>>> <a href="mailto:ejiang@apache.org" target="_blank">ejiang@apache.org</a><br>
>>>
_______________________________________________<br>
>>> cdi-dev mailing list<br>
>>> <a href="mailto:cdi-dev@lists.jboss.org" target="_blank">cdi-dev@lists.jboss.org</a><br>
>>> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
>>><br>
>>> Note that for all code provided on this
list, the provider licenses the code under the Apache
License, Version 2 (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>).
For all other ideas provided on this list, the provider
waives all patent and other intellectual property rights
inherent in such information.<br>
>><br>
>> _______________________________________________<br>
>> cdi-dev mailing list<br>
>> <a href="mailto:cdi-dev@lists.jboss.org" target="_blank">cdi-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
>><br>
>> Note that for all code provided on this list,
the provider licenses the code under the Apache License,
Version 2 (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>).
For all other ideas provided on this list, the provider
waives all patent and other intellectual property rights
inherent in such information.<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> --<br>
>> Thanks<br>
>> Emily<br>
>> =================<br>
>> Emily Jiang<br>
>> <a href="mailto:ejiang@apache.org" target="_blank">ejiang@apache.org</a><br>
>><br>
>><br>
>><br>
>> --<br>
>> Thanks<br>
>> Emily<br>
>> =================<br>
>> Emily Jiang<br>
>> <a href="mailto:ejiang@apache.org" target="_blank">ejiang@apache.org</a><br>
>><br>
>><br>
>> _______________________________________________<br>
>> cdi-dev mailing list<br>
>><br>
>> <a href="mailto:cdi-dev@lists.jboss.org" target="_blank">cdi-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
>><br>
>><br>
>> Note that for all code provided on this list,
the provider licenses the code under the Apache License,
Version 2 (<br>
>> <a href="http://www.apache.org/licenses/LICENSE-2.0.html" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>).
For all other ideas provided on this list, the provider
waives all patent and other intellectual property rights
inherent in such information.<br>
><br>
> _______________________________________________<br>
> cdi-dev mailing list<br>
> <a href="mailto:cdi-dev@lists.jboss.org" target="_blank">cdi-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
><br>
> Note that for all code provided on this list, the
provider licenses the code under the Apache License,
Version 2 (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>).
For all other ideas provided on this list, the provider
waives all patent and other intellectual property rights
inherent in such information.<br>
<br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<div>Thanks<br>
Emily<br>
=================<br>
Emily Jiang<br>
<a href="mailto:ejiang@apache.org" target="_blank">ejiang@apache.org</a><br>
</div>
</div>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature">Thanks<br>Emily<br>=================<br>Emily Jiang<br><a href="mailto:ejiang@apache.org" target="_blank">ejiang@apache.org</a><br></div>
</div>