[ http://issues.apache.org/jira/browse/MYFACES-307?page=all ]
sean schofield closed MYFACES-307:
----------------------------------
Resolution: Won't Fix
> strict attribute
> ----------------
>
> Key: MYFACES-307
> URL: http://issues.apache.org/jira/browse/MYFACES-307
> Project: MyFaces
> Type: New Feature
> Reporter: Martin Zdila
> Priority: Minor
>
> Hello
> It would be fine to implement strict attribute to JSF components. If this
> attribute was true and binding in value attribute was invalid, then component
> wouldn't be rendered. It is useful if someone use one JSF page whith
> components bounded to backing bean where the bean is not allways of the same
> class.
> For example I have some page.jsp using backing bean BeanCaseA that extends
> BeanCaseGeneric or BeanCaseB that extends BeanCaseGeneric. The bean is
> accessible through beanHolder.beanCase. Then:
> #{beanHolder.beanCase.propertyX} - exists in BeanCaseGeneric (so in BeanCaseA
> and BeanCaseB too)
> #{beanHolder.beanCase.propertyA} - only exists in BeanCaseA
> #{beanHolder.beanCase.propertyB} - only exists in BeanCaseB
> The syntax would be eg:
> <h:outputText value="#{beanHolder.beanCase.propertyX}" strict="false" />
> If strict parameter is't specified then the default value would be true.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
