<div dir="ltr">Well as of EAP 6.x (Java EE 6) JBoss seems to have them separately also at runtime;-)<div><br></div><div>I don't have a more recent version here, so maybe they'll change it with Wildfly...? </div><div><br></div><div>Kind Regards,</div><div>Werner</div><div class="gmail_extra">
<br><div class="gmail_quote">On Thu, Aug 13, 2015 at 4:00 PM, manfred riem <span dir="ltr"><<a href="mailto:manfred.riem@oracle.com" target="_blank">manfred.riem@oracle.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hi Werner,<br>
<br>
Arjan is correct.<br>
<br>
The runtime classpath will have the impl JSF 2.3 JAR and it will
contain 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 and as such should never be on the server runtime
classpath, but could be used to compile against (and it will contain
only the javax.faces packages)<br>
<br>
Thanks!<br>
<br>
Kind regards,<br>
Manfred Riem<div><div class="h5"><br>
<br>
On 8/13/15, 8:55 AM, Werner Keil wrote:
<blockquote type="cite">
<div dir="ltr">OK, thanks for the clarification.
<div>The way Arjan phrased it sounded like 2.3 would generally
keep them in one place.</div>
<div><br>
</div>
<div>Hence, if separate JARs are something CDI 2 has to
consider, getBeanClass() and other methods must work for
separate API and impl JARs ;-)</div>
<div><br>
</div>
<div>Werner</div>
<div class="gmail_extra">
<br>
<div class="gmail_quote">On Thu, Aug 13, 2015 at 3:44 PM,
Edward Burns <span dir="ltr"><<a href="mailto:edward.burns@oracle.com" target="_blank">edward.burns@oracle.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>>>>>> On Thu, 13 Aug 2015
15:24:00 +0200, Werner Keil <<a href="mailto:werner.keil@gmail.com" target="_blank">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>
</span>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>
<span><font color="#888888"><br>
--<br>
| <a href="mailto:edward.burns@oracle.com" target="_blank">edward.burns@oracle.com</a>
| office: <a href="tel:%2B1%20407%20458%200017" value="+14074580017" target="_blank">+1 407 458 0017</a><br>
| 58 Business days til JavaOne 2015<br>
| 73 Business days til DOAG 2015<br>
</font></span></blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div></div></div>
</blockquote></div><br></div></div>