So GeoTools requires Java 6? I thought we were still on Java 5? Upgrading is going to be a bit of work for me... but appears i have no choice. I would like to remind folks that when teh proposal to add jaxb as a core dependency was brought up i was against it, but was *assured* that "nothing would be affected". Appears that is not the case.
Jody Garnett wrote: > Justin you should have a different set of dependencies for Java 6; since > jaxb is starting to get folded into Java 6 you will get security / class > cast exception when trying to mix and match the same "class" between two > different classloaders... the JRE gets annoyed when you have classes in > your app that are the same. > > Jody >> Hi all, >> >> I am running into problems with the jaxb module conflicting with the >> version of jaxb that is depended on by the xml parser. The problem is >> i get SecurityException complaining about JAXException: >> >> java.lang.SecurityException: class "javax.xml.bind.JAXBException"'s >> signer information does not match signer information of other classes >> in the same package >> >> It seems to only happen in eclipse. I have also seen the same >> exception in GeoServer and was baffled by it... but it seems this is >> probably the cause. >> >> Any ideas? >> >> > > > !DSPAM:4007,48366532322701439371379! > -- Justin Deoliveira The Open Planning Project [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
