+1, some solid functionality for jsf would be nice. I think we should probably take the multi field validation as part of that.
--- Lincoln Baxter's Droid http://ocpsoft.org "Simpler is better." On Jul 2, 2012 11:19 AM, "Christian Kaltepoth" <[email protected]> wrote: > +1 for starting with JSF in 0.4 > > IMHO it is very important to have JSF support in place soon because > CDI + JSF is a very common application stack. And as soon as there is > some basic integration, people will hopefully start using DS in real > life projects and we will get more feedback. > > Christian > > 2012/7/2 Mark Struberg <[email protected]>: > > really good points. What about starting with JSF in 0.4? > > > > Which of course also means that we need to get 0.3 out of the door soon. > > Which in turn means that we still need to do a bit of review ;) > > > > I'll start a discussion about 0.3 final cleanup. > > > > LieGrue, > > strub > > > > > > > > ----- Original Message ----- > >> From: Cody Lerum <[email protected]> > >> To: [email protected] > >> Cc: > >> Sent: Monday, July 2, 2012 2:48 AM > >> Subject: Missing features for Seam 3 users adoption > >> > >> I'm going to try and outline the three features that I think > >> DeltaSpike is currently missing before we can steer existing Seam 3 > >> users to the project. Once we have these features covered I think we > >> can start picking up some legacy Seam users thus growing the > >> DeltaSpike community. I think these may be the tipping point for some > >> larger adoption. > >> > >> 1. Security + JSF integration: Path level security ie > >> "/private/home.xhtml" and /public/home.xhtml". Includes mechanism > >> to > >> redirect to a view denied page or a login page if not logged in. > >> > >> 2. JSF + Transaction integration: Provide a means to handle > >> transactions for the restore, invoke and render phases. > >> > >> 3. JSF Messages support: Support creating JSF messages and having them > >> displayed after page redirects / conversational boundaries. > >> > >> These might not missing, but are lacking clear steps for a new user to > >> piece the various modules together to provide the required > >> functionality. Might just be a doc issue. > >> > >> Do we still have a published roadmap as I'm having a hard time finding > >> it? If we do have a roadmap, where do these features fit on it and do > >> you think it makes sense to target these specific features. > >> > >> Thanks! > >> > >> -C > >> > > > > -- > Christian Kaltepoth > Blog: http://chkal.blogspot.com/ > Twitter: http://twitter.com/chkal >
