<p>Great Ed. Thanks for being proactive. There is no progress in blame. Let's just find shortcomings and improve the situation.</p>
<p>- Dan Allen</p>
<p>Sent from my Android-powered G1 phone:<br>
An open platform for carriers, developers<br>
and consumers.</p>
<p><blockquote type="cite">On Sep 3, 2009 12:49 PM, "Ed Burns" <<a href="mailto:Ed.Burns@sun.com">Ed.Burns@sun.com</a>> wrote:<br><br>>>>>> On Fri, 28 Aug 2009 15:29:12 -0400, Dan Allen <<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.com</a>> said:<br>
<br>
DA> Without putting a lot of thought into it, I had the same opinion when<br>
DA> developing my JSF 2 talk. I'm also interested in the justification for not<br>
DA> using convention over configuration.<br>
<br>
>>>>> On Fri, 28 Aug 2009 22:45:50 +0200, damien Gouyette <<a href="mailto:damien.gouyette@gmail.com">damien.gouyette@gmail.com</a>> said:<br>
<br>
DG> I'm not sur but localized ressources will be easiest packaged ?<br>
<br>
Yes, this is a well known problem. Cay Horstmann harangued me in our<br>
little JavaOne hallway talk [1]. I think it's counter-productive to<br>
talk about blame. It was in the original design and this problem was<br>
not discovered when the design was shared and discussed with the EG. I<br>
searched the jsr-314-eg archives and there was no dissent on this point.<br>
<br>
Spec issue 548 is tracking the resolution of this problem.<br>
<br>
Ed<br>
<br>
[1] <a href="http://bit.ly/cayhallwaytalk" target="_blank">http://bit.ly/cayhallwaytalk</a><br>
<font color="#888888"><br>
--<br>
| <a href="mailto:ed.burns@sun.com">ed.burns@sun.com</a> | office: 408 884 9519 OR x31640<br>
| homepage: | <a href="http://ridingthecrest.com/" target="_blank">http://ridingthecrest.com/</a><br>
</font></blockquote></p>