You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Martin Zdila (JIRA)" <my...@incubator.apache.org> on 2005/07/07 08:04:09 UTC

[jira] Created: (MYFACES-307) strict attribute

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

[jira] Commented: (MYFACES-307) strict attribute

Posted by "sean schofield (JIRA)" <my...@incubator.apache.org>.
    [ http://issues.apache.org/jira/browse/MYFACES-307?page=comments#action_12315257 ] 

sean schofield commented on MYFACES-307:
----------------------------------------

I agree with John Fallows.  The existing rendered attribute should be able to handle all of your needs.

> 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

[jira] Closed: (MYFACES-307) strict attribute

Posted by "sean schofield (JIRA)" <my...@incubator.apache.org>.
     [ 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