[jira] Commented: (TOMAHAWK-638) Tomahawk Schedule style class attributes are ignored under facelets. (Ex: dayClass, entryClass, etc)

["Mike Kienenberger (JIRA)" <de...@myfaces.apache.org>]

    [ http://issues.apache.org/jira/browse/TOMAHAWK-638?page=comments#action_12436751 ] 
            
Mike Kienenberger commented on TOMAHAWK-638:
--------------------------------------------

Are you sure these are ignored?   Facelets will also report this warning if the attributes are generic (ie, there's no setHeaderClass() attribute, instead a generic UIComponent attribute is used).

The thing to do is to test it first and see if they're still working in spite of the warning.

If so, then we'll change this issue to "change generic attributes to concrete attributes" so it works better with alternate view handlers.

If not, then we'll have to figure out why these attributes aren't working (perhaps the jsp ScheduleTag passes the attribute with a different name to the Schedule component -- that's a bug for non-jsp component handlers).

> Tomahawk Schedule style class attributes are ignored under facelets. (Ex: dayClass, entryClass, etc)
> ----------------------------------------------------------------------------------------------------
>
>                 Key: TOMAHAWK-638
>                 URL: http://issues.apache.org/jira/browse/TOMAHAWK-638
>             Project: MyFaces Tomahawk
>          Issue Type: Bug
>          Components: Schedule
>            Reporter: Mikhail Grushinskiy
>         Assigned To: Jurgen Lust
>            Priority: Minor
>             Fix For: 1.1.4-SNAPSHOT, 1.1.5-SNAPSHOT
>
>
> Tomahawk Schedule style class attributes are ignored under facelets. (Ex: dayClass, entryClass, etc)
> The following are warnings from facelets 
> Property 'headerClass' is not on type: org.apache.myfaces.custom.schedule.HtmlSchedule
> Property 'dayClass' is not on type: org.apache.myfaces.custom.schedule.HtmlSchedule
> facelets 1.1.11
> --MG

-- 
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