Hey Martin, "less bad" sounds good to me as long as it can be coerced in to a proper implementation in the future or once the Java community can get all their ducks in a row.
Adam -----Original Message----- From: Martin Desruisseaux [mailto:[email protected]] Sent: Sunday, February 24, 2013 12:19 PM To: [email protected] Subject: Re: Blocking issue on XML prefix mapping Hello Adam Le 24/02/13 18:09, Adam Estrada a écrit : > Wow...There definitely seems to be a lot of (continuing) problems > between Java version. Yes... In this case, part of the complication come from the fact that JAXB has a kind of special status in the JDK. It is not a "core" part of the JDK, but rather an external library developed as part of another project (namely Glassfish), then bundled in the JDK. Furthermore, users can override the JAXB bundled in the JDK by an other JAXB version put in the "endorsed" directory. So we have to think about JDK versions and JAXB versions as two almost independent things... > However, I do like the approach you took with making use of > NamespacePrefixMapper in GeoTK as it would appear to cover all the > bases for now (meaning different Java versions). Well... this is the "less bad" approach I have found so far, in the hope that the hack could be removed in the future. > Does anyone know when Java 8 is supposed to be released? According some emails I have seen on the JDK8 mailing list, the first developer previews would be soon. But I guess that the final release would be in a year or so. Martin
