After writing the last email, I couldn't leave the office with ConnDefinition so awkward, so I went back in and made ConnDefinition abstract and extended it as PoolConnDefinition (you can pass a URL, a Properties, or a String (which will create a URL)) and RawConnDefinition (which is just the wrapped java.sql.Connection). In recompiling everything, there were some exception problems that javac's dependency glitch hadn't caught. I'd tried to move to throwing TownExceptions instead of ConnectionException, DataSetException whenever possible, but this ended up creating more problems than it was worse, so I undid that. Then I also uncovered that Table.java hadn't been updated to the new API, so I deprecated the existing constructor (passing all the String parameters), updated the deprecated one to construct a PoolConnDefinition as it should, and then added a new constructor that passes the ConnDefinition in lieu of the 4 string parameters. After more exception clause reversals back to ConnectionException, DataSetException, things compile and should generally work nicely. Table.java is actually a little cleaner because you don't have to carry the 4 strings in memory, and when you create the supporting data sets, you just pass the single object instead of the 4 previous ones. Hopefully this won't confuse anyone too much. Let me know if anybody has any problems... I'll be testing this a lot more tomorrow hopefully as I work on the taglib. Serge Knystautas Loki Technologies http://www.lokitech.com/ ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Problems?: [EMAIL PROTECTED]
