Ted, while I have no opinion on case, I can say that my comments in these 
threads has been driven entirely from real world experience. This URL:

https://struts.hostedqa.com/project/7/session/suite/list

Maps, via conventions, to com.hostedqa.action.project.session.suite.ListAction

So there, now you have a reason for deep paths, and a reason why today's simple 
wildcards won't work :)

Patrick

> On 8/3/06, Patrick Lightbody
> <[EMAIL PROTECTED]> wrote:
> > Don and I talked in-depth about using wildcards to
> do the style of conventions I am
> >talking about, and we found that it would require a
> much more complex
> implementation of
> > wildcards. Don, can you add to that?
> 
> Why not focus on starting with conventions that are
> achievable with
> the wildcards we already have, and then expand on the
> wilcard
> capability best on actual experience, that *proves* a
> need for more
> complexity.
> 
> I would also suggest that we only add more complexity
> grudgingly and
> only when *required* to do so, not simply to placate
> an arbitrary
> convention that happens, for no particular reason, to
> be popular.
> 
> Case is a good example. Outside of the JavaBean
> design patterns, I
> believe Java itself is indifferent to case. If the
> language doesn't
> care, why should we?
> 
> -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=39339&messageID=78118#78118


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

Reply via email to