Hi Thomas.
>The idea is that you can have your own JDO implementation.
>Those pieces of code are designed to be generic. However,
>it is not designed that you can replace one or two classes, but
>whole layer.
Okay, I understand this design of JDO. However, I just want to extend the
functionality of DatabaseImpl and TransactionContext. I can reuse 99% of the
existing code of those two classes, so I don't want to write a complete
replacement. Subclassing is the perfect solution to my problem.
I don't see, why it should be problematic to offer three protected "getters" in
DatabaseImpl.
Martin
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
