[MYFACES-192] inputParam component

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.0.9m9
• Fix Version/s: 1.1.0
• Environment: All
• Assignee: Unassigned
• Reporter: Rob Decker
• Created: 15/Apr/05 22:28
• Updated: 17/Apr/06 20:48
• Resolved: 19/Aug/05 18:28

Description

inputParam extends inputHidden by adding an attribute, paramValue, which allows value binding predefined form values to a managed bean. For example, if you have a managed bean named searchBean with a setLastModified(Date d) method you can create a hidden form element with a preset date:

<h:form>
<h:commandLink action="searchBean.search">
<x:inputParam value="#

{searchBean.lastModified}

" paramValue="04/05/2005">
<f:convertDateTime type="date" dateStyle="short"/>
</x:inputParam>
</h:commandLink>
</h:form>

renders:

<input type="hidden" value="04/05/2005"/>

When the form is submitted searchBean.setLastModified is called with the Date object. When the link is clicked there is no need to look in the request for the parameters of the search. There is no need to modify the bean if a different search is required. Just create a new form/commandLink and specify the new parameters. I used it to create quick searches: New in last Day/Week/Month using the same bean for a full fledged form that let's the user specify the dates without having to modify the bean or tie it to faces/request to populate it.

The attached archive contains the component package and the required xml fragments for the tld and faces-config.