[jsr-314-open] [jsf2next] PROJECT_STAGE system property configuration

Matthias Wessendorf matzew at apache.org
Wed Jan 20 00:30:43 EST 2010


+1 I am also in fav of that ;-)

On Tue, Jan 19, 2010 at 11:07 PM, Lincoln Baxter, III
<lincolnbaxter at gmail.com> wrote:
> 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.
>
> Lincoln Baxter's Droid
>
> http://ocpsoft.com
> http://scrumshark.com
> Keep it simple.
>
> On Jan 19, 2010 5:03 PM, "Andy Schwartz" <andy.schwartz at oracle.com> wrote:
>
> Ed Burns wrote: >>>>>> >>>>>> On Mon, 18 Jan 2010 15:16:20 -0500, Andy
> Schwartz <andy.schwartz at oracl...
>
> Okay, thanks for the update Ed.  I wasn't aware that there had been push
> back from the Servlet EG on this.
>
> 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.
>
>> In fact, I'm on the phone with Bill Shannon, Roberto Chinnici, Rajiv >
>> Mordani, and the Sun EE a...
>
> Wow, sounds harsh.  I guess I am missing why this is so controversial.
>
> In any case, thanks for raising this (again).
>
> Andy
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf




More information about the jsr-314-open-mirror mailing list