On Thu, 2010-12-02 at 21:34, Patricia Shanahan wrote: > I believe that, in order to use the most relevant features of 1.6 we > would have to run with a 1.6 JVM and rt.jar. The question is whether the > gains from going to 1.6, rather than 1.5, are worth the cost. > > We know at least some of the cost of compiling to 1.6, abandoning anyone > who is stuck on 1.5. > > Now I'm trying to probe the cost of compiling to 1.5, but testing with > both 1.5 and 1.6 JVMs. I understand the cost to River developers, > especially the loss of the 1.6 java.util enhancements - and I think it > is a manageable convenience cost. > > Now I'm asking "Does compiling River to 1.5 impose a cost on 1.6 users, > assuming we do QA test against JVM 1.6 as well as JVM 1.5?". > > Patricia
It's probably worth mentioning that int he J2EE world, there are many, many folks out there on JDK 1.5 or earlier (for instance users of Websphere Application Server 6). There's no reason you can't call Jini services from within a web layer (well, to be totally open I haven't tried it under WAS6, but certainly have done it with no issues under Tomcat). So I can see some justification for not mandating JDK 1.6 just yet. Cheers, Greg. -- Greg Trasuk, President StratusCom Manufacturing Systems Inc. - We use information technology to solve business problems on your plant floor. http://stratuscom.com
