Nope - I'm for making it protected. IMHO protected should be the default unless there is a good reason to make it private.

Do you have CVS access? Email me privately & I'll change it if you don't.

Cheers,
Scott

boxed wrote:
I have written a custom directory browsing view with webwork, and it works
fine now, but I discovered a rather annoying thing in webwork in the
proccess: ServletDispatchers getActionName() method is private. This forced
me to copy paste the entire code of this class into my directory browse
servlet, when a simple extend and override of getActionName() would've been
enough. Is there some rationale behind using private instead of protected
here that I can't see?

// Anders Hovmöller




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

--

ATLASSIAN - http://www.atlassian.com
Expert J2EE Software, Services and Support
-------------------------------------------------------
Need a simple, powerful way to track and manage issues?
Try JIRA - http://www.atlassian.com/software/jira




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to