[
https://issues.apache.org/jira/browse/MYFACES-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MYFACES-3734.
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.2.0
Assignee: Leonardo Uribe
I have committed a solution for this one. I think it is ok, but maybe there is
a minor problem because when creating a tag, you usually must have the renderer
type. If null is passed, the tag handler will not be created correctly, so you
need to find out which is the default renderer type. The easy way is create a
dummy component and try to retrieve the value from getRendererType().
> Implement @FacesComponent createTag, namespace and tagName attributes
> ---------------------------------------------------------------------
>
> Key: MYFACES-3734
> URL: https://issues.apache.org/jira/browse/MYFACES-3734
> Project: MyFaces Core
> Issue Type: Task
> Components: JSR-344
> Reporter: Leonardo Uribe
> Assignee: Leonardo Uribe
> Fix For: 2.2.0
>
>
> The trick with this one is add proper metadata in FacesConfig class to
> identify which components has a "component tag definition". The best is
> associate the componentType with the definition.
> When the configuration is read, this information goes to RuntimeConfig and
> finally facelets vdl grab this information and set up the compiler.
> In theory it should be something like the hierarchy of classes we have for
> FacesConfig, but for facelets, but since there is and there will be an
> stronger collaboration between jsf and facelets, it has more sense to put all
> related information into FacesConfig.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
