>
> Now, when doPerform() is public this goal is not achieved anymore.
>
That is correct, to a point.
>
> I suppose there is another purpose of having two methods:
> peform() and doPeform() - some initialization code can be in perform()
> in the low level.
>
> So, if you make public final perform() you can achieve this, and
> others can execute module in correct way by calling perform()
>
Nope, that is unacceptable. For instance, all my actions extend Action, and
I am using perform for all the stuff that is common to my actions. I create
that method final however, to prevent others from accidentally replacing
that code.
> ------
> The same applies to other modules.
>
>
> / Shamil
>
>
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
