News: JSF Component Metadata Proposal from Oracle Published
JSF Central has published a proposal from Oracle for a standardized approach to JSF component metadata. Having a standardized way to provide additional details about JSF user interface components would simplify integration with IDEs like Oracle JDeveloper, Sun Java Studio Creator, and WebSphere Studio. Currently, integrating JSF components with these tools requires a different process for each tool. We invite the community, especially component and tool developers, to provide their feedback.
- Posted by: Kito Mann
- Posted on: August 25 2004 01:55 EDT
A Proposal for Design-Time Metadata for Java Server Faces Components
- JSF Component Metadata Proposal from Oracle Published by Dmitry Namiot on August 25 2004 15:55 EDT
- Re: Writable attribute by Jeffrey Stephenson on August 25 2004 18:54 EDT
- JSF Component Metadata Proposal from Oracle Published by Craig McClanahan on August 25 2004 22:33 EDT
Why do not detect that automatically: do we have setter or not?
Writable attribute:Why do not detect that automatically?http://www.servletsuite.comI agree that it is not common that a component author would want to specify statically in faces-config.xml that a certain attribute or property should be treated by the tool as not writable (read-only). That particular metadata item was originally inspired by JavaBeans. Unless there are good use cases for it, perhaps it shouldn't be part of the final solution.
Our main goal with this proposal was to start a discussion in the Faces Community in the hope that tool vendors and component authors can agree upon a standard set of metadata items and a syntax for specifying them. The proposal includes some ideas for possible metadata items that tools could share, but obviously that whole set is up for debate.
Writable attribute:Why do not detect that automatically: do we have setter or not?Dmitryhttp://www.servletsuite.comThere are going to be cases where you want a property setter to be available for programmatic manipulation in event handlers, but where it should not be manipulated by the page author at design time. One example in the standard JSF components is the "first" property of the UIData component. It is important that event handlers for "Next Page" and "Previous Page" commands be able to manipulate this value to implement paging through a dataset, but it doesn't really make sense for this attribute to be set by the page author.