If we try to summarize we get: 1) JSF 2) JPA repo 3) servlet module (almost already dev if i understood)
I think it is fine to get these 3 items in 0.5. having only JSF makes DS too much linked to JSF in terms of comm + cdi query is waiting for months, we need something now even if quickly written and matching less features than cdi-query itself. *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/6/3 Mark Struberg <[email protected]> > it's not about focusing on JSF, it's about focusing on JSF for THIS very > release. > > The main focus of DeltaSpike is btw currently on the core and not on JSF... > > LieGrue, > strub > > > > > ----- Original Message ----- > > From: John D. Ament <[email protected]> > > To: [email protected] > > Cc: > > Sent: Monday, 3 June 2013, 15:31 > > Subject: Re: [DISCUSS] deltaspike-0.5 features > > > > -1 for JSF support being a focus, since it makes it look like DS is a JSF > > specific library (of course this is only my opinion). > > > > This was one of the benefits we had in Seam3, since all modules were at > the > > same level (solder being core of course), it didn't prefer any one > > technology over another. > > > > > > On Mon, Jun 3, 2013 at 9:25 AM, Adrian Gonzalez > > <[email protected]>wrote: > > > >> Sorry, forgot : > >> - EAR support. > >> > >> Regards, > >> Adrian > >> > >> ________________________________ > >> De : Adrian Gonzalez <[email protected]> > >> À : "[email protected]" <[email protected]> > >> Envoyé le : Lundi 3 juin 2013 15h18 > >> Objet : Re: [DISCUSS] deltaspike-0.5 features > >> > >> > >> Hello, > >> > >> +1 for me too for : > >> - port the CODI Conversation and related scopes to DS (Group etc.) > >> - port the ViewAccessScope to DS > >> > >> > >> Also, didn't looked if JSF and REST bridge for DS Exception Handling > > where > >> available for 0.4. > >> > >> If not it would be good to have them in 0.5. > >> > >> Thanks, > >> Adrian > >> > >> > >> ________________________________ > >> De : titou10 titou10 <[email protected]> > >> À : [email protected] > >> Envoyé le : Lundi 3 juin 2013 14h43 > >> Objet : Re: [DISCUSS] deltaspike-0.5 features > >> > >> > >> For us DS v0.5 should be focused on the JSF module and particularly > >> on porting CODI scopes top get rid of CODI asap. ie: > >> - port the CODI Conversation and related scopes to DS (Group etc.) > >> - Enhance the WindowScope. (at least > >> https://issues.apache.org/jira/browse/DELTASPIKE-374 ) > >> - port the ViewAccessScope to DS > >> - Tie the current JSF CDIfied ViewScope to a new anotation that can be > >> used for producers (@PageScope ?) to mimic Seam2 "Page Scope". > > Current > >> JSF @ViewScope annotation can only be set on classes. > >> Note that "PageScope" is different from CODI > > "ViewAccessScope". > >> ViewAccessScope live until there are no more referenced by ANY view. > >> PageScope object live in one and only one view until the view is > >> dismissed..) > >> - Clean/update the JSF module documentation > >> Thanks > >> > >> 2013/6/2 hantsy <[email protected]>: > >> > I think the programming way to get the CDI bean via BeanProvider > >> > manually can be accepted... > >> > > >> > I would like the following will be added into the Apache DeltaSpike > as > >> > soon as possible. > >> > > >> > 1. import the CDI query aka the JPA Repository API > >> > 2. improve the JSF scopes and Conversation support(nested, @Begin, > > @End > >> > etc which are supported in Seam2), and add other Seam3 Faces > > facilities, > >> > Formvalidation, inputContainer etc. > >> > 3. improve Security support, Authentication API for social(oAuth, > etc) > >> > and stateless web service...and allow use multi Authenticators in one > >> > project. eg. /rest REST web service use stateless > authentication(eg, > >> > BASIC, Base 64 encoded), other urls select a generic Authenticator. > >> > > >> > > >> > Hantsy > >> > > >> > > >> > On 6/1/2013 23:45, Matt Benson wrote: > >> >> RE Bean Validation, I agree and enthusiastically invite anyone who > > has > >> an > >> >> itch to work on Bean Validation and CDI to come help out > > implementing BV > >> >> 1.1 at Apache BVal :D > >> >> > >> >> Matt > >> >> > >> >> > >> >> On Sat, Jun 1, 2013 at 8:20 AM, Gerhard Petracek < > >> [email protected] > >> >>> wrote: > >> >>> as mentioned earlier i'm not sure about the bv parts (just > > for > >> injection). > >> >>> therefore you just need to enable any bv 1.1 implementation > > (via > >> >>> default-provider) and you get even more. > >> >>> > >> >>> @thomas: > >> >>> the only missing parts besides that are the remaining scopes > > (the rest > >> is > >> >>> in already). > >> >>> > >> >>> imo it's way more important to finish [1]. > >> >>> > >> >>> regards, > >> >>> gerhard > >> >>> > >> >>> [1] https://issues.apache.org/jira/browse/DELTASPIKE-335 > >> >>> > >> >>> > >> >>> > >> >>> 2013/6/1 Thomas Andraschko <[email protected]> > >> >>> > >> >>>> the most important feature are propably: > >> >>>> - finish the extended JSF scopes > >> >>>> - type view navigation > >> >>>> - injection BV artifacts > >> >>>> > >> >>>> so the most users could switch from CODI to DS. We > > currently do not > >> use > >> >>>> more features in the most apps. > >> >>>> > >> >>>> > >> >>>> 2013/6/1 Romain Manni-Bucau <[email protected]> > >> >>>> > >> >>>>> Cdi query stuff would be great too > >> >>>>> Le 1 juin 2013 13:12, "Mark Struberg" > > <[email protected]> a écrit : > >> >>>>> > >> >>>>>> Yes should mainly be a bugfix release with only a > > few new features. > >> >>>>>> > >> >>>>>> LieGrue, > >> >>>>>> strub > >> >>>>>> > >> >>>>>> > >> >>>>>> > >> >>>>>> > >> >>>>>>> ________________________________ > >> >>>>>>> From: John D. Ament > > <[email protected]> > >> >>>>>>> To: [email protected]; Mark Struberg > > <[email protected]> > >> >>>>>>> Cc: deltaspike > > <[email protected]> > >> >>>>>>> Sent: Saturday, 1 June 2013, 13:07 > >> >>>>>>> Subject: Re: [DISCUSS] deltaspike-0.5 features > >> >>>>>>> > >> >>>>>>> > >> >>>>>>> > >> >>>>>>> Mark, > >> >>>>>>> > >> >>>>>>> > >> >>>>>>> A little aggressive based on how long it took > > to get 0.4? Should > >> >>> this > >> >>>>> be > >> >>>>>> a small release then? > >> >>>>>>> > >> >>>>>>> I'd like to add some level of > > BeanValidation support in this > >> >>> release, > >> >>>>>> looks like the CODI and Seam features are pretty > > similar; so adding > >> >>>>> support > >> >>>>>> for a ConstraintValidatorFactory that creates > > injectable references > >> >>>> would > >> >>>>>> be a good one (I was about to kick off that > > email). > >> >>>>>>> > >> >>>>>>> John > >> >>>>>>> > >> >>>>>>> > >> >>>>>>> > >> >>>>>>> On Sat, Jun 1, 2013 at 7:00 AM, Mark Struberg > > <[email protected]> > >> >>>>> wrote: > >> >>>>>>> Hi! > >> >>>>>>>> It's time to go for planing ds-0.5. > >> >>>>>>>> I'd say the release should be pretty > > small this time. Mostly bug > >> >>>> fixes > >> >>>>>> and a few minor enhancements. And max 1 or 2 > > bigger bullet features. > >> >>>>>>>> The goal is to release ds-0.5 end of this > > month. > >> >>>>>>>> > >> >>>>>>>> A few things on the list as I remember so > > far: > >> >>>>>>>> > >> >>>>>>>> * Finish graduation and apply latest > > changes to our Docs. > >> >>>>>>>> * Servlet module. Please add JIRAs which > > feature you like to see > >> in > >> >>>>> this > >> >>>>>> module > >> >>>>>>>> * Improve the JSF module. We still miss a > > few features from CODI > >> >>> and > >> >>>>>> seam-faces > >> >>>>>>>> . improve ClientWindow handling > >> >>>>>>>> . improve the typesafe navigation > >> >>>>>>>> . add @ConfigurationScoped and > > @ViewAccessScoped > >> >>>>>>>> > >> >>>>>>>> > >> >>>>>>>> * Improve the configuration > >> >>>>>>>> . brainstorming about configuration > > 'categories' as requested a > >> >>> few > >> >>>>>> times already > >> >>>>>>>> . ProjectStage and/or property specific > > configuration > >> >>>>>>>> > >> >>>>>>>> > >> >>>>>>>> This DISCUSS will be closed in 72h. New > > feature requests after > >> that > >> >>>>> time > >> >>>>>> will be handled in deltaspike-0.6 (unless they are > > blockers). > >> >>>>>>>> The timeframe I would suggest: > >> >>>>>>>> > >> >>>>>>>> * Implement new features during 2013-06-12 > >> >>>>>>>> * Bugfixing and documentation until > > 2013-06-19 > >> >>>>>>>> * start with the release on 2013-06-23 > >> >>>>>>>> > >> >>>>>>>> > >> >>>>>>>> Any objection, ideas, feedback? > >> >>>>>>>> > >> >>>>>>>> > >> >>>>>>>> txs and LieGrue, > >> >>>>>>>> strub > >> >>>>>>>> > >> >>>>>>>> > >> >>>>>>> > >> >>>>>>> > >> > > >> > -- > >> > Hantsy Bai > >> > Blog: http://hantsy.blogspot.com > >> > LinkedIN: http://www.linkedin.com/in/hantsy > >> > Github: https://github.com/hantsy > >> > > >
