I've heard rumors of properties for Java 7 -- if you've ever used VB6 classes, you probably have a good idea of what that means; think of a public member which may have read-only, write-only, or read-write access -- which would cause the deprecation of getters/setters.
Scott -----Original Message----- From: Michael Gentry [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2008 9:25 AM To: user@cayenne.apache.org Subject: Re: Java 6 [Was: Cayenne and JAX-WS / JAXB] That seems like a rather short period for Java 1.5. We are just now starting to incorporate some Java 1.5 features here (I convinced them to switch). Java 1.6 is not an option here yet (Apple didn't release it for Tiger). I guess we'll get squeezed by Sun and Apple. :-) I'm kind of looking forward to Java 1.7. Apparently they are going to allow "void" to auto-return "this" so that you can daisy-chain setters. (Something I loved in Objective-C until Distributed Objects changed everything.) http://tech.puredanger.com/java7/#chained /dev/mrg On Tue, May 27, 2008 at 7:15 AM, Andrus Adamchik <[EMAIL PROTECTED]> wrote: > I don't disagree with that (although check the EOL note here [1]), still > this shouldn't matter. Consider that Cayenne being Java 1.4 in the recent > past did not prevent us from fully supporting enums. The mechanism to > develop and test multi-JDK extensions is there, so if we see a benefit, we > can easily start adding Java6-only features. > > To me personally the turning point in my interest in Java 6 was Apple > releasing the JDK for Mac about a month ago. Until then I didn't bother to > look this way. > > Andrus > > [1] http://java.sun.com/javase/downloads/index_jdk5.jsp
