From: "Simon Kitching" <[EMAIL PROTECTED]> > While compiling the release notes, and checking for API > incompatibilities between releases, it occurred to me that there is a > backward compatibility issue. Am I right in thinking that when > subclassing a class with "protected" members, if the parent class > implementation changes the type of those members then that is a binary > incompatibility with the subclass? You are correct.
> PS: I've tested BeanUtils and Digester against collections-3.0, and: > (a) binaries compiled against collections-2.1 complete all tests ok > when 3.0 is put in the classpath instead of 2.1. > (b) all source compiles against 3.0 fine, and tests run ok. I have avoided commenting on digester/beanutils issues with collections, as I believe the long term proposed solution of separation to be correct (commons components should be pretty isolated). However, at the very least it needs to be made clear in any release notes that digester and beanutils will run correctly with either 2.1 or 3.0. Perhaps that way tomcat can be convinced to change to 3.0. Stephen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
