John,

I've never worked with SBT in any incarnation, but from messages I've seen here about the OO conversion of the 2.x code, I understand your grief. *s*

I'm also a strong believer that problems in code are better fixed where the problem occurs. But that is problematic when you are trying to derive from a vendor's supplied classlib. Have you looked at some of the design patterns and other relevant topics over on tht fox.wiki?

>>>Bypassing a class's code to try and call the grandparent's code is a sure sign that your class design has problems.
>
>More like 'SBT's code' ...
>
>But that's nothing new<g>.