Jim,

Right, that's exactly what I meant, and that's in fact the work around
which I've been using.

My question is really why I need to do this, and if there is a better
way... It forces me to decide whether I'll ever subclass when I code
the parent, which seems unrubyish... I'd rather just code the parent,
and if the child changes the URL, so be it!