Tim Moore wrote:
It seems to me that just making Action an interface wouldn't even solve
your problem. Your problem is that you want to use inheritance for the
template method pattern, but you also want to use inheritance to reuse
functionality from the LookupDispatchAction. The best solution I
> -Original Message-
> From: Erik Hatcher [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, December 05, 2002 1:48 PM
> To: [EMAIL PROTECTED]
> Subject: subclassing frustrations
>
>
> *everything should be an interface* :))
>
> ARG... I'm having some frustrations with the built-in Struts Act
er <[EMAIL PROTECTED]>
Reply-To: "Struts Developers List" <[EMAIL PROTECTED]>
To: Struts Developers List <[EMAIL PROTECTED]>
Subject: Re: subclassing frustrations
Date: Thu, 05 Dec 2002 15:55:16 -0500
Jason Rosenblum wrote:
Erik,
One simple hack is to layer your base
On Thu, 5 Dec 2002, Erik Hatcher wrote:
>
> *everything should be an interface* :))
>
Unless you want to add public methods in some future version -- that
breaks all existing implementations of the interface :-)).
> ARG... I'm having some frustrations with the built-in Struts Actions
> (yeah,
]>
To: Struts Developers List <[EMAIL PROTECTED]>
Subject: Re: subclassing frustrations
Date: Thu, 05 Dec 2002 15:55:16 -0500
Jason Rosenblum wrote:
Erik,
One simple hack is to layer your base Actions on top
of the pre-defined Actions. You could change your
Struts code such that LookupD
Jason Rosenblum wrote:
Erik,
One simple hack is to layer your base Actions on top
of the pre-defined Actions. You could change your
Struts code such that LookupDispatchAction subclasses
BaseAction or BaseAdminAction. It's not convenient but
it should work.
I'm not sure I follow. To invert the
Erik,
One simple hack is to layer your base Actions on top
of the pre-defined Actions. You could change your
Struts code such that LookupDispatchAction subclasses
BaseAction or BaseAdminAction. It's not convenient but
it should work.
Actually, it would be a nice feature if you could
supply Strut
