hi romain, so far users were very happy with @View#basePath, @View#name and @View#extension. the only request we saw was about a simple mechanism to change the default naming-conventions.
with deltaspike that's possible. just use org.apache.deltaspike.jsf.api.config.view.View$DefaultBasePathBuilder and/or org.apache.deltaspike.jsf.api.config.view.View$DefaultFileNameBuilder and/or org.apache.deltaspike.jsf.api.config.view.View$DefaultExtensionBuilder to configure your own implementation/s. (if it makes sense, we can provide multiple implementations and users just configure whatever they need.) regards, gerhard 2013/6/2 Romain Manni-Bucau <[email protected]> > Hi > > We support a nice jsf navigation (strong typed) but i wonder if we shouldnt > look in our config (config resolver) if the page name is not overrided. It > would allow to use templates easily. > > Wdyt? > > If we do it we need to orefix the properties as for global alternatives. >
