More notes. The utility class idea doesn't really work because despite having the same name and structure, they're not the same thing. I guess I've been using languages with duck typing a little too long.
This would dictate introducing an interface that the two hierarchies could implement and the utility classes could work with. I'll have to mess around with Velocity to simplify things. -- Kevin On 9/14/07 4:16 PM, "Kevin Menard" <[EMAIL PROTECTED]> wrote: > Answering my first question . . . That's a definite no. The parent class > implementations are quite different. So, I may just have to break down and > create utility classes that accept DOs as arguments. A bit of pain, but > it'll reduce the code duplication.
