Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdi-dev] About parsing beans.xml files in Lite
  • From: Manfred Riem <m_riem@xxxxxxxxxxx>
  • Date: Tue, 26 Jan 2021 14:27:43 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=55wlyGFQiICdBDuR4c2WBp817xGCHpKhAMAT3gkezwc=; b=ANY6SSuXydgBuwLbpscGf70c3nHYzLKxSOnfA1u1fjKUY47UeVCVDKt+wxqjdujPAR20LtgMIWqmdH9DD4XULLSuGg9AeQfkPW2jt/1mbCyLIMP7VBtX/sT0e8OMOooB4juz9BOYe7hztkEdTERoubwzNxtF4/GFK78cmtUw+OX42MvxGm7W92J86i1VJaihxT6G5XivwD0IozZYG8oVjDebbXZHxgT6M4erxhk4HLDZsBgT5guPtt5bbfErkFBN9ebfk32WMnicy+WiNGY5Jz7u0XShiGxvIr8EOmyhIGn5TR7P2AtKADYD0W+sfqqGKeZyOZD1to8JVWrfYEUNow==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=MB61jhGBSIS7pm4fczYS0cdGay/LRSll7WEE392r6ujOuCj5kQEkVGmSOZGMdJ5Z9TNtyXoUdkI/myh7T+dlPZbgBHHqE9l0dWrgAj6MDGCO8bx+2zgnRltlmB1pgYszENFNA6c9dzbG7E+LO9c1nj2c6KLMPcWMB5Md39UfCFCVp7l2voKR2k2YWvjUDaYJ3J0sQ0YAqBy0LBuKo9YvolyPR+lOTQxyAoxl6N2da9NhtlcdpfN9pYAOYtRK15/J+WQde5uhr1Ar+S2PLRgj3YjkinnIyTBU02QOQiLZzPQOYpGjb53texrtxncUv6jPtdPSrrEe/Zb9qWvh7AlSVg==
  • Delivered-to: cdi-dev@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/cdi-dev/>
  • List-help: <mailto:cdi-dev-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/cdi-dev>, <mailto:cdi-dev-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/cdi-dev>, <mailto:cdi-dev-request@eclipse.org?subject=unsubscribe>
  • Thread-index: reQXM5giyn30KzavmDp2LwUk75YIhOWjm0OAgAUmcICAA7segIACBDKAgAjm1ACAAH5sEIAAQ7cAgAAAQgCAAAeigIAABpAAgAAR3VCAAA/RgIAAtkqAgABnNYA=
  • Thread-topic: [cdi-dev] About parsing beans.xml files in Lite

Hi,

 

I am sorry you think me asking for the one defining feature is inconvenient and make you feel like going around and around, but from my perspective it is a very important question to answer.

 

What is the one defining feature for CDI itself? I would argue when most folks think about CDI they think Dependency Injection.

 

So my question stands! What would most folks think this to be named variant would stand for?

 

Everything I have heard so far does not tell me that as I have only heard implementation concerns.

 

Thanks!

 

Kind regards,

Manfred Riem

 

From: cdi-dev <cdi-dev-bounces@xxxxxxxxxxx> On Behalf Of Ladislav Thon
Sent: Tuesday, January 26, 2021 1:18 AM
To: cdi-dev@xxxxxxxxxxx
Subject: Re: [cdi-dev] About parsing beans.xml files in Lite

 

Here's my take at "one defining feature", though it really is the same as what Jason wrote: decouple the "initialization" phase (where beans are discovered, extensions executed etc. etc.) from the "runtime" phase (where the application just runs) so that these 2 phases can be executed in 2 different JVM instances.

Note that I already wrote this here on the list at least once. At this point, I feel like we're running around in circles, attacking the same strawman over and over and over and over. That is not productive. How come we got from a very specific quesion on which everyone's opinion would be very much welcome, to debating "what is CDI Lite", again?

LT

On 25. 01. 21 22:25, Jason Greene wrote:

 

Hi Manfred, response inline:

 

 

On Jan 25, 2021, at 2:29 PM, Manfred Riem <m_riem@xxxxxxxxxxx> wrote:

 

-snip-



To clarify if you say subset do you mean that everything that works in this version of CDI would also work in the “Full” version of CDI?

 

As that is what subset means to me. 

 

If you are a CDI API user (e.g. a typical EE developer) then yes. 

 

If you are an integrator extending CDI by distributing an extension then it depends on if the Full implementation chooses to implement the build-compatible extension SPI. In an ideal world we would have one extension SPI, but the problem is that we can’t change/evolve the existing extension SPI without impacting compatibility. Full implementations expect to continue to offer that compatibility so we effectively arrive at two extension SPIs. 

 

-Jason



_______________________________________________
cdi-dev mailing list
cdi-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdi-dev

Back to the top