The talk that I've seen is about making use of CDI in more Java EE
technologies. I didn't understand this to mean "below the appserver
level" (if that means below Java EE).
Now there are several Java EE technologies that are used in the
implementation of nucleus, such as JAX-RS. So if those technologies
require CDI, then I could see CDI in nucleus. The intent of nucleus is
not to deliver Java EE technologies. In fact, we've done the opposite,
trying to remove dependencies on Java EE from nucleus, so that
implementations (of Java EE or non-Java EE) technologies that use
nucleus do not drag along unnecessary dependencies. (This is a tough
line to walk.)
Tom
On 10/25/2012 9:49 AM, John Wells wrote:
> Well, I thought there was some talk of expanding the scope of CDI
> below the appserver level in future releases. Hence, it might one day
> make sense to have it in the nucleus distro, right?
>
> On 10/25/2012 8:58 AM, Romain Grecourt wrote:
>> Why would it go into nucleus if it's not bundled in nucleus distro ?
>>
>> On 10/25/2012 02:41 PM, John Wells wrote:
>>> Perhaps it should go even lower, perhaps under main/nucleus/cdi. I
>>> don't know what the implications of that would be though...
>>>
>>> On 10/25/2012 8:29 AM, JJ Snyder wrote:
>>>> The GlassFish cdi integration is currently in 3 modules under
>>>> main/appserver/web. They are:
>>>> - weld-integration
>>>> - weld-integration-fragment
>>>> - weld-integration-test-fragment
>>>>
>>>> There is much more to the CDI integration than just web so it seems
>>>> that these modules should be at a different location. I am
>>>> planning on moving them to main/appserver/cdi. If anyone has any
>>>> suggestions/objections please let me know.
>>>>
>>>> thanks,
>>>> JJ
>>>>
>>>
>