It appears as if Java EE has been out for a wee bit (may?) so we probably should update our Language Policy again. - http://docs.codehaus.org/display/GEOT/2.1+Language > > Our policy is waiting for a dot release before migrating to new > version of the Java language. The GeoTools project will not release a > Java 5 enhanced branch until Java 5.1 is made available. Why? The > GeoServer project, and indeed many uses of the GeoTools toolkit, are > dependent on J2EE. The GeoTools project will migrate when J2EE is made > available under Java 5. > Is the time now? And why would I ask ...
Java EE has been out since May and I wonder how GeoServer fairs in that environment. Is everything okay, or are we going to take the more realistic step and check back when J2EE has been adopted by more major vendors? I would like to know how things are shaping up; do we have work to do? And why I am asking :-) Well I miss Java 5, especially as I consider using hibernate for a few things (storing a catalog, a database agnostic epsg authorty) - annotations are just so much more clean. The other reason (as seen on the GeoAPI list) is that we are failing to catch API mistakes since we are only implementing in Java 1.4. Also running into Java 6 only problems this last week is a bit scary. Cheers, Jody ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
