No, there is no way. We use the same configuration, thus it will be the 'same'. The Problem is that the JSF ProjectStage is a simple Enum and thus cannot be extended. Whereas DS ProjectStage is extensible. If you configure such an extended ProjectStage then JSF will fallback to 'Production' for the JSF core.
LieGrue, strub ----- Original Message ----- > From: Adrian Gonzalez <[email protected]> > To: "[email protected]" > <[email protected]>; Mark Struberg <[email protected]> > Cc: > Sent: Friday, August 24, 2012 11:42 AM > Subject: Re: [DISCUSS] roadmap for deltaspike-0.4-incubating > > Hi Mark, > >> What does _not_ work is defining the ProjectStage via web.xml. > > Is there a way to tell JSF to use DS projectStage instead of web.xml ? > (in this way if I want during development mode to modify current projectStage > from Development to Production, I only have to modify it in one location - > not > in DS AND JSF web.xml) > > > ----- Mail original ----- > De : Mark Struberg <[email protected]> > À : "[email protected]" > <[email protected]> > Cc : > Envoyé le : Vendredi 24 août 2012 11h37 > Objet : Re: [DISCUSS] roadmap for deltaspike-0.4-incubating > > Thanks for your feedback! > > I don't know all the details but the list look good so far. > >> * ProjectStage >> Automatically bind to JSF projectStage > That should work even with 0.3 as we already check the property, environment > and > JNDI locations for it. What does _not_ work is defining the ProjectStage via > web.xml. But we discussed this in CODI quite lengthy and ended up considering > that broken anyway. Reason is that the WAR file shall not change regardless > on > which box you install it (production, staging, ...) > >> * Locale and MessageResolver >> Automatically bind to JSF locale and message. > Definitely! We already designed the whole Message stuff in hindsight of that. > > The others look good as well (but are not my main domain, so others should > review/tweak). > > LieGrue, > strub > > >> ________________________________ >> From: Adrian Gonzalez <[email protected]> >> To: "[email protected]" > <[email protected]>; Mark Struberg > <[email protected]> >> Sent: Friday, August 24, 2012 11:24 AM >> Subject: Re: [DISCUSS] roadmap for deltaspike-0.4-incubating >> >> >> Hi, >> >> >> Very good news for the JSF module ! >> >> >> Is there somewhere the list of expected features for the JSF module ? >> >> >> Here's a list of features that I would personnally use as a JSF > developer in my day to day work (ranking from most used to least used). >> >> If this list doesn't have any sense to you, please just drop the mail ;) >> >> >> * s:viewAction >> >> For those not having JSF 2.2 >> * UIInputContainer >> > http://docs.jboss.org/seam/3/faces/latest/reference/en-US/html/components.html#UIInputContainer >> * Exception >> JSF ExceptionHandler for DS Exception (c.f. Seam Faces Module) >> * ProjectStage >> Automatically bind to JSF projectStage >> * Locale and MessageResolver >> Automatically bind to JSF locale and message. >> * Scopes (CODI ViewAccess, CODI Conversation, ...) >> >> * Security >> >> authentication, El to handle authorization / permission >> something like #{s:hasRole('admin')}, #{identify.login} >> see JSF scenarii > in https://cwiki.apache.org/confluence/display/DeltaSpike/Security+Module+Drafts >> * Theme handling >> >> > http://docs.jboss.org/seam/2.2.2.Final/reference/en-US/html/i18n.html#d0e14307 >> * Seam Application Framework >> Or something similar / simple to use and understand. >> > http://docs.jboss.org/seam/2.2.2.Final/reference/en-US/html/framework.html >> >> Best regards, >> >> >> >> >
