which can result in inifinite loop and stackoverflow error. long time ago, i think I heard that CDI 1.1 would solve the stackoverflow error when developer does circular injection, incorrectly, or maybe I did not read something correctly, when i first started using CDI, and trying to avoid the stackoverflow error caused by circular reference.
On Thu, Oct 31, 2013 at 9:53 AM, Howard W. Smith, Jr. < [email protected]> wrote: > I think you called it 'circular injection'[1] and I've seen others call it > circular reference, and for whatever reason, I was under the assumption > that it was called cyclic reference (ever since i started using CDI). > > Circular Injection A->B->A > > [1] Page 26, > http://people.apache.org/~struberg/inso2013/INSO_webdev-cdi-2013.pdf > > > On Thu, Oct 31, 2013 at 9:00 AM, Mark Struberg <[email protected]> wrote: > >> >> >> what do you mean with cyclic reference issue? >> >> there is no such thing for @NormalScoped beans, and for @Dependent it >> will never work. >> >> LieGrue, >> strub >> >> >> >> >> >> >________________________________ >> > From: "Howard W. Smith, Jr." <[email protected]> >> >To: MyFaces Discussion <[email protected]>; Mark Struberg < >> [email protected]> >> >Sent: Thursday, 31 October 2013, 0:12 >> >Subject: Re: Apache CODI x JEE7 Glassfish4 >> > >> > >> > >> >Mark, >> > >> > >> > >> >On Wed, Oct 30, 2013 at 7:05 PM, Mark Struberg <[email protected]> >> wrote: >> > >> > >> >>The main changes in CDI-1.1 have been clarifications. But most of them >> are already implemented in OWB and Weld, even in the CDI-1.0 targetting >> versions. >> >>There have been a few good Extensions in the Extension area, scanning, >> etc in CDI-1.1. >> >> >> >> >> > >> > >> >Hmmm, I thought I heard that CDI-1.1 would address the cyclic reference >> issue that occurs when using CDI. I have been using tomee/openwebbeans, and >> I made a change in my software/app that exposed that the cyclic reference >> issue still occurs. >> > >> > >> >will OWB or CDI 1.1 (or future versions) address the cyclic reference >> issue, or is this up to the developer to ensure their software avoids the >> issue? >> > >> > >> > >> > >> > >
