+1 On Tue, Oct 13, 2009 at 10:52 AM, Bruno Aranda <[email protected]>wrote:
> +1 with the project stage sounds good to me! > > 2009/10/13 Simon Lessard <[email protected]> > > +1 for the project stage idea. >> >> >> On Tue, Oct 13, 2009 at 10:28 AM, Michael Concini <[email protected]>wrote: >> >>> What about using project stage to determine which behavior to follow? If >>> we're in production stage we don't check for best performance, but in >>> development/test stages we perform the check. >>> Alternatively, could we at least make it configurable through an >>> org.apache.myfaces param in web.xml so apps that have been fully tested can >>> disable the check? >>> >>> Thanks, >>> Mike >>> >>> >>> Jakob Korherr wrote: >>> >>>> Hi everbody. >>>> >>>> While working on MYFACES-2375, I got stuck at the following scenario: >>>> >>>> Managed bean m1 has a custom scope #{m2.scope} and managed bean m2 has a >>>> custom scope #{m1.scope}. >>>> In this scenario you will get a StackOverflowException when trying to >>>> create one of the two managed beans. >>>> >>>> RI really ends in a StackOverflowException, should MyFaces end in such a >>>> Exception too or detect the cyclic reference and throw an ELException? >>>> >>>> Mike Kienenberger told me the following: "We have a precedent set on >>>> making MyFaces proactive on detecting error conditions in the >>>> configuration." >>>> >>>> The only problem is, that checking the cyclic references would not >>>> happen once at MyFaces startup, but every time a managed bean will be >>>> created, which means it slows down the application. >>>> >>>> What is your opinion on this question? >>>> Vote +1, if you think MyFaces should detect cyclic references in the >>>> managed bean scope. >>>> >>> >>> >> >
