we're not using JSF or any framework so far.
we keep postnuke concepts based around : blocks and themes.
in addition JSF is not final and has been often critisized.
> we're not using JSF or any framework so far.
> we keep postnuke concepts based around : blocks and
JSF provides that functionality , only much more powerfully. Check out the spec - it's a nice separation of UI functionality & style.. you can create custom renderers to implement skinnability, not to mention render your components to other markup languages..
> in addition JSF is not final and has been often
JSF isn't final, true, but that won't be long, and there are already implementations available (the EA version from Sun and a new alpha LGPL implementation at http://sourceforge.net/projects/myfaces/ )
JBoss has often been criticized, as has j2ee.. what specific issues do you have with JSF ?
This might prove an interesting test of the modularity aspects then, since I might create my own set of modules using JSF on top of nuke for Jboss.. :)
in fact each module is responsible to do things
like he wants.
module invocation are made through an url lile
nukes routes that invocation to the target module,
which does what he wants.
on top of that we don't need JSF since perimeter is clearly defined. But if JSF is not too much tied to servlet it would be possible to have modules that use JSF.