<p>We should probably at least address the request in this forum post to make the project stage extensible.</p>
<p><a href="http://wiki.jcp.org/boards/index.php?t=419">http://wiki.jcporg/boards/index.php?t=419</a></p>
<p>- Dan Allen</p>
<p>Sent from my Android-powered phone:<br>
An open platform for carriers, consumers<br>
and developers.</p>
<p><blockquote type="cite">On Jan 6, 2010 12:16 AM, "Cay Horstmann" <<a href="mailto:cay@horstmann.com">cay@horstmann.com</a>> wrote:<br><br><p><font color="#500050">On 01/05/2010 08:14 PM, Ed Burns wrote:
>>>>>>
>>>>>> On Mon, 04 Jan 2010 11:21:50 -0800, Jim Drisco...</font></p>
I think there are two unrelated issues.<br>
<br>
1) Should one be able to change the project stage setting on the fly for a deployed application? Clearly, this is tricky since it affects caching etc., and I agree that it isn't an important use case.<br>
<br>
2) Should there be a way of setting the project stage without touching web.xml? The usecase here would be for apps that can do without web.xml, which is increasingly likely as web fragments catch on. I talked this over with the GlassFish people a few months ago, and they were receptive to the concept of global parameters for all web apps, such as setting the project stage for all apps in a particular server instance.<br>
<br>
Still, this points to the fact that the default for the project stage is probably wrong. For developers and students, not fussing with web.xml is very handy. At deployment time, it's an easy matter to add a web.xml, or a parameter in an existing web.xml, that sets the project stage to production<br>
<br>
Cheers,<br>
<br>
Cay<br><font color="#888888">
<br>
<br>
-- <br>
<br>
Cay S. Horstmann | <a href="http://horstmann.com" target="_blank">http://horstmann.com</a> | mailto:<a href="mailto:cay@horstmann.com" target="_blank">cay@horstmann.com</a><br>
</font></blockquote></p>