So far it&#39;s clear that the current way locales are handled in JSF 2 is not intuitive and requires unnecessary overhead. Since we know this now, how about defining a solution ASAP that can be handled a the implementation level until 2.1 standardizes it at the spec level? This way we can save some unnecessary pain for our developers, and avoid criticism of JSF 2 going forward. Since everybody expects it to work like the current Java platform prefixes, I don&#39;t think a new solution would require a lot of debate.<br>
<br>Thoughts?<br><br>---<br>Kito D. Mann | twitter: kito99 | Author, JSF in Action<br>Virtua, Inc. | <a href="http://www.virtua.com">http://www.virtua.com</a> | JSF/Java EE training and consulting<br><a href="http://www.JSFCentral.com">http://www.JSFCentral.com</a> - JavaServer Faces FAQ, news, and info | twitter: jsfcentral<br>
+1 203-404-4848 x3<br><br>JSF Summit Conference Dec 1st-4th in Orlando: <a href="http://www.jsfsummit.com">http://www.jsfsummit.com</a><br><br>