<div class="gmail_quote">On Thu, Jan 7, 2010 at 9:54 AM, Cay Horstmann <span dir="ltr"><<a href="mailto:cay@horstmann.com">cay@horstmann.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On 01/07/2010 03:43 AM, Pete Muir wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I like the idea of a container-wide setting - it fits with how people<br>
use container instances (people rarely use the same server for<br>
development and production).<br>
<br>
It would also be great to get this pushed into the EE platform - I<br>
know that this has been suggested by the 314 EG, but when I speak to<br>
the EE guys, they also seem keen on this idea...<br>
<br>
</blockquote>
<br></div>
Absolutely. This is something that I have requested for years. An app<br>
server is a development platform, not just a deployment platform.<div><div></div><div class="h5"><br></div></div></blockquote><div> </div><div>We need to make sure this request makes it out of the mailinglist and in front of the Java EE spec leads. Is there a formal way for one spec to propose and enhancement to another spec, other than submitting a JSR? We want to propose it in such a way that they understand that all of us that support it are pushing/voting for it.<br>
<br>-Dan<br></div></div><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>