+1 to add type-safe view-configs described in [1] +0 to add support for enums
regards, gerhard [1] https://cwiki.apache.org/confluence/display/EXTCDI/JSF+Usage#JSFUsage-TypesafeViewConfig 2012/10/18 Gerhard Petracek <[email protected]> > short addition: > > [1] is just the first step. if we agree to add it, we will continue e.g. > with discussions about [2] [3]. > (please notice that [1] is a whole chapter and not just one headline.) > > regards, > gerhard > > [1] > https://cwiki.apache.org/confluence/display/EXTCDI/JSF+Usage#JSFUsage-TypesafeViewConfig > [2] > https://cwiki.apache.org/confluence/display/EXTCDI/JSF+Usage#JSFUsage-Alternativeto@PageBean%28sincev0.9.1%29 > [3] > https://cwiki.apache.org/confluence/display/EXTCDI/JSF+Usage#JSFUsage-InlineViewConfigs%28sincev0.9.3%29 > > > > 2012/10/18 Mark Struberg <[email protected]> > >> Hi folks! >> >> We already discussed this as part of another thread, but it's time to >> find a final solution >> >> What we have so far: >> >> in CODI we have interface + annotation based view configs: >> >> >> https://cwiki.apache.org/confluence/display/EXTCDI/JSF+Usage#JSFUsage-TypesafeViewConfig >> >> You basically write your page structure as interface with sub-interfaces >> and annotate them with features you like to get. >> A nice feature is that you can write JSF actions like the following >> >> Class<? extends ViewConfig> doSomething() { >> .... >> return Admin.EditCustomer.class; >> } >> >> Say goodbye to any clumsy String handling... >> >> >> In Seam3 there is a way to write Enums for approaching something similar. >> Someone has a link for the docs and might join in to explain the strengths >> and weak spots of this approach? >> >> >> txs and LieGrue, >> strub >> > >
