[seam-dev] Seam 3 Internationalization & Localization module ideas / thoughts

[Ken Finnigan]

All,

I'm currently in the process of pulling together some thoughts and ideas 
as to what to include in the new i18n and l10n module within Seam 3.

Here are some initial ideas that have been put forward:

     - Remove all hard dependencies to JSF from within the module
     - i18nable logging
     - Pushing the default locale to JSF and other view layers based on 
the system locale
     - Modify the message interpolation mechanism to remove the use of 
#{} and be consistent with Java by using simply {}
     - The ability for multiple view frameworks to co-exist with the 
appropriate messages being returned to the calling framework.  My 
initial thoughts on this are to convert the existing StatusMessages 
class into a conversational scoped bean which can be used by application 
code to create a message for display.  Then a view framework would 
create the mechanism to convert the StatusMessages content into messages 
appropriate to them.  With JSF this could be achieved by taking the 
existing FacesMessages class and injecting the StatusMessages instance 
(while retaining the extends) to retrieve the messages that are present 
and FacesMessages can be used by SeamPhaseListener as it is now.

Any comments on the above are most welcome, as well as any thoughts 
about what else would be useful to have within this module.

Regards
Ken