Hi all, I've moved TSCCM into a separate package and started to factor out some inner classes. As was to be expected, things get worse before they can get better. Due to the private nested classes, some of which are used C-struct-like, there were plenty of direct attribute accesses spread in the code. I had to implement accessors and partially increase visibility of attributes to keep the stuff compiling. On the plus side, TSCCM itself is now down to less than 1000 lines. The next step is to factor out TSCCM.ConnectionPool. Once that is done, I can start to clean up the mess of object relations, visible attributes, public accessors, poorly chosen class names, missing JavaDocs, and so on.
Still, prospects are bright. The code will become more open though. There is little chance to prevent applications from downcasting a connection wrapper and retrieving references to classes which are not meant to be used by applications. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
