[ http://issues.apache.org/struts/browse/SHALE-328?page=all ]

Gary VanMatre resolved SHALE-328.
---------------------------------

    Resolution: Fixed

This bug was reported by Torsten Krah.  Thanks for the help.

> Clay is not recognizing the converterId attribute when using the generic 
> f:converter
> ------------------------------------------------------------------------------------
>
>                 Key: SHALE-328
>                 URL: http://issues.apache.org/struts/browse/SHALE-328
>             Project: Shale
>          Issue Type: Bug
>          Components: Clay
>    Affects Versions: 1.0.4-SNAPSHOT
>            Reporter: Gary VanMatre
>         Assigned To: Gary VanMatre
>             Fix For: 1.0.4-SNAPSHOT
>
>
> There are several way to associated a converter with a component that is a 
> value holder.  The converter can be defined as a top-level component where 
> the component type corresponds to the converter-id.  Or, the generic 
> f:converter can be associated to a converter using the converterId attribute.
> Consider:
> <component jsfid="f:convertBoolean" componentType="javax.faces.Boolean"/>
>       
> <component jsfid="testlabel1" extends="h:outputLabel"> 
>                  <attributes>
>                     <set name="value" value="true" />         
>                  </attributes>
>                  <converter jsfid="f:convertBoolean"/>
> </component>
>       
> This scenario doesn't work:
>       
> <component jsfid="testlabel2" extends="h:outputLabel"> 
>    <attributes>
>       <set name="value" value="true" />               
>    </attributes>
>    <converter jsfid="f:converter">
>       <attributes>
>           <set name="converterId" value="javax.faces.Boolean"/>
>        </attributes>
>     </converter>
> </component>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to