On Mon, Mar 14, 2011 at 4:01 PM, Dennis Sosnoski <[email protected]> wrote:
> Going from 1.4 to 1.5 gave access to many new features. Going from 1.5 to > 1.6 seems to me to add very little that's useful. > > What do you see as the big advantages of moving to 1.6/Java 6? > Perhaps you are in a better position to answer that question than me :) > > - Dennis > > > > On 03/14/2011 10:17 PM, Afkham Azeez wrote: > > I remember people saying similar things when we were planning to move from > JDK 1.4 to 1.5, and there were many discussions & resistance about the > drastic shift since JDK 1.5 introduced significant changes. There will be > some inertia, but eventually we will have to move on. Regarding the benefits > of migrating to JDK 6, I don't think we can simply classify those as minor, > and ignore it. > > > On Mon, Mar 14, 2011 at 2:14 PM, Dennis Sosnoski <[email protected]> wrote: > >> I'd think that the benefits of moving to Java 6 are minor at best, and >> while most users won't care about the loss of Java 5 support there are >> probably a significant number who will. Andreas' earlier suggestion of a >> Maven profile sounds like it gives a nice way of selectively updating to >> dependencies that require Java 6 without moving the rest of the code to Java >> 6. >> >> - Dennis >> >> Dennis M. Sosnoski >> Java SOA and Web Services Consulting<http://www.sosnoski.com/consult.html> >> Axis2/CXF/Metro SOA and Web Services >> Training<http://www.sosnoski.com/training.html> >> Web Services Jump-Start <http://www.sosnoski.com/jumpstart.html> >> >> On 03/14/2011 05:50 AM, Andreas Veithen wrote: >> >> Oracle will not release any new version of their _free-of-charge_ Java >> 1.5 distribution. That doesn't apply to their commercial offering and >> also doesn't apply to other vendors. E.g. WebSphere 6.1 (the last >> remaining version that uses Java 1.5) will only reach end of service >> in late 2012. >> >> There was a similar discussion recently in the CXF project. They >> concluded that it is too early to drop 1.5 support: >> http://www.mail-archive.com/[email protected]/msg04370.html >> >> I think most of the arguments also apply to Axis2. >> >> Andreas >> >> On Sun, Mar 13, 2011 at 13:49, Afkham Azeez <[email protected]> >> <[email protected]> wrote: >> >> >> I believe Oracle will not release any new JDK 1.5 version to fix security >> issues such >> as http://www.theregister.co.uk/2011/02/07/java_denial_of_service_bug/ >> A JDK 1.6 release was provided a few days after the bug was made public. >> However, they have made a patching tool >> available >> http://www.oracle.com/technetwork/topics/security/alert-cve-2010-4476-305811.html >> >> On Sun, Mar 13, 2011 at 6:02 PM, Andreas Veithen <[email protected]> >> <[email protected]> >> wrote: >> >> >> I think that the question is not asked in the right way. It's not an >> all-or-nothing thing. We can easily set up a Maven profile so that the >> clustering module is skipped if the build is run on Java 1.5. This >> allows us to remain compatible with Java 1.5 for the rest of the >> framework. We only need to update the release procedure to make sure >> that the release build is done using Java 1.6, so that the clustering >> stuff is included in the binary distributions. It's pretty much the >> same approach that was used for the JAXB2 and JAX-WS support up to >> Axis2 1.4.x. >> >> Note that for many people, upgrading to Java 1.6 represents a huge >> effort because it requires an upgrade of the application server on >> which they deploy their applications. At this point, I don't see >> enough added value that would justify to make this mandatory for the >> entire Axis2 stack. >> >> Andreas >> >> On Sun, Mar 13, 2011 at 12:56, Afkham Azeez <[email protected]> >> <[email protected]> wrote: >> >> >> Thoughts on $subject please. I had to revert a useful Apache Tribes >> upgrade >> since Tomcat no longer supports Java 5. >> >> -- >> Afkham Azeez >> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, >> >> Member; Apache Software Foundation; http://www.apache.org/ >> email: [email protected] cell: <%2B94%2077%203320919>+94 77 3320919 >> blog: http://blog.afkham.org >> twitter: http://twitter.com/afkham_azeez >> linked-in: http://lk.linkedin.com/in/afkhamazeez >> >> Lean . Enterprise . Middleware >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> -- >> Afkham Azeez >> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, >> >> Member; Apache Software Foundation; http://www.apache.org/ >> email: [email protected] cell: <%2B94%2077%203320919>+94 77 3320919 >> blog: http://blog.afkham.org >> twitter: http://twitter.com/afkham_azeez >> linked-in: http://lk.linkedin.com/in/afkhamazeez >> >> Lean . Enterprise . Middleware >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> > > > -- > *Afkham Azeez* > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, > * > * > *Member; Apache Software Foundation; > **http://www.apache.org/*<http://www.apache.org/> > * > email: **[email protected]* <[email protected]>* cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * > linked-in: **http://lk.linkedin.com/in/afkhamazeez* > * > * > *Lean . Enterprise . Middleware* > * > * > > -- *Afkham Azeez* Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, * * *Member; Apache Software Foundation; **http://www.apache.org/*<http://www.apache.org/> * email: **[email protected]* <[email protected]>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* * *
