myfaces-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kito Mann <kito.m...@virtua.com>
Subject Re: @FlowScoped, @Named and @ManagedBean
Date Wed, 12 Feb 2014 16:44:52 GMT
Thanks for the info, Karl. Good to know.

On Wednesday, February 12, 2014, Karl Kildén <karl.kilden@gmail.com> wrote:

> This question has been raised on the mailing list several times. The answer
> is always the same:
> Released functionality is mature and stable. 0.X indicates that the API
> might change but so far this has happened like 1-2 times I think and
> probably took 2 minutes to fix for depending projects. The actual impl is
> stable though.
>
> By following the discussion on the mailing list it's quite clear that they
> put effort into not only porting CODI but to enhance it as well. I have
> Deltaspike in production for many, many months with no issues (all though
> not 0.6-SNAPSHOT). And you can assume it's going to be more tested then
> code you include yourself to do something similar.
>
> The parts regarding JSF is stable for 0.6 so getting the support from a
> SNAPSHOT right now and replace with stable release later is not a very
> adventurous.
>
> These are the docs for getting started:
> http://deltaspike.apache.org/jsf.html
>
> cheers
>
>
> On 12 February 2014 11:33, Howard W. Smith, Jr. <smithh032772@gmail.com<javascript:;>
> >wrote:
>
> > On Feb 12, 2014 1:40 AM, "Karl Kildén" <karl.kilden@gmail.com> wrote:
> > >
> > > Deltaspike modules have consistently been usable off the shelf and
> would
> > be
> > > a far better solution then doing tricks to make CODI work.
> >
> > +1
> >
> > >
> > > However using JSF stuff would require you to use 0.6-SNAPSHOT. I would
> > > actually just use @SessionScoped, write a TODO and wait for 0.6 release
> > if
> > > I could. Otherwise I would use SNAPSHOT since the JSF stuff is all
> fixed
> > > for 0.6 afaik.
> >
> > When I experimented with CODI, I used 1.0.6 snapshot and had the same
> thing
> > in mind and then i heard that CODI was dead project, and most likely
> 1.0.6
> > would not be released. And I did hear and recognize that deltaspike is
> > recommended instead of CODI. Someone, please confirm.
> >
> > >
> > >
> > > On 12 February 2014 02:44, Kito Mann <kito.mann@virtua.com> wrote:
> > >
> > > > How mature is DeltaSpike? It's only at 0.05.
> >
> > +1 good question.
> >
> > > >
> > > > On Tuesday, February 11, 2014, Thomas Andraschko <
> > > > andraschko.thomas@gmail.com> wrote:
> > > >
> > > > > Can't you just switch to DS?
> > > > >
> > > > >
> > > > > 2014-02-11 18:46 GMT+01:00 Leonardo Uribe <lu4242@gmail.com
> > <javascript:;>
> > > > > >:
> > > > >
> > > > > > Hi
> > > > > >
> > > > > > CDI implementations does not require to provide anything to
JSF
> in
> > > > > > order to make @FlowScoped to work. The code has been tested
> against
> > > > > > OWB and Weld and it works in both cases.
> > > > > >
> > > > > > But the flow stuff relies on the new ClientWindow API, and that
> > could
> > > > > > cause a conflict with CODI, because CODI provides a solution
for
> > this
> > > > > > part too. In fact, the solution introduced in the standard comes
> > from
> > > > > > CODI.
> > > > > >
> > > > > > In your particular case, the best option is provide a custom
> > > > > > ClientWindowFactory / ClientWindow that implements
> > > > > > ClientWindow.getId() method and grab the value generated by
CODI.
> > > > > > Theorically there is no need of the custom PhaseListener, because
> > the
> > > > > > "attachWindow" step is done in CODI. I haven't tried it but
I
> > suppose
> > > > > > a custom ClientWindow will work.
> > > > > >
> > > > > > regards,
> > > > > >
> > > > > > Leonardo Uribe
> > > > > >
> > > > > > 2014-02-11 11:56 GMT-05:00 l.penet@senat.fr <l.penet@senat.fr>:
> > > > > > > On 11/02/2014 14:51, l.penet@senat.fr wrote:
> > > > > > >>
> > > > > > >> On 11/02/2014 10:28, l.penet@senat.fr wrote:
> > > > > > >>>
> > > > > > >>> On 11/02/2014 03:30, Leonardo Uribe wrote:
> > > > > > >>
> > > > > > >>
> > > > > > >> [...]
> > > > > > >>>>
> > > > > > >>>> @FlowScoped annotation is for CDI only, so
it will not work
> > for
> > > > JSF
> > > > > > >>>> managed beans. In your case, I believe the
bean is
> > instantiated
> > > > but
> > > > > it
> > > > > > >>>> is not stored in any context, so once is created
is
> discarded,
> > > > > giving
> > > > > > >>>> the impression that the bean is working but
it is not.
> > > > > > >>>>
> > > > > > >>



-- 
___

Kito D. Mann | @kito99 | Author, JSF in Action
Virtua, Inc. | http://www.virtua.com | JSF/Java EE training and consulting
http://www.JSFCentral.com | @jsfcentral
+1 203-998-0403

* Listen to the Enterprise Java Newscast: *http://w
<http://blogs.jsfcentral.com/JSFNewscast/>ww.enterprisejavanews.com
<http://ww.enterprisejavanews.com>*
* JSFCentral Interviews Podcast:
http://www.jsfcentral.com/resources/jsfcentralpodcasts/
* Sign up for the JSFCentral Newsletter: http://oi.vresp.com/?fid=ac048d0e17

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message