A collection of fishy stuff to look at
Collection handling at multiple places
I'm having the creeping feeling that collection handling happens at multiple (not coordinated) places, so I start a list which collection handlers I occur:
Utility class for obtaining collection handlers. Based on the configuration and supported classes it will return collections suitable for Java 1.1 and Java 1.2 run times.
In org.exolab.castor.builder.BuilderConfiguration.load a public static attribute of JavaNamingImpl is set to configure how JavaNaming should behave... this is not the correct way.