FYI: returning true will also work, so I am happy to use that as a workaround instead, but I am still puzzled as to why it gets invoked twice? I suspect this is going to cause issues when I need to return an Object.
cheers, Peter ----- Original Message ----- From: "Peter Stavrinides" <[email protected]> To: "Tapestry Mailing List" <[email protected]> Sent: Thursday, 27 October, 2011 13:11:35 GMT +02:00 Athens, Bucharest, Istanbul Subject: Possible regression Tapestry 5.1 to 5.3 Hi all, We noticed some odd behaviour today in one of our apps, it appears when we use the pattern detailed below, the onSuccessFromStep1() event gets invoked twice by Tapestry, this was not the case in 5.1: public abstract class BaseClass { public abstract Object onSuccessFromStep1(); } public class SubClass extends BaseClass{ @Override public Object onSuccessFromStep1() { if (!foundErrors()) incrementStep(); return null; } } Of course a simple workaround is to remove the @Override, but that really defeats the purpose of using a base class. regards, Peter --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
