myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Fallows <>
Subject Re: new feature suggestion - strict attribute
Date Thu, 07 Jul 2005 16:20:46 GMT
On 7/6/05, M.Zdila/EpiSoftware Slovakia Ltd. <> wrote:
> 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.
> Is this possible? Or is there some way to do this without modifying MyFaces?

There is no need to add a new "strict" attribute.

This should be solved by binding the rendered attribute appropriately,
attaching the same logic that is described above for

Kind Regards,
John Fallows.

View raw message