<p>We should also probably decide and state that configuration defined in web.xml will override the system property.. or visa versa. Though I think the former allows more fine grained control.</p>
<p>Lincoln Baxter's Droid<br>
<a href="http://ocpsoft.com">http://ocpsoft.com</a><br>
<a href="http://scrumshark.com">http://scrumshark.com</a><br>
Keep it simple.</p>
<p><blockquote type="cite">On Jan 19, 2010 5:03 PM, "Andy Schwartz" <<a href="mailto:andy.schwartz@oracle.com">andy.schwartz@oracle.com</a>> wrote:<br><br><p><font color="#500050">Ed Burns wrote:
>>>>>>
>>>>>> On Mon, 18 Jan 2010 15:16:20 -0500, Andy Schwartz <andy.schwartz@oracl...</font></p>
Okay, thanks for the update Ed. I wasn't aware that there had been push back from the Servlet EG on this.<br>
<br>
Personally I don't understand the nature of the objection. In some case fine-grained (application-specific) control is desired. We have addressed this case via the context parameter. There seems to be general agreement in our EG that a system-level property would also be beneficial and in particular would improve the ease of use of this feature for development-time scenarios (ie. no need for a web.xml or JNDI config). Not sure why we need to choose one approach vs. the other. Both serve a purpose.<p>
<font color="#500050">
> In fact, I'm on the phone with Bill Shannon, Roberto Chinnici, Rajiv
> Mordani, and the Sun EE a...</font></p>
Wow, sounds harsh. I guess I am missing why this is so controversial.<br>
<br>
In any case, thanks for raising this (again).<br><font color="#888888">
<br>
Andy<br>
</font></blockquote></p>