[
https://issues.apache.org/jira/browse/MYFACES-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe updated MYFACES-3308:
------------------------------------
Resolution: Fixed
Fix Version/s: 2.1.4
2.0.10
Assignee: Leonardo Uribe
Status: Resolved (was: Patch Available)
added test case as junit test and fixed other bug in TagConfigLibrary related
to handle xml composite components.
> Allow localized composite components
> ------------------------------------
>
> Key: MYFACES-3308
> URL: https://issues.apache.org/jira/browse/MYFACES-3308
> Project: MyFaces Core
> Issue Type: Improvement
> Components: JSR-314
> Affects Versions: 2.1.3
> Reporter: Michael Kurz
> Assignee: Leonardo Uribe
> Fix For: 2.0.10, 2.1.4
>
> Attachments: MYFACES-3308.patch, MYFACES-3308.patch, MYFACES-3308.zip
>
>
> I tried to make a localized composite components for dynamic localization of
> content on my pages (that goes beyond resource bundles). The basic idea is to
> be able to create composite components with static text and/or components
> (links, images...) for different languages. As a composite component
> basically is a resource I thought something like this should be possible:
> /resources/fragments/fragment01.xhtml
> /resources/de/fragments/fragment01.xhtml
> IMO the spec is a bit unclear on this but I would say it should work. I tried
> it - it did not work. The problem is, that
> CompositeComponentResourceTagHandler gets a resource in the constructor that
> will be used till the death of the webapp. No chance to switch locales.
> My idea is to use a cache holding a resource for every locale.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
