|Feedback on the proposal (BEA) [message #566986]
||Mon, 25 July 2005 22:36
| john rohrlich
Registered: July 2009
-------- Tools Section|
1. Add JSF Project nature to any Web Module
Agree with IBM team - adding JSF should be done via the features framework
3. Wizard for creating a new JSF Page
- Question whether we need a wizard - Agree we should use the template -
- JSF page creation should *also* create the backing bean. The template
should support this as well so that the backing bean can automatically
extend a class the user specifies.
- JSF page and backing bean should be handled as unit for the user in
respect to creation, deletion and rename.
-------- Editors for JSF
The proposal calls for two editors, one for JSP pages and one for
faces-config.xml. I support having both editors but I think the big win
will be if the user doesn't need to edit faces-config.xml. I think we
should add to the proposal support for annotations that would reside in
backing beans and perhaps in JSPs that would be used to generate
config.xml. These annotations could also be used to generate struts
mappings or used by other navigation code that vendors might implement.
After all, JSF navigation, like all of JSF is pluggable.
3. Graphical Editor for JSF page
I agree with the IBM feedback that this is a big ticket item but as I
see JSF as largely a view technology I see this feature as critical to
the success of the JSF Tooling Project
What does support for backing beans mean in this context?
Would like to see us create wizards for those cases where round trip
editing isn't likely but provide round trip editors where iteration is
likely such as with data tables.
Powered by FUDForum
. Page generated in 0.32808 seconds