<div dir="ltr">Manfred,<div><br></div><div>For Glassfish probably, but at least the version of JBoss we use here (EAP 6) has these JARs separate at runtime, too.</div><div><br></div><div>Werner</div><div class="gmail_extra">
<br><div class="gmail_quote">On Thu, Aug 13, 2015 at 7:02 PM, <span dir="ltr"><<a href="mailto:cdi-dev-request@lists.jboss.org" target="_blank">cdi-dev-request@lists.jboss.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send cdi-dev mailing list submissions to<br>
<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:cdi-dev-request@lists.jboss.org">cdi-dev-request@lists.jboss.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:cdi-dev-owner@lists.jboss.org">cdi-dev-owner@lists.jboss.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of cdi-dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: getBeanClass return value for build-in beans? (Edward Burns)<br>
2. Re: getBeanClass return value for build-in beans? (Werner Keil)<br>
3. Re: getBeanClass return value for build-in beans? (Werner Keil)<br>
4. Re: getBeanClass return value for build-in beans? (manfred riem)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 13 Aug 2015 06:44:24 -0700<br>
From: Edward Burns <<a href="mailto:edward.burns@oracle.com">edward.burns@oracle.com</a>><br>
Subject: Re: [cdi-dev] getBeanClass return value for build-in beans?<br>
To: Werner Keil <<a href="mailto:werner.keil@gmail.com">werner.keil@gmail.com</a>><br>
Cc: Manfred Riem <<a href="mailto:manfred.riem@oracle.com">manfred.riem@oracle.com</a>>, cdi-dev<br>
<<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
Message-ID: <21964.40760.775241.930217@gargle.gargle.HOWL><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
>>>>> On Thu, 13 Aug 2015 15:24:00 +0200, Werner Keil <<a href="mailto:werner.keil@gmail.com">werner.keil@gmail.com</a>> said:<br>
<br>
>> In this particular case it concerns the javax.faces.jar for JSF 2.3.<br>
>> Some vendors split up this archive in two, an API jar and an impl, jar<br>
>> (although for JSF 2.3 we don't really encourage this).<br>
<br>
WK> Could you explain, why the JSF 2.3 API and RI are molded together?<br>
WK> If the API JAR is no longer separate from the RI (as it was till<br>
WK> javax.faces-api-2.2.jar<br>
WK> <<a href="http://search.maven.org/remotecontent?filepath=javax/faces/javax.faces-api/2.2/javax.faces-api-2.2.jar" rel="noreferrer" target="_blank">http://search.maven.org/remotecontent?filepath=javax/faces/javax.faces-api/2.2/javax.faces-api-2.2.jar</a>>)<br>
WK> it seems, every vendor has to build that API JAR from scratch, or carry a<br>
WK> 3-4 MB JAR where the API in 2.2 was just a little under 700kB ?;-|<br>
<br>
We will be producing a separate API artifact for all the JCP<br>
milestones.<br>
<br>
It is very important to note that the for all Java EE API jars,<br>
including JSF, the only supported use is to satisfy compile time<br>
dependencies. Including a Java EE API jar in a runtime classpath is not<br>
supported and may cause unexpected behavior.<br>
<br>
If there is demand we can investigate producing a JSF API jar for<br>
-SNAPSHOT releases as well.<br>
<br>
Ed<br>
<br>
--<br>
| <a href="mailto:edward.burns@oracle.com">edward.burns@oracle.com</a> | office: <a href="tel:%2B1%20407%20458%200017" value="+14074580017">+1 407 458 0017</a><br>
| 58 Business days til JavaOne 2015<br>
| 73 Business days til DOAG 2015<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Thu, 13 Aug 2015 15:55:49 +0200<br>
From: Werner Keil <<a href="mailto:werner.keil@gmail.com">werner.keil@gmail.com</a>><br>
Subject: Re: [cdi-dev] getBeanClass return value for build-in beans?<br>
To: Edward Burns <<a href="mailto:edward.burns@oracle.com">edward.burns@oracle.com</a>><br>
Cc: Manfred Riem <<a href="mailto:manfred.riem@oracle.com">manfred.riem@oracle.com</a>>, cdi-dev<br>
<<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
Message-ID:<br>
<<a href="mailto:CAAGawe0eCfjhTNR5kJSRwYEm9NE45XP6Tf13xUSJQqpxYKvFLA@mail.gmail.com">CAAGawe0eCfjhTNR5kJSRwYEm9NE45XP6Tf13xUSJQqpxYKvFLA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
OK, thanks for the clarification.<br>
The way Arjan phrased it sounded like 2.3 would generally keep them in one<br>
place.<br>
<br>
Hence, if separate JARs are something CDI 2 has to consider, getBeanClass()<br>
and other methods must work for separate API and impl JARs ;-)<br>
<br>
Werner<br>
<br>
On Thu, Aug 13, 2015 at 3:44 PM, Edward Burns <<a href="mailto:edward.burns@oracle.com">edward.burns@oracle.com</a>><br>
wrote:<br>
<br>
> >>>>> On Thu, 13 Aug 2015 15:24:00 +0200, Werner Keil <<br>
> <a href="mailto:werner.keil@gmail.com">werner.keil@gmail.com</a>> said:<br>
><br>
> >> In this particular case it concerns the javax.faces.jar for JSF 2.3.<br>
> >> Some vendors split up this archive in two, an API jar and an impl, jar<br>
> >> (although for JSF 2.3 we don't really encourage this).<br>
><br>
> WK> Could you explain, why the JSF 2.3 API and RI are molded together?<br>
> WK> If the API JAR is no longer separate from the RI (as it was till<br>
> WK> javax.faces-api-2.2.jar<br>
> WK> <<br>
> <a href="http://search.maven.org/remotecontent?filepath=javax/faces/javax.faces-api/2.2/javax.faces-api-2.2.jar" rel="noreferrer" target="_blank">http://search.maven.org/remotecontent?filepath=javax/faces/javax.faces-api/2.2/javax.faces-api-2.2.jar</a><br>
> >)<br>
> WK> it seems, every vendor has to build that API JAR from scratch, or<br>
> carry a<br>
> WK> 3-4 MB JAR where the API in 2.2 was just a little under 700kB ?;-|<br>
><br>
> We will be producing a separate API artifact for all the JCP<br>
> milestones.<br>
><br>
> It is very important to note that the for all Java EE API jars,<br>
> including JSF, the only supported use is to satisfy compile time<br>
> dependencies. Including a Java EE API jar in a runtime classpath is not<br>
> supported and may cause unexpected behavior.<br>
><br>
> If there is demand we can investigate producing a JSF API jar for<br>
> -SNAPSHOT releases as well.<br>
><br>
> Ed<br>
><br>
> --<br>
> | <a href="mailto:edward.burns@oracle.com">edward.burns@oracle.com</a> | office: <a href="tel:%2B1%20407%20458%200017" value="+14074580017">+1 407 458 0017</a><br>
> | 58 Business days til JavaOne 2015<br>
> | 73 Business days til DOAG 2015<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.jboss.org/pipermail/cdi-dev/attachments/20150813/c0e82e18/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.jboss.org/pipermail/cdi-dev/attachments/20150813/c0e82e18/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Thu, 13 Aug 2015 16:13:40 +0200<br>
From: Werner Keil <<a href="mailto:werner.keil@gmail.com">werner.keil@gmail.com</a>><br>
Subject: Re: [cdi-dev] getBeanClass return value for build-in beans?<br>
To: manfred riem <<a href="mailto:manfred.riem@oracle.com">manfred.riem@oracle.com</a>><br>
Cc: Edward Burns <<a href="mailto:edward.burns@oracle.com">edward.burns@oracle.com</a>>, cdi-dev<br>
<<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
Message-ID:<br>
<CAAGawe00BozP+doe487V-0XOfAh0TFRrC7P_mdzN=<a href="mailto:XrQayYfYw@mail.gmail.com">XrQayYfYw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Well as of EAP 6.x (Java EE 6) JBoss seems to have them separately also at<br>
runtime;-)<br>
<br>
I don't have a more recent version here, so maybe they'll change it with<br>
Wildfly...?<br>
<br>
Kind Regards,<br>
Werner<br>
<br>
On Thu, Aug 13, 2015 at 4:00 PM, manfred riem <<a href="mailto:manfred.riem@oracle.com">manfred.riem@oracle.com</a>><br>
wrote:<br>
<br>
> Hi Werner,<br>
><br>
> Arjan is correct.<br>
><br>
> The runtime classpath will have the impl JSF 2.3 JAR and it will contain<br>
> the javax.faces and com.sun.faces packages.<br>
><br>
> The API jar we are referring to will not be part of the runtime classpath<br>
> and as such should never be on the server runtime classpath, but could be<br>
> used to compile against (and it will contain only the javax.faces packages)<br>
><br>
> Thanks!<br>
><br>
> Kind regards,<br>
> Manfred Riem<br>
><br>
><br>
> On 8/13/15, 8:55 AM, Werner Keil wrote:<br>
><br>
> OK, thanks for the clarification.<br>
> The way Arjan phrased it sounded like 2.3 would generally keep them in one<br>
> place.<br>
><br>
> Hence, if separate JARs are something CDI 2 has to consider,<br>
> getBeanClass() and other methods must work for separate API and impl JARs<br>
> ;-)<br>
><br>
> Werner<br>
><br>
> On Thu, Aug 13, 2015 at 3:44 PM, Edward Burns <<a href="mailto:edward.burns@oracle.com">edward.burns@oracle.com</a>><br>
> wrote:<br>
><br>
>> >>>>> On Thu, 13 Aug 2015 15:24:00 +0200, Werner Keil <<br>
>> <a href="mailto:werner.keil@gmail.com">werner.keil@gmail.com</a>> said:<br>
>><br>
>> >> In this particular case it concerns the javax.faces.jar for JSF 2.3.<br>
>> >> Some vendors split up this archive in two, an API jar and an impl, jar<br>
>> >> (although for JSF 2.3 we don't really encourage this).<br>
>><br>
>> WK> Could you explain, why the JSF 2.3 API and RI are molded together?<br>
>> WK> If the API JAR is no longer separate from the RI (as it was till<br>
>> WK> javax.faces-api-2.2.jar<br>
>> WK> <<br>
>> <a href="http://search.maven.org/remotecontent?filepath=javax/faces/javax.faces-api/2.2/javax.faces-api-2.2.jar" rel="noreferrer" target="_blank">http://search.maven.org/remotecontent?filepath=javax/faces/javax.faces-api/2.2/javax.faces-api-2.2.jar</a><br>
>> >)<br>
>> WK> it seems, every vendor has to build that API JAR from scratch, or<br>
>> carry a<br>
>> WK> 3-4 MB JAR where the API in 2.2 was just a little under 700kB ?;-|<br>
>><br>
>> We will be producing a separate API artifact for all the JCP<br>
>> milestones.<br>
>><br>
>> It is very important to note that the for all Java EE API jars,<br>
>> including JSF, the only supported use is to satisfy compile time<br>
>> dependencies. Including a Java EE API jar in a runtime classpath is not<br>
>> supported and may cause unexpected behavior.<br>
>><br>
>> If there is demand we can investigate producing a JSF API jar for<br>
>> -SNAPSHOT releases as well.<br>
>><br>
>> Ed<br>
>><br>
>> --<br>
>> | <a href="mailto:edward.burns@oracle.com">edward.burns@oracle.com</a> | office: <a href="tel:%2B1%20407%20458%200017" value="+14074580017">+1 407 458 0017</a><br>
>> | 58 Business days til JavaOne 2015<br>
>> | 73 Business days til DOAG 2015<br>
>><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.jboss.org/pipermail/cdi-dev/attachments/20150813/e9209dd9/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.jboss.org/pipermail/cdi-dev/attachments/20150813/e9209dd9/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Thu, 13 Aug 2015 09:00:56 -0500<br>
From: manfred riem <<a href="mailto:manfred.riem@oracle.com">manfred.riem@oracle.com</a>><br>
Subject: Re: [cdi-dev] getBeanClass return value for build-in beans?<br>
To: Werner Keil <<a href="mailto:werner.keil@gmail.com">werner.keil@gmail.com</a>><br>
Cc: Edward Burns <<a href="mailto:edward.burns@oracle.com">edward.burns@oracle.com</a>>, cdi-dev<br>
<<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
Message-ID: <<a href="mailto:55CCA318.3040108@oracle.com">55CCA318.3040108@oracle.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi Werner,<br>
<br>
Arjan is correct.<br>
<br>
The runtime classpath will have the impl JSF 2.3 JAR and it will contain<br>
the javax.faces and com.sun.faces packages.<br>
<br>
The API jar we are referring to will not be part of the runtime<br>
classpath and as such should never be on the server runtime classpath,<br>
but could be used to compile against (and it will contain only the<br>
javax.faces packages)<br>
<br>
Thanks!<br>
<br>
Kind regards,<br>
Manfred Riem<br>
<br>
On 8/13/15, 8:55 AM, Werner Keil wrote:<br>
> OK, thanks for the clarification.<br>
> The way Arjan phrased it sounded like 2.3 would generally keep them in<br>
> one place.<br>
><br>
> Hence, if separate JARs are something CDI 2 has to consider,<br>
> getBeanClass() and other methods must work for separate API and impl<br>
> JARs ;-)<br>
><br>
> Werner<br>
><br>
> On Thu, Aug 13, 2015 at 3:44 PM, Edward Burns <<a href="mailto:edward.burns@oracle.com">edward.burns@oracle.com</a><br>
> <mailto:<a href="mailto:edward.burns@oracle.com">edward.burns@oracle.com</a>>> wrote:<br>
><br>
> >>>>> On Thu, 13 Aug 2015 15:24:00 +0200, Werner Keil<br>
> <<a href="mailto:werner.keil@gmail.com">werner.keil@gmail.com</a> <mailto:<a href="mailto:werner.keil@gmail.com">werner.keil@gmail.com</a>>> said:<br>
><br>
> >> In this particular case it concerns the javax.faces.jar for JSF 2.3.<br>
> >> Some vendors split up this archive in two, an API jar and an<br>
> impl, jar<br>
> >> (although for JSF 2.3 we don't really encourage this).<br>
><br>
> WK> Could you explain, why the JSF 2.3 API and RI are molded together?<br>
> WK> If the API JAR is no longer separate from the RI (as it was till<br>
> WK> javax.faces-api-2.2.jar<br>
> WK><br>
> <<a href="http://search.maven.org/remotecontent?filepath=javax/faces/javax.faces-api/2.2/javax.faces-api-2.2.jar" rel="noreferrer" target="_blank">http://search.maven.org/remotecontent?filepath=javax/faces/javax.faces-api/2.2/javax.faces-api-2.2.jar</a>>)<br>
> WK> it seems, every vendor has to build that API JAR from scratch,<br>
> or carry a<br>
> WK> 3-4 MB JAR where the API in 2.2 was just a little under 700kB ?;-|<br>
><br>
> We will be producing a separate API artifact for all the JCP<br>
> milestones.<br>
><br>
> It is very important to note that the for all Java EE API jars,<br>
> including JSF, the only supported use is to satisfy compile time<br>
> dependencies. Including a Java EE API jar in a runtime classpath<br>
> is not<br>
> supported and may cause unexpected behavior.<br>
><br>
> If there is demand we can investigate producing a JSF API jar for<br>
> -SNAPSHOT releases as well.<br>
><br>
> Ed<br>
><br>
> --<br>
> | <a href="mailto:edward.burns@oracle.com">edward.burns@oracle.com</a> <mailto:<a href="mailto:edward.burns@oracle.com">edward.burns@oracle.com</a>> |<br>
> office: <a href="tel:%2B1%20407%20458%200017" value="+14074580017">+1 407 458 0017</a> <tel:%2B1%20407%20458%200017><br>
> | 58 Business days til JavaOne 2015<br>
> | 73 Business days til DOAG 2015<br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.jboss.org/pipermail/cdi-dev/attachments/20150813/914a6fab/attachment.html" rel="noreferrer" target="_blank">http://lists.jboss.org/pipermail/cdi-dev/attachments/20150813/914a6fab/attachment.html</a><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
cdi-dev mailing list<br>
<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" 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" rel="noreferrer" 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>
End of cdi-dev Digest, Vol 57, Issue 8<br>
**************************************<br>
</blockquote></div><br></div></div>