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