okay, understood, thanks Karl. i have learned how to avoid the stackoverflow error caused by circular injection, but just recently, I made a change in my software/project, and i experienced the stackoverflow error, and at first, i did not know what caused the exception, but then I ran a local test, and read the stacktrace...in netbeans error/output console...on my development server. the stacktrace (on the production server) was a bit too long for me to decipher; evidently, tomee/tomcat localhost log and/or stderr/catalina logs are easier to read in netbeans output/error console for tomee server. :)
On Thu, Oct 31, 2013 at 10:31 AM, Karl Kildén <karl.kil...@gmail.com> wrote: > In some clear cases it's not supported and this has not changed in CDI > 1.1. However it's never been a limiting factor for me at least since i > normally don't really use dependent beans or any other non normalscoped. > From the CDI 1.1 spec: > > the container is required to support circularities in the bean dependency > graph where at least one bean participating in every circular chain of > dependencies has a normal scope, as defined in [normal_scope]. The > container is not required to support circular chains of dependencies where > every bean participating in the chain has a pseudo-scope. > > > > > On 31 October 2013 15:01, Howard W. Smith, Jr. <smithh032...@gmail.com > >wrote: > > > 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. < > > smithh032...@gmail.com> 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 <strub...@yahoo.de> > > 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." <smithh032...@gmail.com> > > >> >To: MyFaces Discussion <users@myfaces.apache.org>; Mark Struberg < > > >> strub...@yahoo.de> > > >> >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 <strub...@yahoo.de> > > >> 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? > > >> > > > >> > > > >> > > > >> > > > >> > > > > > > > > >
