hi, i found a workaround [1]. you can build the latest version of codi manually or you wait for the nightly build.
regards, gerhard [1] https://issues.apache.org/jira/browse/EXTCDI-191 http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/5/20 Gerhard Petracek <[email protected]> > hi thomas, > > this part of codi hasn't changed since the first release whereas weld > changed a lot. > > regards, > gerhard > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces > > > > 2011/5/20 Ing.Thomas Kernstock <[email protected]> > > Hi Gerhard, >> >> I Think you are right - this problem exists either since Codi 0.9.4 or >> Glassfish3.1(Weld 1.1.1). This explains why I see extra database updates >> (in >> my logfiles) of entities that should have been destroyed allready. On >> Glassfish 3.0.1 with CODI 0.9.3 this worked fine ! >> >> best regards >> Thomas >> >> ___________________________________ >> -----Ursprüngliche Nachricht----- >> Von: Gerhard Petracek [mailto:[email protected]] >> Gesendet: Freitag, 20. Mai 2011 19:35 >> An: MyFaces Discussion >> Betreff: Re: CODI @ViewAccessScoped not cleaned up? >> >> hi gernot, >> >> @PreDestroy will be called after rendering the first page which doesn't >> use >> the bean. >> it looks like a weld bug (i see the same with weld v1.1.1). >> i tested it with owb and it works as expected. >> i'll have a look at it, if there is a possible workaround for weld. >> >> regards, >> gerhard >> >> http://www.irian.at >> >> Your JSF powerhouse - >> JSF Consulting, Development and >> Courses in English and German >> >> Professional Support for Apache MyFaces >> >> >> 2011/5/20 Gernot Pfingstl <[email protected]> >> >> > Hi, >> > >> > I'm using Glassfish 3.1 and CODI 0.9.5 >> > >> > I've a bean A annotated with @ViewAccessScoped. >> > >> > Bean A is used in page1.xhtml. If page1 is called from page1 the state >> > of the bean is preserved (as expected). >> > >> > Then I navigate to page2.xhtml (which does not have any reference to >> > bean A), an then I navigate (from page2) to page3.xhtml (which also >> > does not have any reference to bean A). >> > At this point I supposed bean A has bean invalidated/removed - but a >> > @PreDestroy is never calles >> > >> > Now I navigate (from page3) to page1.xhtml - and bean A has the >> > previous values and not an inital state. >> > >> > Do I misunderstand the @ViewAccessScoped or is there something wrong? >> > >> > regards, >> > Gernot >> > >> >> >
