"perwik" wrote : One option would be to see each static content item as one
object and then connect a number of translations to it. Then you show the
translation corresponding to the current locale using the same rules as the
properties files (i.e showing the default locale when the selected locale is
not in the list of supported locales).
Thank you for the idea, but maintenance question is still open in this case. Or
how are you going to populate this object with content: from a data base? Then
a custom-made CMS would be necessary to maintain texts in the database...
By the way content can require for example html to be included. Properties
files don't allow entering html according to my quick test.
So I would prefer simple <ui:include> tag:
<div class="header"><ui:include
src="/WEB-INF/layout/header#{messages['application.fileSuffix']}.xhtml" /></div>
Any concerns?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969271#3969271
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969271
_______________________________________________
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
