I've found very few cases where single inheritance has been a problem:
Action -> MyActionBase -> MyAction is a useful pattern.
My personal opinion is that you would be doing yourself a favor by
breaking your aversion to lots of little files. That's why we have
packages :-) Don't fight the framework.
Jeff
>-----Original Message-----
>From: DONNIE HALE [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, March 08, 2001 7:56 AM
>To: [EMAIL PROTECTED]
>Subject: RE: Minimizing Action class proliferation
>
>
>Jeff,
>
>I do understand the flip side of the issue. In our
>environment, one developer "owns" what would be considered the
>related actions. In any case, CVS does a great job of handling
>multiple developers working on the same file. As far as a
>common base class goes, well Java doesn't support multiple
>inheritance and you pretty much already have to extend Action.
>
>All I'm striving for is a little bit of balance between lots
>of little files, the only difference between them being their
>class name and the method they call on the bean; and the need
>for flexibility.
>
>Donnie
>
>
>>>> [EMAIL PROTECTED] 03/08/01 10:47AM >>>
>>From: DONNIE HALE [mailto:[EMAIL PROTECTED]]
>>
>>Thanks for responding. I understand what you're saying re:
>>keeping the action classes simple. However, it still makes the
>>whole cycle more tedious than perhaps it needs to be. It's
>>harder to write "helper" methods, perhaps for bean
>>manipulation, that can be shared across action classes. In the
>>real world, where revision control is being used, you have to
>>make sure to check all the action classes in. And so on.
>>Further, the smaller those action classes are, the more
>>painful it is to have to put each in a separate source file.
>
>Hey, you could implement your *entire* application as a single
>java file
>with inner classes! Wouldn't that be convenient!
>
>I don't quite understand the problem with lots of small files.
> It seems
>to me that this is a good thing. If you want helper methods, put them
>in a common base class.
>
>If you want version control pain, try having 15 developers all working
>on a single file :-)
>
>Jeff
>
>
