OK, that all sounds good. My only request would be then: can we un-deprecate 
the ! syntax and keep it on (by default), while still giving the option to turn 
it off and perhaps set up a "Security conscience" page on the wiki that 
catalogs all these switches?

> On 8/21/06, Patrick Lightbody
> <[EMAIL PROTECTED]> wrote:
> > Sure, I agree with all of that. And I've said I'm
> opening to nailing this down more with
> > conventions and/or annotations. I'm even open to a
> switch to turn it off.
> 
> Which is where we are, right now, today.
> 
> 
> >So let's dig deep and get to a consensus on what we
> think the "right"
> way to recommend
> >working with Struts is.
> 
> I'm all for that (or at least the right ways), and I
> think we all
> would agree that the switch isn't going to be removed
> unless we are
> all happy with whatever alternatives we find.
> 
> As PMC members, we each have the unilateral right to
> veto a change to
> the codebase on technical grounds. If alternatives
> can't accomplish
> what the bang can accomplish, without bloating or
> obfuscating the
> configuration, then I think everyone would agree that
> would be a
> technical ground. (Or at least one of us would: if
> the technical
> ground isn't obvious, all you need is a second.)
> 
> In my own mind, I never thought we'd remove the
> switch before "phase
> 2", when there might be other breaks in backward
> compatiblity.
> 
> Right now, the last thing I want to do is
> disenfranchise the WebWork
> community, because I want guys like Rainer over here
> helping me push
> out Struts 2.0.x releases. :)
> 
> -Ted.
> 
> ------------------------------------------------------
> ---------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
> 
>
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=40932&messageID=81550#81550


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to