If I commented the problem in the first place, it's because I like to think of these 'on...' methods as methods without any specific contract, that the framework user can freely overwrite. It's more kind of a suggestion.
yes but this doesn't hold. What happens if you extend an object (yours or not your own) that already implements onAttach() ? We currently in wicket do already have all kinds of internalAttach and things like that that is messy johan
