You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Mike Kienenberger (JIRA)" <de...@myfaces.apache.org> on 2007/03/30 01:05:25 UTC
[jira] Resolved: (TOMAHAWK-942) Renderer set in extended html
component jsp tag handler rather than in component class
[ https://issues.apache.org/jira/browse/TOMAHAWK-942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Kienenberger resolved TOMAHAWK-942.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.1.6-SNAPSHOT
Assignee: Mike Kienenberger
Fixed all of the extended html components and taghandlers to consistently deal with DEFAULT_RENDERER_TYPE in constructor.
> Renderer set in extended html component jsp tag handler rather than in component class
> --------------------------------------------------------------------------------------
>
> Key: TOMAHAWK-942
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-942
> Project: MyFaces Tomahawk
> Issue Type: Bug
> Affects Versions: 1.1.6-SNAPSHOT
> Reporter: Mike Kienenberger
> Assigned To: Mike Kienenberger
> Priority: Minor
> Fix For: 1.1.6-SNAPSHOT
>
>
> A number of the extended html components simply inherit the renderer specified in shared, and then set a different renderer inside of the jsp tag handler. This can break non-jsp viewhandlers (like Facelets and Shale/Clay) since the components have the incorrect renderer specified.
> Setting the correct default renderer type should be done in the component.
> I'll add a list of affected components later, but I recall that this seemed to be the design pattern for all of the extended components.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.