I wonder if it might have something to do with the superclass signature being:
void activate(EventContext) and the subclass signature being: Object activate(EventContext) I know I've used similar patterns in 5.3, but haven't tried in 5.4 yet. mrg On Wed, Apr 22, 2015 at 6:56 AM, Chris Poulsen <mailingl...@nesluop.dk> wrote: > Hi, > > We have an abstract parent class with an activation handler declared like > this: > > @OnEvent( EventConstants.ACTIVATE ) > void activate( EventContext ec ) (Called) > > And an extending class with an activation handler declared like this: > > @OnEvent( EventConstants.ACTIVATE ) > Object activate( EventContext ec ) (Not called during activation) > > After updating to beta-31 the activation handler in the extending class is > not called anymore. > > Changing the signature to use the naming convention in the extending class > gets things going again: > > Object onActivate( EventContext ec ) (Called after parent activate) > > Has anyone else seen this behavior after upgrading from beta-22? > > -- > Chris >
