You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Afkham Azeez <af...@gmail.com> on 2011/03/13 12:56:55 UTC
[Axis2] Isn't it time for us to move to Java 6?
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/*<http://www.apache.org/>
*
email: **azeez@wso2.com* <az...@wso2.com>* 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*
*
*
Re: [Axis2] Isn't it time for us to move to Java 6?
Posted by Deepal jayasinghe <de...@gmail.com>.
I agree with Andreas, we've seen issues related with core features but a
very few (significantly less issues) related with java version. I have
no objection and really encourage testing java6, but do not think we
should completely move to java6 (unless we gain something significantly).
Deepal
> We need to take into account the interest of the entire user
> community, not just particular customers of particular companies
> selling particular services. In addition, dropping support for Java
> 1.5 is not going to change things fundamentally for these
> customers/companies:
>
> * We already have developers testing with Java 1.6 and test coverage
> doesn't grow linearly with the number of developers.
> * There is empirical evidence (see the mailing list posts of the last
> few days) that there are some parts of Axis2 that are not regularly
> tested at all. This means that the primary concern with respect to
> testing is not the Java 1.6 vs. 1.5 question.
> * Once Java 1.7 is out, you will again be in a situation where
> different developers use different versions of Java.
>
> Finally, if you want to sell a service, then you need to create some
> added value that justifies the price of the service. If that service
> consists in providing certified distributions of an Open Source
> product, then obviously the added value is created by extensively
> testing the product on some platform. That is not something that the
> volunteer developers in the Open Source project will ever do for you.
> They will always provide the software "as is".
>
> If one takes into account all these things, I don't see how your
> argument could possibly outweigh the arguments given by Dennis and
> Tom.
>
> Andreas
>
> On Thu, Mar 17, 2011 at 03:14, Afkham Azeez <af...@gmail.com> wrote:
>>
>> On Thu, Mar 17, 2011 at 2:33 AM, Andreas Veithen <an...@gmail.com>
>> wrote:
>>> I don't see any empirical evidence that would support the claim that
>>> Axis2 is not sufficiently tested with Java 1.6. How do you come to
>>> that conclusion?
>> What percentage of developers build/test Axis2 on a regular basis on Java
>> 1.6? As providers of commercial support for Axis2 based software, we have
>> seen critical issues related to Java. So much so, some of the minor versions
>> have produced critical production issues. So, having extensively tested
>> Axis2 in a Java 1.5 environment does not satisfy corporate customers. Some
>> customers require the software provider to certify which specific Sun/IBM
>> etc. JDK versions against which the software has been tested.
>> A flat statement like, 'it works on Java 1.5 and above' can be theoretical
>> acceptable, but for all practical purposes, it has no real meaning. In
>> theory, Java is write once run anywhere. In practice, Java is write once,
>> debug everywhere. :)
>>
>>> Andreas
>>>
>>> On Wed, Mar 16, 2011 at 08:21, Afkham Azeez <af...@gmail.com> wrote:
>>>> If you were working for a company which required that their software run
>>>> on
>>>> JDK6 and when you ask the developers whether they have extensively
>>>> tested
>>>> the software on JDK 6, and the answer is, yes, the continuous
>>>> integration
>>>> system runs that, but we developers mostly test it with JDK5, would you
>>>> be
>>>> confident enough to provide an assurance to your management that Axis2
>>>> works
>>>> perfectly on JDK6? Theoretically everything should work fine, but we
>>>> know
>>>> how software behaves :)
>>>>
>>>> On Wed, Mar 16, 2011 at 12:17 PM, Andreas Veithen
>>>> <an...@gmail.com> wrote:
>>>>> If somebody asks that question, the correct answer is that we have
>>>>> automated builds that check every single commit against both Java
>>>>> versions and that our developers are using different Java versions
>>>>> from different vendors on different platforms. I know that some
>>>>> developers use 1.6 because it happened in the past that they committed
>>>>> things to the trunk that broke the build on Java 1.5. These issues
>>>>> were mostly related to the endorsed library stuff in JAX-WS and easy
>>>>> to fix.
>>>>>
>>>>> Maintaining 1.5 compatibility doesn't mean that we force people to
>>>>> stay away from Java 1.6. It also doesn't mean that developers have to
>>>>> use Java 1.5. It only means that developers should watch the
>>>>> notifications from Jenkins and take appropriate actions if they break
>>>>> the build on 1.5. Obviously this may include deciding to drop support
>>>>> for 1.5 if at some point the cost of maintaining 1.5 compatibility
>>>>> becomes too high.
>>>>>
>>>>> Andreas
>>>>>
>>>>> On Wed, Mar 16, 2011 at 05:48, Afkham Azeez <af...@gmail.com> wrote:
>>>>>> What I'm saying is, if somebody asks has Axis2 been thoroughly tested
>>>>>> on
>>>>>> JDK/JRE 6, the best answer we could give is; 'Yes, everything should
>>>>>> work
>>>>>> fine, but we the developers have not rigorously tested it with JDK 6,
>>>>>> nor do
>>>>>> we regularly build it with JDK 6. So yeah, run in on JDK 6 on your
>>>>>> own
>>>>>> risk"
>>>>>>
>>>>>> On Wed, Mar 16, 2011 at 10:14 AM, Afkham Azeez <af...@gmail.com>
>>>>>> wrote:
>>>>>>> What I've been observing is the world is gradually moving away from
>>>>>>> Java
>>>>>>> 5, most of the people who download a JDK download JDK 6. The JRE
>>>>>>> itself
>>>>>>> contains many improvements. Sticking to JDK5 means, Axis2 does not
>>>>>>> get
>>>>>>> tested of Java 6 on a regular basis by the developers, so we cannot
>>>>>>> give
>>>>>>> 100% assurance that everything in Axis2 works fine with Java 6.
>>>>>>>
>>>>>>> On Wed, Mar 16, 2011 at 8:54 AM, Dennis Sosnoski <dm...@sosnoski.com>
>>>>>>> wrote:
>>>>>>>> On 03/16/2011 12:59 AM, Afkham Azeez wrote:
>>>>>>>>
>>>>>>>> On Mon, Mar 14, 2011 at 4:01 PM, Dennis Sosnoski <dm...@sosnoski.com>
>>>>>>>> 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
>>>>>>>> :)
>>>>>>>>
>>>>>>>> I guess I'm confused - I thought you were the one saying we should
>>>>>>>> move
>>>>>>>> to requiring Java 6?
>>>>>>>>
>>>>>>>> One of the main "advances" of Java 6 is the bundling of
>>>>>>>> Sun/Oracle's
>>>>>>>> JAXB
>>>>>>>> and JAX-WS implementations into the base distribution. But that's
>>>>>>>> not
>>>>>>>> really
>>>>>>>> a gain for us on Axis2, since we want to use our own versions
>>>>>>>> instead
>>>>>>>> of the
>>>>>>>> (generally outdated) ones that are present in the distribution.
>>>>>>>> Aside
>>>>>>>> from
>>>>>>>> that, there are a few added classes (with Deque probably the most
>>>>>>>> useful),
>>>>>>>> and some scattered added methods. None of this is going to make any
>>>>>>>> significant difference to the Axis2 codebase, as far as I can see.
>>>>>>>>
>>>>>>>> - Dennis
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Afkham Azeez
>>>>>>> Senior Software Architect & Senior Manager; WSO2,
>>>>>>> Inc.; http://wso2.com,
>>>>>>>
>>>>>>> Member; Apache Software Foundation; http://www.apache.org/
>>>>>>> email: azeez@wso2.com cell: +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
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Afkham Azeez
>>>>>> Senior Software Architect & Senior Manager; WSO2,
>>>>>> Inc.; http://wso2.com,
>>>>>>
>>>>>> Member; Apache Software Foundation; http://www.apache.org/
>>>>>> email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
>>>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>>>
>>>>
>>>>
>>>> --
>>>> Afkham Azeez
>>>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>>>>
>>>> Member; Apache Software Foundation; http://www.apache.org/
>>>> email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>
>>
>> --
>> Afkham Azeez
>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>>
>> Member; Apache Software Foundation; http://www.apache.org/
>> email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: [Axis2] Isn't it time for us to move to Java 6?
Posted by Afkham Azeez <af...@gmail.com>.
On Fri, Mar 18, 2011 at 2:40 AM, Andreas Veithen
<an...@gmail.com>wrote:
> We need to take into account the interest of the entire user
> community, not just particular customers of particular companies
> selling particular services. In addition, dropping support for Java
> 1.5 is not going to change things fundamentally for these
> customers/companies:
>
> * We already have developers testing with Java 1.6 and test coverage
> doesn't grow linearly with the number of developers.
> * There is empirical evidence (see the mailing list posts of the last
> few days) that there are some parts of Axis2 that are not regularly
> tested at all. This means that the primary concern with respect to
> testing is not the Java 1.6 vs. 1.5 question.
> * Once Java 1.7 is out, you will again be in a situation where
> different developers use different versions of Java.
>
> Finally, if you want to sell a service, then you need to create some
> added value that justifies the price of the service. If that service
> consists in providing certified distributions of an Open Source
> product, then obviously the added value is created by extensively
> testing the product on some platform. That is not something that the
> volunteer developers in the Open Source project will ever do for you.
> They will always provide the software "as is".
>
I was speaking with my Apache hat on. I just mentioned our experience at
WSO2 to demonstrate some real world constraints when it comes to putting
software in production. I was not suggesting that the community do the
testing on Java 6 because we want to support commercial customers who are on
Java 6. FYI, we at WSO2 exclusively test Axis2 based products on Java 6. So,
we are confident that it works well on Java 6. However, what I was thinking
was will that be a good enough answer for people who want to download and
use Axis2 on Java 6 in production. I believe incorporating real world
production deployment experience into the development processes & practices
of open source projects would really be beneficial for these projects.
>
> If one takes into account all these things, I don't see how your
> argument could possibly outweigh the arguments given by Dennis and
> Tom.
>
> Andreas
>
> On Thu, Mar 17, 2011 at 03:14, Afkham Azeez <af...@gmail.com> wrote:
> >
> >
> > On Thu, Mar 17, 2011 at 2:33 AM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> I don't see any empirical evidence that would support the claim that
> >> Axis2 is not sufficiently tested with Java 1.6. How do you come to
> >> that conclusion?
> >
> > What percentage of developers build/test Axis2 on a regular basis on Java
> > 1.6? As providers of commercial support for Axis2 based software, we have
> > seen critical issues related to Java. So much so, some of the minor
> versions
> > have produced critical production issues. So, having extensively tested
> > Axis2 in a Java 1.5 environment does not satisfy corporate customers.
> Some
> > customers require the software provider to certify which specific Sun/IBM
> > etc. JDK versions against which the software has been tested.
> > A flat statement like, 'it works on Java 1.5 and above' can be
> theoretical
> > acceptable, but for all practical purposes, it has no real meaning. In
> > theory, Java is write once run anywhere. In practice, Java is write once,
> > debug everywhere. :)
> >
> >>
> >> Andreas
> >>
> >> On Wed, Mar 16, 2011 at 08:21, Afkham Azeez <af...@gmail.com> wrote:
> >> > If you were working for a company which required that their software
> run
> >> > on
> >> > JDK6 and when you ask the developers whether they have extensively
> >> > tested
> >> > the software on JDK 6, and the answer is, yes, the continuous
> >> > integration
> >> > system runs that, but we developers mostly test it with JDK5, would
> you
> >> > be
> >> > confident enough to provide an assurance to your management that Axis2
> >> > works
> >> > perfectly on JDK6? Theoretically everything should work fine, but we
> >> > know
> >> > how software behaves :)
> >> >
> >> > On Wed, Mar 16, 2011 at 12:17 PM, Andreas Veithen
> >> > <an...@gmail.com> wrote:
> >> >>
> >> >> If somebody asks that question, the correct answer is that we have
> >> >> automated builds that check every single commit against both Java
> >> >> versions and that our developers are using different Java versions
> >> >> from different vendors on different platforms. I know that some
> >> >> developers use 1.6 because it happened in the past that they
> committed
> >> >> things to the trunk that broke the build on Java 1.5. These issues
> >> >> were mostly related to the endorsed library stuff in JAX-WS and easy
> >> >> to fix.
> >> >>
> >> >> Maintaining 1.5 compatibility doesn't mean that we force people to
> >> >> stay away from Java 1.6. It also doesn't mean that developers have to
> >> >> use Java 1.5. It only means that developers should watch the
> >> >> notifications from Jenkins and take appropriate actions if they break
> >> >> the build on 1.5. Obviously this may include deciding to drop support
> >> >> for 1.5 if at some point the cost of maintaining 1.5 compatibility
> >> >> becomes too high.
> >> >>
> >> >> Andreas
> >> >>
> >> >> On Wed, Mar 16, 2011 at 05:48, Afkham Azeez <af...@gmail.com>
> wrote:
> >> >> > What I'm saying is, if somebody asks has Axis2 been thoroughly
> tested
> >> >> > on
> >> >> > JDK/JRE 6, the best answer we could give is; 'Yes, everything
> should
> >> >> > work
> >> >> > fine, but we the developers have not rigorously tested it with JDK
> 6,
> >> >> > nor do
> >> >> > we regularly build it with JDK 6. So yeah, run in on JDK 6 on your
> >> >> > own
> >> >> > risk"
> >> >> >
> >> >> > On Wed, Mar 16, 2011 at 10:14 AM, Afkham Azeez <af...@gmail.com>
> >> >> > wrote:
> >> >> >>
> >> >> >> What I've been observing is the world is gradually moving away
> from
> >> >> >> Java
> >> >> >> 5, most of the people who download a JDK download JDK 6. The JRE
> >> >> >> itself
> >> >> >> contains many improvements. Sticking to JDK5 means, Axis2 does not
> >> >> >> get
> >> >> >> tested of Java 6 on a regular basis by the developers, so we
> cannot
> >> >> >> give
> >> >> >> 100% assurance that everything in Axis2 works fine with Java 6.
> >> >> >>
> >> >> >> On Wed, Mar 16, 2011 at 8:54 AM, Dennis Sosnoski <
> dms@sosnoski.com>
> >> >> >> wrote:
> >> >> >>>
> >> >> >>> On 03/16/2011 12:59 AM, Afkham Azeez wrote:
> >> >> >>>
> >> >> >>> On Mon, Mar 14, 2011 at 4:01 PM, Dennis Sosnoski <
> dms@sosnoski.com>
> >> >> >>> 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
> >> >> >>> :)
> >> >> >>>
> >> >> >>> I guess I'm confused - I thought you were the one saying we
> should
> >> >> >>> move
> >> >> >>> to requiring Java 6?
> >> >> >>>
> >> >> >>> One of the main "advances" of Java 6 is the bundling of
> >> >> >>> Sun/Oracle's
> >> >> >>> JAXB
> >> >> >>> and JAX-WS implementations into the base distribution. But that's
> >> >> >>> not
> >> >> >>> really
> >> >> >>> a gain for us on Axis2, since we want to use our own versions
> >> >> >>> instead
> >> >> >>> of the
> >> >> >>> (generally outdated) ones that are present in the distribution.
> >> >> >>> Aside
> >> >> >>> from
> >> >> >>> that, there are a few added classes (with Deque probably the most
> >> >> >>> useful),
> >> >> >>> and some scattered added methods. None of this is going to make
> any
> >> >> >>> significant difference to the Axis2 codebase, as far as I can
> see.
> >> >> >>>
> >> >> >>> - Dennis
> >> >> >>>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Afkham Azeez
> >> >> >> Senior Software Architect & Senior Manager; WSO2,
> >> >> >> Inc.; http://wso2.com,
> >> >> >>
> >> >> >> Member; Apache Software Foundation; http://www.apache.org/
> >> >> >> email: azeez@wso2.com cell: +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
> >> >> >>
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Afkham Azeez
> >> >> > Senior Software Architect & Senior Manager; WSO2,
> >> >> > Inc.; http://wso2.com,
> >> >> >
> >> >> > Member; Apache Software Foundation; http://www.apache.org/
> >> >> > email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
> >> >> For additional commands, e-mail: java-dev-help@axis.apache.org
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Afkham Azeez
> >> > Senior Software Architect & Senior Manager; WSO2, Inc.;
> http://wso2.com,
> >> >
> >> > Member; Apache Software Foundation; http://www.apache.org/
> >> > email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
> >> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>
> >
> >
> >
> > --
> > Afkham Azeez
> > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
> >
> > Member; Apache Software Foundation; http://www.apache.org/
> > email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
--
*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: **azeez@wso2.com* <az...@wso2.com>* 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*
*
*
Re: [Axis2] Isn't it time for us to move to Java 6?
Posted by Andreas Veithen <an...@gmail.com>.
We need to take into account the interest of the entire user
community, not just particular customers of particular companies
selling particular services. In addition, dropping support for Java
1.5 is not going to change things fundamentally for these
customers/companies:
* We already have developers testing with Java 1.6 and test coverage
doesn't grow linearly with the number of developers.
* There is empirical evidence (see the mailing list posts of the last
few days) that there are some parts of Axis2 that are not regularly
tested at all. This means that the primary concern with respect to
testing is not the Java 1.6 vs. 1.5 question.
* Once Java 1.7 is out, you will again be in a situation where
different developers use different versions of Java.
Finally, if you want to sell a service, then you need to create some
added value that justifies the price of the service. If that service
consists in providing certified distributions of an Open Source
product, then obviously the added value is created by extensively
testing the product on some platform. That is not something that the
volunteer developers in the Open Source project will ever do for you.
They will always provide the software "as is".
If one takes into account all these things, I don't see how your
argument could possibly outweigh the arguments given by Dennis and
Tom.
Andreas
On Thu, Mar 17, 2011 at 03:14, Afkham Azeez <af...@gmail.com> wrote:
>
>
> On Thu, Mar 17, 2011 at 2:33 AM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> I don't see any empirical evidence that would support the claim that
>> Axis2 is not sufficiently tested with Java 1.6. How do you come to
>> that conclusion?
>
> What percentage of developers build/test Axis2 on a regular basis on Java
> 1.6? As providers of commercial support for Axis2 based software, we have
> seen critical issues related to Java. So much so, some of the minor versions
> have produced critical production issues. So, having extensively tested
> Axis2 in a Java 1.5 environment does not satisfy corporate customers. Some
> customers require the software provider to certify which specific Sun/IBM
> etc. JDK versions against which the software has been tested.
> A flat statement like, 'it works on Java 1.5 and above' can be theoretical
> acceptable, but for all practical purposes, it has no real meaning. In
> theory, Java is write once run anywhere. In practice, Java is write once,
> debug everywhere. :)
>
>>
>> Andreas
>>
>> On Wed, Mar 16, 2011 at 08:21, Afkham Azeez <af...@gmail.com> wrote:
>> > If you were working for a company which required that their software run
>> > on
>> > JDK6 and when you ask the developers whether they have extensively
>> > tested
>> > the software on JDK 6, and the answer is, yes, the continuous
>> > integration
>> > system runs that, but we developers mostly test it with JDK5, would you
>> > be
>> > confident enough to provide an assurance to your management that Axis2
>> > works
>> > perfectly on JDK6? Theoretically everything should work fine, but we
>> > know
>> > how software behaves :)
>> >
>> > On Wed, Mar 16, 2011 at 12:17 PM, Andreas Veithen
>> > <an...@gmail.com> wrote:
>> >>
>> >> If somebody asks that question, the correct answer is that we have
>> >> automated builds that check every single commit against both Java
>> >> versions and that our developers are using different Java versions
>> >> from different vendors on different platforms. I know that some
>> >> developers use 1.6 because it happened in the past that they committed
>> >> things to the trunk that broke the build on Java 1.5. These issues
>> >> were mostly related to the endorsed library stuff in JAX-WS and easy
>> >> to fix.
>> >>
>> >> Maintaining 1.5 compatibility doesn't mean that we force people to
>> >> stay away from Java 1.6. It also doesn't mean that developers have to
>> >> use Java 1.5. It only means that developers should watch the
>> >> notifications from Jenkins and take appropriate actions if they break
>> >> the build on 1.5. Obviously this may include deciding to drop support
>> >> for 1.5 if at some point the cost of maintaining 1.5 compatibility
>> >> becomes too high.
>> >>
>> >> Andreas
>> >>
>> >> On Wed, Mar 16, 2011 at 05:48, Afkham Azeez <af...@gmail.com> wrote:
>> >> > What I'm saying is, if somebody asks has Axis2 been thoroughly tested
>> >> > on
>> >> > JDK/JRE 6, the best answer we could give is; 'Yes, everything should
>> >> > work
>> >> > fine, but we the developers have not rigorously tested it with JDK 6,
>> >> > nor do
>> >> > we regularly build it with JDK 6. So yeah, run in on JDK 6 on your
>> >> > own
>> >> > risk"
>> >> >
>> >> > On Wed, Mar 16, 2011 at 10:14 AM, Afkham Azeez <af...@gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> What I've been observing is the world is gradually moving away from
>> >> >> Java
>> >> >> 5, most of the people who download a JDK download JDK 6. The JRE
>> >> >> itself
>> >> >> contains many improvements. Sticking to JDK5 means, Axis2 does not
>> >> >> get
>> >> >> tested of Java 6 on a regular basis by the developers, so we cannot
>> >> >> give
>> >> >> 100% assurance that everything in Axis2 works fine with Java 6.
>> >> >>
>> >> >> On Wed, Mar 16, 2011 at 8:54 AM, Dennis Sosnoski <dm...@sosnoski.com>
>> >> >> wrote:
>> >> >>>
>> >> >>> On 03/16/2011 12:59 AM, Afkham Azeez wrote:
>> >> >>>
>> >> >>> On Mon, Mar 14, 2011 at 4:01 PM, Dennis Sosnoski <dm...@sosnoski.com>
>> >> >>> 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
>> >> >>> :)
>> >> >>>
>> >> >>> I guess I'm confused - I thought you were the one saying we should
>> >> >>> move
>> >> >>> to requiring Java 6?
>> >> >>>
>> >> >>> One of the main "advances" of Java 6 is the bundling of
>> >> >>> Sun/Oracle's
>> >> >>> JAXB
>> >> >>> and JAX-WS implementations into the base distribution. But that's
>> >> >>> not
>> >> >>> really
>> >> >>> a gain for us on Axis2, since we want to use our own versions
>> >> >>> instead
>> >> >>> of the
>> >> >>> (generally outdated) ones that are present in the distribution.
>> >> >>> Aside
>> >> >>> from
>> >> >>> that, there are a few added classes (with Deque probably the most
>> >> >>> useful),
>> >> >>> and some scattered added methods. None of this is going to make any
>> >> >>> significant difference to the Axis2 codebase, as far as I can see.
>> >> >>>
>> >> >>> - Dennis
>> >> >>>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Afkham Azeez
>> >> >> Senior Software Architect & Senior Manager; WSO2,
>> >> >> Inc.; http://wso2.com,
>> >> >>
>> >> >> Member; Apache Software Foundation; http://www.apache.org/
>> >> >> email: azeez@wso2.com cell: +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
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Afkham Azeez
>> >> > Senior Software Architect & Senior Manager; WSO2,
>> >> > Inc.; http://wso2.com,
>> >> >
>> >> > Member; Apache Software Foundation; http://www.apache.org/
>> >> > email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
>> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>> >>
>> >
>> >
>> >
>> > --
>> > Afkham Azeez
>> > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>> >
>> > Member; Apache Software Foundation; http://www.apache.org/
>> > email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>
>
>
> --
> Afkham Azeez
> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: [Axis2] Isn't it time for us to move to Java 6?
Posted by Afkham Azeez <af...@gmail.com>.
On Thu, Mar 17, 2011 at 2:33 AM, Andreas Veithen
<an...@gmail.com>wrote:
> I don't see any empirical evidence that would support the claim that
> Axis2 is not sufficiently tested with Java 1.6. How do you come to
> that conclusion?
>
What percentage of developers build/test Axis2 on a regular basis on Java
1.6? As providers of commercial support for Axis2 based software, we have
seen critical issues related to Java. So much so, some of the minor versions
have produced critical production issues. So, having extensively tested
Axis2 in a Java 1.5 environment does not satisfy corporate customers. Some
customers require the software provider to certify which specific Sun/IBM
etc. JDK versions against which the software has been tested.
A flat statement like, 'it works on Java 1.5 and above' can be theoretical
acceptable, but for all practical purposes, it has no real meaning. In
theory, Java is write once run anywhere. In practice, Java is write once,
debug everywhere. :)
>
> Andreas
>
> On Wed, Mar 16, 2011 at 08:21, Afkham Azeez <af...@gmail.com> wrote:
> > If you were working for a company which required that their software run
> on
> > JDK6 and when you ask the developers whether they have extensively tested
> > the software on JDK 6, and the answer is, yes, the continuous integration
> > system runs that, but we developers mostly test it with JDK5, would you
> be
> > confident enough to provide an assurance to your management that Axis2
> works
> > perfectly on JDK6? Theoretically everything should work fine, but we know
> > how software behaves :)
> >
> > On Wed, Mar 16, 2011 at 12:17 PM, Andreas Veithen
> > <an...@gmail.com> wrote:
> >>
> >> If somebody asks that question, the correct answer is that we have
> >> automated builds that check every single commit against both Java
> >> versions and that our developers are using different Java versions
> >> from different vendors on different platforms. I know that some
> >> developers use 1.6 because it happened in the past that they committed
> >> things to the trunk that broke the build on Java 1.5. These issues
> >> were mostly related to the endorsed library stuff in JAX-WS and easy
> >> to fix.
> >>
> >> Maintaining 1.5 compatibility doesn't mean that we force people to
> >> stay away from Java 1.6. It also doesn't mean that developers have to
> >> use Java 1.5. It only means that developers should watch the
> >> notifications from Jenkins and take appropriate actions if they break
> >> the build on 1.5. Obviously this may include deciding to drop support
> >> for 1.5 if at some point the cost of maintaining 1.5 compatibility
> >> becomes too high.
> >>
> >> Andreas
> >>
> >> On Wed, Mar 16, 2011 at 05:48, Afkham Azeez <af...@gmail.com> wrote:
> >> > What I'm saying is, if somebody asks has Axis2 been thoroughly tested
> on
> >> > JDK/JRE 6, the best answer we could give is; 'Yes, everything should
> >> > work
> >> > fine, but we the developers have not rigorously tested it with JDK 6,
> >> > nor do
> >> > we regularly build it with JDK 6. So yeah, run in on JDK 6 on your own
> >> > risk"
> >> >
> >> > On Wed, Mar 16, 2011 at 10:14 AM, Afkham Azeez <af...@gmail.com>
> wrote:
> >> >>
> >> >> What I've been observing is the world is gradually moving away from
> >> >> Java
> >> >> 5, most of the people who download a JDK download JDK 6. The JRE
> itself
> >> >> contains many improvements. Sticking to JDK5 means, Axis2 does not
> get
> >> >> tested of Java 6 on a regular basis by the developers, so we cannot
> >> >> give
> >> >> 100% assurance that everything in Axis2 works fine with Java 6.
> >> >>
> >> >> On Wed, Mar 16, 2011 at 8:54 AM, Dennis Sosnoski <dm...@sosnoski.com>
> >> >> wrote:
> >> >>>
> >> >>> On 03/16/2011 12:59 AM, Afkham Azeez wrote:
> >> >>>
> >> >>> On Mon, Mar 14, 2011 at 4:01 PM, Dennis Sosnoski <dm...@sosnoski.com>
> >> >>> 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
> >> >>> :)
> >> >>>
> >> >>> I guess I'm confused - I thought you were the one saying we should
> >> >>> move
> >> >>> to requiring Java 6?
> >> >>>
> >> >>> One of the main "advances" of Java 6 is the bundling of Sun/Oracle's
> >> >>> JAXB
> >> >>> and JAX-WS implementations into the base distribution. But that's
> not
> >> >>> really
> >> >>> a gain for us on Axis2, since we want to use our own versions
> instead
> >> >>> of the
> >> >>> (generally outdated) ones that are present in the distribution.
> Aside
> >> >>> from
> >> >>> that, there are a few added classes (with Deque probably the most
> >> >>> useful),
> >> >>> and some scattered added methods. None of this is going to make any
> >> >>> significant difference to the Axis2 codebase, as far as I can see.
> >> >>>
> >> >>> - Dennis
> >> >>>
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Afkham Azeez
> >> >> Senior Software Architect & Senior Manager; WSO2,
> >> >> Inc.; http://wso2.com,
> >> >>
> >> >> Member; Apache Software Foundation; http://www.apache.org/
> >> >> email: azeez@wso2.com cell: +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
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Afkham Azeez
> >> > Senior Software Architect & Senior Manager; WSO2, Inc.;
> http://wso2.com,
> >> >
> >> > Member; Apache Software Foundation; http://www.apache.org/
> >> > email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
> >> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>
> >
> >
> >
> > --
> > Afkham Azeez
> > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
> >
> > Member; Apache Software Foundation; http://www.apache.org/
> > email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
--
*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: **azeez@wso2.com* <az...@wso2.com>* 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*
*
*
RE: [Axis2] Isn't it time for us to move to Java 6?
Posted by Tom Jordahl <tj...@adobe.com>.
I agree with Andreas here. I work on commercial software and we always build on a minimum JDK (happens to be 5 at the moment) and we always claim support for that version and above. I do not think that there is any hesitation for consumers of open source software to take a release that supports JDK 5 and above. It has never been my experience that running a newer JDK would be a detriment to adoption.
What I *have* experienced is that for some reason or another, I am stuck on the older JDK and software that requires newer is a *huge* pain to deal with. For instance I embed Axis2 in my system and I need a bug fix (or functionality) in Axis2 1.7, but I can't use it. That is a barrier to adoption.
Since Axis2 is a piece of middleware (generally) in larger systems, it would be much more user friendly to support 5 and above. That coupled with a lack of features in JDK 6 that would make the Axis2 source "better" (unlike for instance generics) seems a compelling reason to continue to stay at the JDK 5 language level, at least for a while longer (like when JDK 7 arrives).
My .02 cents.
Tom Jordahl
-----Original Message-----
From: Andreas Veithen [mailto:andreas.veithen@gmail.com]
Sent: Wednesday, March 16, 2011 5:03 PM
To: java-dev@axis.apache.org
Subject: Re: [Axis2] Isn't it time for us to move to Java 6?
I don't see any empirical evidence that would support the claim that
Axis2 is not sufficiently tested with Java 1.6. How do you come to
that conclusion?
Andreas
On Wed, Mar 16, 2011 at 08:21, Afkham Azeez <af...@gmail.com> wrote:
> If you were working for a company which required that their software run on
> JDK6 and when you ask the developers whether they have extensively tested
> the software on JDK 6, and the answer is, yes, the continuous integration
> system runs that, but we developers mostly test it with JDK5, would you be
> confident enough to provide an assurance to your management that Axis2 works
> perfectly on JDK6? Theoretically everything should work fine, but we know
> how software behaves :)
>
> On Wed, Mar 16, 2011 at 12:17 PM, Andreas Veithen
> <an...@gmail.com> wrote:
>>
>> If somebody asks that question, the correct answer is that we have
>> automated builds that check every single commit against both Java
>> versions and that our developers are using different Java versions
>> from different vendors on different platforms. I know that some
>> developers use 1.6 because it happened in the past that they committed
>> things to the trunk that broke the build on Java 1.5. These issues
>> were mostly related to the endorsed library stuff in JAX-WS and easy
>> to fix.
>>
>> Maintaining 1.5 compatibility doesn't mean that we force people to
>> stay away from Java 1.6. It also doesn't mean that developers have to
>> use Java 1.5. It only means that developers should watch the
>> notifications from Jenkins and take appropriate actions if they break
>> the build on 1.5. Obviously this may include deciding to drop support
>> for 1.5 if at some point the cost of maintaining 1.5 compatibility
>> becomes too high.
>>
>> Andreas
>>
>> On Wed, Mar 16, 2011 at 05:48, Afkham Azeez <af...@gmail.com> wrote:
>> > What I'm saying is, if somebody asks has Axis2 been thoroughly tested on
>> > JDK/JRE 6, the best answer we could give is; 'Yes, everything should
>> > work
>> > fine, but we the developers have not rigorously tested it with JDK 6,
>> > nor do
>> > we regularly build it with JDK 6. So yeah, run in on JDK 6 on your own
>> > risk"
>> >
>> > On Wed, Mar 16, 2011 at 10:14 AM, Afkham Azeez <af...@gmail.com> wrote:
>> >>
>> >> What I've been observing is the world is gradually moving away from
>> >> Java
>> >> 5, most of the people who download a JDK download JDK 6. The JRE itself
>> >> contains many improvements. Sticking to JDK5 means, Axis2 does not get
>> >> tested of Java 6 on a regular basis by the developers, so we cannot
>> >> give
>> >> 100% assurance that everything in Axis2 works fine with Java 6.
>> >>
>> >> On Wed, Mar 16, 2011 at 8:54 AM, Dennis Sosnoski <dm...@sosnoski.com>
>> >> wrote:
>> >>>
>> >>> On 03/16/2011 12:59 AM, Afkham Azeez wrote:
>> >>>
>> >>> On Mon, Mar 14, 2011 at 4:01 PM, Dennis Sosnoski <dm...@sosnoski.com>
>> >>> 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
>> >>> :)
>> >>>
>> >>> I guess I'm confused - I thought you were the one saying we should
>> >>> move
>> >>> to requiring Java 6?
>> >>>
>> >>> One of the main "advances" of Java 6 is the bundling of Sun/Oracle's
>> >>> JAXB
>> >>> and JAX-WS implementations into the base distribution. But that's not
>> >>> really
>> >>> a gain for us on Axis2, since we want to use our own versions instead
>> >>> of the
>> >>> (generally outdated) ones that are present in the distribution. Aside
>> >>> from
>> >>> that, there are a few added classes (with Deque probably the most
>> >>> useful),
>> >>> and some scattered added methods. None of this is going to make any
>> >>> significant difference to the Axis2 codebase, as far as I can see.
>> >>>
>> >>> - Dennis
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Afkham Azeez
>> >> Senior Software Architect & Senior Manager; WSO2,
>> >> Inc.; http://wso2.com,
>> >>
>> >> Member; Apache Software Foundation; http://www.apache.org/
>> >> email: azeez@wso2.com cell: +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
>> >>
>> >
>> >
>> >
>> > --
>> > Afkham Azeez
>> > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>> >
>> > Member; Apache Software Foundation; http://www.apache.org/
>> > email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>
>
>
> --
> Afkham Azeez
> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: [Axis2] Isn't it time for us to move to Java 6?
Posted by Andreas Veithen <an...@gmail.com>.
I don't see any empirical evidence that would support the claim that
Axis2 is not sufficiently tested with Java 1.6. How do you come to
that conclusion?
Andreas
On Wed, Mar 16, 2011 at 08:21, Afkham Azeez <af...@gmail.com> wrote:
> If you were working for a company which required that their software run on
> JDK6 and when you ask the developers whether they have extensively tested
> the software on JDK 6, and the answer is, yes, the continuous integration
> system runs that, but we developers mostly test it with JDK5, would you be
> confident enough to provide an assurance to your management that Axis2 works
> perfectly on JDK6? Theoretically everything should work fine, but we know
> how software behaves :)
>
> On Wed, Mar 16, 2011 at 12:17 PM, Andreas Veithen
> <an...@gmail.com> wrote:
>>
>> If somebody asks that question, the correct answer is that we have
>> automated builds that check every single commit against both Java
>> versions and that our developers are using different Java versions
>> from different vendors on different platforms. I know that some
>> developers use 1.6 because it happened in the past that they committed
>> things to the trunk that broke the build on Java 1.5. These issues
>> were mostly related to the endorsed library stuff in JAX-WS and easy
>> to fix.
>>
>> Maintaining 1.5 compatibility doesn't mean that we force people to
>> stay away from Java 1.6. It also doesn't mean that developers have to
>> use Java 1.5. It only means that developers should watch the
>> notifications from Jenkins and take appropriate actions if they break
>> the build on 1.5. Obviously this may include deciding to drop support
>> for 1.5 if at some point the cost of maintaining 1.5 compatibility
>> becomes too high.
>>
>> Andreas
>>
>> On Wed, Mar 16, 2011 at 05:48, Afkham Azeez <af...@gmail.com> wrote:
>> > What I'm saying is, if somebody asks has Axis2 been thoroughly tested on
>> > JDK/JRE 6, the best answer we could give is; 'Yes, everything should
>> > work
>> > fine, but we the developers have not rigorously tested it with JDK 6,
>> > nor do
>> > we regularly build it with JDK 6. So yeah, run in on JDK 6 on your own
>> > risk"
>> >
>> > On Wed, Mar 16, 2011 at 10:14 AM, Afkham Azeez <af...@gmail.com> wrote:
>> >>
>> >> What I've been observing is the world is gradually moving away from
>> >> Java
>> >> 5, most of the people who download a JDK download JDK 6. The JRE itself
>> >> contains many improvements. Sticking to JDK5 means, Axis2 does not get
>> >> tested of Java 6 on a regular basis by the developers, so we cannot
>> >> give
>> >> 100% assurance that everything in Axis2 works fine with Java 6.
>> >>
>> >> On Wed, Mar 16, 2011 at 8:54 AM, Dennis Sosnoski <dm...@sosnoski.com>
>> >> wrote:
>> >>>
>> >>> On 03/16/2011 12:59 AM, Afkham Azeez wrote:
>> >>>
>> >>> On Mon, Mar 14, 2011 at 4:01 PM, Dennis Sosnoski <dm...@sosnoski.com>
>> >>> 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
>> >>> :)
>> >>>
>> >>> I guess I'm confused - I thought you were the one saying we should
>> >>> move
>> >>> to requiring Java 6?
>> >>>
>> >>> One of the main "advances" of Java 6 is the bundling of Sun/Oracle's
>> >>> JAXB
>> >>> and JAX-WS implementations into the base distribution. But that's not
>> >>> really
>> >>> a gain for us on Axis2, since we want to use our own versions instead
>> >>> of the
>> >>> (generally outdated) ones that are present in the distribution. Aside
>> >>> from
>> >>> that, there are a few added classes (with Deque probably the most
>> >>> useful),
>> >>> and some scattered added methods. None of this is going to make any
>> >>> significant difference to the Axis2 codebase, as far as I can see.
>> >>>
>> >>> - Dennis
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Afkham Azeez
>> >> Senior Software Architect & Senior Manager; WSO2,
>> >> Inc.; http://wso2.com,
>> >>
>> >> Member; Apache Software Foundation; http://www.apache.org/
>> >> email: azeez@wso2.com cell: +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
>> >>
>> >
>> >
>> >
>> > --
>> > Afkham Azeez
>> > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>> >
>> > Member; Apache Software Foundation; http://www.apache.org/
>> > email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>
>
>
> --
> Afkham Azeez
> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: [Axis2] Isn't it time for us to move to Java 6?
Posted by Afkham Azeez <af...@gmail.com>.
If you were working for a company which required that their software run on
JDK6 and when you ask the developers whether they have extensively tested
the software on JDK 6, and the answer is, yes, the continuous integration
system runs that, but we developers mostly test it with JDK5, would you be
confident enough to provide an assurance to your management that Axis2 works
perfectly on JDK6? Theoretically everything should work fine, but we know
how software behaves :)
On Wed, Mar 16, 2011 at 12:17 PM, Andreas Veithen <andreas.veithen@gmail.com
> wrote:
> If somebody asks that question, the correct answer is that we have
> automated builds that check every single commit against both Java
> versions and that our developers are using different Java versions
> from different vendors on different platforms. I know that some
> developers use 1.6 because it happened in the past that they committed
> things to the trunk that broke the build on Java 1.5. These issues
> were mostly related to the endorsed library stuff in JAX-WS and easy
> to fix.
>
> Maintaining 1.5 compatibility doesn't mean that we force people to
> stay away from Java 1.6. It also doesn't mean that developers have to
> use Java 1.5. It only means that developers should watch the
> notifications from Jenkins and take appropriate actions if they break
> the build on 1.5. Obviously this may include deciding to drop support
> for 1.5 if at some point the cost of maintaining 1.5 compatibility
> becomes too high.
>
> Andreas
>
> On Wed, Mar 16, 2011 at 05:48, Afkham Azeez <af...@gmail.com> wrote:
> > What I'm saying is, if somebody asks has Axis2 been thoroughly tested on
> > JDK/JRE 6, the best answer we could give is; 'Yes, everything should work
> > fine, but we the developers have not rigorously tested it with JDK 6, nor
> do
> > we regularly build it with JDK 6. So yeah, run in on JDK 6 on your own
> risk"
> >
> > On Wed, Mar 16, 2011 at 10:14 AM, Afkham Azeez <af...@gmail.com> wrote:
> >>
> >> What I've been observing is the world is gradually moving away from Java
> >> 5, most of the people who download a JDK download JDK 6. The JRE itself
> >> contains many improvements. Sticking to JDK5 means, Axis2 does not get
> >> tested of Java 6 on a regular basis by the developers, so we cannot give
> >> 100% assurance that everything in Axis2 works fine with Java 6.
> >>
> >> On Wed, Mar 16, 2011 at 8:54 AM, Dennis Sosnoski <dm...@sosnoski.com>
> wrote:
> >>>
> >>> On 03/16/2011 12:59 AM, Afkham Azeez wrote:
> >>>
> >>> On Mon, Mar 14, 2011 at 4:01 PM, Dennis Sosnoski <dm...@sosnoski.com>
> >>> 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 :)
> >>>
> >>> I guess I'm confused - I thought you were the one saying we should move
> >>> to requiring Java 6?
> >>>
> >>> One of the main "advances" of Java 6 is the bundling of Sun/Oracle's
> JAXB
> >>> and JAX-WS implementations into the base distribution. But that's not
> really
> >>> a gain for us on Axis2, since we want to use our own versions instead
> of the
> >>> (generally outdated) ones that are present in the distribution. Aside
> from
> >>> that, there are a few added classes (with Deque probably the most
> useful),
> >>> and some scattered added methods. None of this is going to make any
> >>> significant difference to the Axis2 codebase, as far as I can see.
> >>>
> >>> - Dennis
> >>>
> >>
> >>
> >>
> >> --
> >> Afkham Azeez
> >> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com
> ,
> >>
> >> Member; Apache Software Foundation; http://www.apache.org/
> >> email: azeez@wso2.com cell: +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
> >>
> >
> >
> >
> > --
> > Afkham Azeez
> > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
> >
> > Member; Apache Software Foundation; http://www.apache.org/
> > email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
--
*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: **azeez@wso2.com* <az...@wso2.com>* 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*
*
*
Re: [Axis2] Isn't it time for us to move to Java 6?
Posted by Andreas Veithen <an...@gmail.com>.
If somebody asks that question, the correct answer is that we have
automated builds that check every single commit against both Java
versions and that our developers are using different Java versions
from different vendors on different platforms. I know that some
developers use 1.6 because it happened in the past that they committed
things to the trunk that broke the build on Java 1.5. These issues
were mostly related to the endorsed library stuff in JAX-WS and easy
to fix.
Maintaining 1.5 compatibility doesn't mean that we force people to
stay away from Java 1.6. It also doesn't mean that developers have to
use Java 1.5. It only means that developers should watch the
notifications from Jenkins and take appropriate actions if they break
the build on 1.5. Obviously this may include deciding to drop support
for 1.5 if at some point the cost of maintaining 1.5 compatibility
becomes too high.
Andreas
On Wed, Mar 16, 2011 at 05:48, Afkham Azeez <af...@gmail.com> wrote:
> What I'm saying is, if somebody asks has Axis2 been thoroughly tested on
> JDK/JRE 6, the best answer we could give is; 'Yes, everything should work
> fine, but we the developers have not rigorously tested it with JDK 6, nor do
> we regularly build it with JDK 6. So yeah, run in on JDK 6 on your own risk"
>
> On Wed, Mar 16, 2011 at 10:14 AM, Afkham Azeez <af...@gmail.com> wrote:
>>
>> What I've been observing is the world is gradually moving away from Java
>> 5, most of the people who download a JDK download JDK 6. The JRE itself
>> contains many improvements. Sticking to JDK5 means, Axis2 does not get
>> tested of Java 6 on a regular basis by the developers, so we cannot give
>> 100% assurance that everything in Axis2 works fine with Java 6.
>>
>> On Wed, Mar 16, 2011 at 8:54 AM, Dennis Sosnoski <dm...@sosnoski.com> wrote:
>>>
>>> On 03/16/2011 12:59 AM, Afkham Azeez wrote:
>>>
>>> On Mon, Mar 14, 2011 at 4:01 PM, Dennis Sosnoski <dm...@sosnoski.com>
>>> 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 :)
>>>
>>> I guess I'm confused - I thought you were the one saying we should move
>>> to requiring Java 6?
>>>
>>> One of the main "advances" of Java 6 is the bundling of Sun/Oracle's JAXB
>>> and JAX-WS implementations into the base distribution. But that's not really
>>> a gain for us on Axis2, since we want to use our own versions instead of the
>>> (generally outdated) ones that are present in the distribution. Aside from
>>> that, there are a few added classes (with Deque probably the most useful),
>>> and some scattered added methods. None of this is going to make any
>>> significant difference to the Axis2 codebase, as far as I can see.
>>>
>>> - Dennis
>>>
>>
>>
>>
>> --
>> Afkham Azeez
>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>>
>> Member; Apache Software Foundation; http://www.apache.org/
>> email: azeez@wso2.com cell: +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
>>
>
>
>
> --
> Afkham Azeez
> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: [Axis2] Isn't it time for us to move to Java 6?
Posted by Afkham Azeez <af...@gmail.com>.
What I'm saying is, if somebody asks has Axis2 been thoroughly tested on
JDK/JRE 6, the best answer we could give is; 'Yes, everything should work
fine, but we the developers have not rigorously tested it with JDK 6, nor do
we regularly build it with JDK 6. So yeah, run in on JDK 6 on your own risk"
On Wed, Mar 16, 2011 at 10:14 AM, Afkham Azeez <af...@gmail.com> wrote:
> What I've been observing is the world is gradually moving away from Java 5,
> most of the people who download a JDK download JDK 6. The JRE itself
> contains many improvements. Sticking to JDK5 means, Axis2 does not get
> tested of Java 6 on a regular basis by the developers, so we cannot give
> 100% assurance that everything in Axis2 works fine with Java 6.
>
>
> On Wed, Mar 16, 2011 at 8:54 AM, Dennis Sosnoski <dm...@sosnoski.com> wrote:
>
>> On 03/16/2011 12:59 AM, Afkham Azeez wrote:
>>
>>
>>
>> On Mon, Mar 14, 2011 at 4:01 PM, Dennis Sosnoski <dm...@sosnoski.com>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 :)
>>
>>
>> I guess I'm confused - I thought you were the one saying we should move to
>> requiring Java 6?
>>
>> One of the main "advances" of Java 6 is the bundling of Sun/Oracle's JAXB
>> and JAX-WS implementations into the base distribution. But that's not really
>> a gain for us on Axis2, since we want to use our own versions instead of the
>> (generally outdated) ones that are present in the distribution. Aside from
>> that, there are a few added classes (with Deque probably the most useful),
>> and some scattered added methods. None of this is going to make any
>> significant difference to the Axis2 codebase, as far as I can see.
>>
>> - Dennis
>>
>>
>
>
> --
> *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: **azeez@wso2.com* <az...@wso2.com>* 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: **azeez@wso2.com* <az...@wso2.com>* 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*
*
*
Re: [Axis2] Isn't it time for us to move to Java 6?
Posted by Afkham Azeez <af...@gmail.com>.
What I've been observing is the world is gradually moving away from Java 5,
most of the people who download a JDK download JDK 6. The JRE itself
contains many improvements. Sticking to JDK5 means, Axis2 does not get
tested of Java 6 on a regular basis by the developers, so we cannot give
100% assurance that everything in Axis2 works fine with Java 6.
On Wed, Mar 16, 2011 at 8:54 AM, Dennis Sosnoski <dm...@sosnoski.com> wrote:
> On 03/16/2011 12:59 AM, Afkham Azeez wrote:
>
>
>
> On Mon, Mar 14, 2011 at 4:01 PM, Dennis Sosnoski <dm...@sosnoski.com> 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 :)
>
>
> I guess I'm confused - I thought you were the one saying we should move to
> requiring Java 6?
>
> One of the main "advances" of Java 6 is the bundling of Sun/Oracle's JAXB
> and JAX-WS implementations into the base distribution. But that's not really
> a gain for us on Axis2, since we want to use our own versions instead of the
> (generally outdated) ones that are present in the distribution. Aside from
> that, there are a few added classes (with Deque probably the most useful),
> and some scattered added methods. None of this is going to make any
> significant difference to the Axis2 codebase, as far as I can see.
>
> - Dennis
>
>
--
*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: **azeez@wso2.com* <az...@wso2.com>* 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*
*
*
Re: [Axis2] Isn't it time for us to move to Java 6?
Posted by Dennis Sosnoski <dm...@sosnoski.com>.
On 03/16/2011 12:59 AM, Afkham Azeez wrote:
>
>
> On Mon, Mar 14, 2011 at 4:01 PM, Dennis Sosnoski <dms@sosnoski.com
> <ma...@sosnoski.com>> 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 :)
I guess I'm confused - I thought you were the one saying we should move
to requiring Java 6?
One of the main "advances" of Java 6 is the bundling of Sun/Oracle's
JAXB and JAX-WS implementations into the base distribution. But that's
not really a gain for us on Axis2, since we want to use our own versions
instead of the (generally outdated) ones that are present in the
distribution. Aside from that, there are a few added classes (with Deque
probably the most useful), and some scattered added methods. None of
this is going to make any significant difference to the Axis2 codebase,
as far as I can see.
- Dennis
Re: [Axis2] Isn't it time for us to move to Java 6?
Posted by Afkham Azeez <af...@gmail.com>.
On Mon, Mar 14, 2011 at 4:01 PM, Dennis Sosnoski <dm...@sosnoski.com> 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 <dm...@sosnoski.com> 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/dev@cxf.apache.org/msg04370.html
>>
>> I think most of the arguments also apply to Axis2.
>>
>> Andreas
>>
>> On Sun, Mar 13, 2011 at 13:49, Afkham Azeez <af...@gmail.com> <af...@gmail.com> 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 <an...@gmail.com> <an...@gmail.com>
>> 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 <af...@gmail.com> <af...@gmail.com> 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: azeez@wso2.com 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: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>> --
>> Afkham Azeez
>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>>
>> Member; Apache Software Foundation; http://www.apache.org/
>> email: azeez@wso2.com 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: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
>>
>
>
> --
> *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: **azeez@wso2.com* <az...@wso2.com>* 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: **azeez@wso2.com* <az...@wso2.com>* 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*
*
*
Re: [Axis2] Isn't it time for us to move to Java 6?
Posted by Dennis Sosnoski <dm...@sosnoski.com>.
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?
- 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 <dms@sosnoski.com
> <ma...@sosnoski.com>> 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/dev@cxf.apache.org/msg04370.html
>>
>> I think most of the arguments also apply to Axis2.
>>
>> Andreas
>>
>> On Sun, Mar 13, 2011 at 13:49, Afkham Azeez <af...@gmail.com> <ma...@gmail.com> 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 <an...@gmail.com> <ma...@gmail.com>
>>> 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 <af...@gmail.com> <ma...@gmail.com> 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: azeez@wso2.com <ma...@wso2.com> cell: +94 77 3320919 <tel:%2B94%2077%203320919>
>>>>> 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: java-dev-unsubscribe@axis.apache.org <ma...@axis.apache.org>
>>>> For additional commands, e-mail: java-dev-help@axis.apache.org <ma...@axis.apache.org>
>>>>
>>>>
>>> --
>>> Afkham Azeez
>>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>>>
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> email: azeez@wso2.com <ma...@wso2.com> cell: +94 77 3320919 <tel:%2B94%2077%203320919>
>>> 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: java-dev-unsubscribe@axis.apache.org <ma...@axis.apache.org>
>> For additional commands, e-mail: java-dev-help@axis.apache.org <ma...@axis.apache.org>
>>
>>
>>
>
>
>
>
> --
> *Afkham Azeez*
> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
> /
> /
> /Member; Apache Software Foundation; //http://www.apache.org///
> email: //azeez@wso2.com/ <ma...@wso2.com>/ cell: +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/
> /
> /
>
Re: [Axis2] Isn't it time for us to move to Java 6?
Posted by Andreas Veithen <an...@gmail.com>.
On Mon, Mar 14, 2011 at 10:17, Afkham Azeez <af...@gmail.com> 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.
Can you be a bit more specific and give some examples of the added
value for Axis2 to move to JDK 6 at this point?
> On Mon, Mar 14, 2011 at 2:14 PM, Dennis Sosnoski <dm...@sosnoski.com> 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
>> Axis2/CXF/Metro SOA and Web Services Training
>> Web Services Jump-Start
>>
>> 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/dev@cxf.apache.org/msg04370.html
>>
>> I think most of the arguments also apply to Axis2.
>>
>> Andreas
>>
>> On Sun, Mar 13, 2011 at 13:49, Afkham Azeez <af...@gmail.com> 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
>> <an...@gmail.com>
>> 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 <af...@gmail.com> 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: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
>>
>> --
>> Afkham Azeez
>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>>
>> Member; Apache Software Foundation; http://www.apache.org/
>> email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
>>
>
>
> --
> Afkham Azeez
> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: [Axis2] Isn't it time for us to move to Java 6?
Posted by Afkham Azeez <af...@gmail.com>.
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 <dm...@sosnoski.com> 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/dev@cxf.apache.org/msg04370.html
>
> I think most of the arguments also apply to Axis2.
>
> Andreas
>
> On Sun, Mar 13, 2011 at 13:49, Afkham Azeez <af...@gmail.com> <af...@gmail.com> 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 <an...@gmail.com> <an...@gmail.com>
> 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 <af...@gmail.com> <af...@gmail.com> 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: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
> --
> Afkham Azeez
> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
>
--
*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: **azeez@wso2.com* <az...@wso2.com>* 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*
*
*
Re: [Axis2] Isn't it time for us to move to Java 6?
Posted by Dennis Sosnoski <dm...@sosnoski.com>.
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/dev@cxf.apache.org/msg04370.html
>
> I think most of the arguments also apply to Axis2.
>
> Andreas
>
> On Sun, Mar 13, 2011 at 13:49, Afkham Azeez <af...@gmail.com> 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 <an...@gmail.com>
>> 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 <af...@gmail.com> 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: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>>
>>
>>
>> --
>> Afkham Azeez
>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>>
>> Member; Apache Software Foundation; http://www.apache.org/
>> email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
>
Re: [Axis2] Isn't it time for us to move to Java 6?
Posted by Afkham Azeez <af...@gmail.com>.
Nevertheless, the world seems to be moving away from JDK 5.
On Sun, Mar 13, 2011 at 10:20 PM, Andreas Veithen <andreas.veithen@gmail.com
> 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/dev@cxf.apache.org/msg04370.html
>
> I think most of the arguments also apply to Axis2.
>
> Andreas
>
> On Sun, Mar 13, 2011 at 13:49, Afkham Azeez <af...@gmail.com> 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 <
> andreas.veithen@gmail.com>
> > 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 <af...@gmail.com> 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: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
> >> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>
> >
> >
> >
> > --
> > Afkham Azeez
> > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
> >
> > Member; Apache Software Foundation; http://www.apache.org/
> > email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
--
*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: **azeez@wso2.com* <az...@wso2.com>* 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*
*
*
Re: [Axis2] Isn't it time for us to move to Java 6?
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Andreas IMO Oracle's willingness to provide commercial support for JDK 1.5
is not a reason for us to keep supporting JDK 1.5. If our primary user
community (who use our open source code) cannot use it on the publicly
available Java platform then we should move away.
Sanjiva.
On Sun, Mar 13, 2011 at 10:20 PM, Andreas Veithen <andreas.veithen@gmail.com
> 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/dev@cxf.apache.org/msg04370.html
>
> I think most of the arguments also apply to Axis2.
>
> Andreas
>
> On Sun, Mar 13, 2011 at 13:49, Afkham Azeez <af...@gmail.com> 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 <
> andreas.veithen@gmail.com>
> > 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 <af...@gmail.com> 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: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
> >> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>
> >
> >
> >
> > --
> > Afkham Azeez
> > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
> >
> > Member; Apache Software Foundation; http://www.apache.org/
> > email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
--
Sanjiva Weerawarana, Ph.D.
Founder, Director & Chief Scientist; Lanka Software Foundation;
http://www.opensource.lk/
Founder, Chairman & CEO; WSO2; http://wso2.com/
Founder & Director; Thinkcube Systems; http://www.thinkcube.com/
Member; Apache Software Foundation; http://www.apache.org/
Member; Sahana Software Foundation; http://www.sahanafoundation.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
Blog: http://sanjiva.weerawarana.org/
Re: [Axis2] Isn't it time for us to move to Java 6?
Posted by Andreas Veithen <an...@gmail.com>.
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/dev@cxf.apache.org/msg04370.html
I think most of the arguments also apply to Axis2.
Andreas
On Sun, Mar 13, 2011 at 13:49, Afkham Azeez <af...@gmail.com> 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 <an...@gmail.com>
> 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 <af...@gmail.com> 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: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>
>
>
> --
> Afkham Azeez
> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: [Axis2] Isn't it time for us to move to Java 6?
Posted by Afkham Azeez <af...@gmail.com>.
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
<an...@gmail.com>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 <af...@gmail.com> 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: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
--
*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: **azeez@wso2.com* <az...@wso2.com>* 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*
*
*
Re: [Axis2] Isn't it time for us to move to Java 6?
Posted by Andreas Veithen <an...@gmail.com>.
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 <af...@gmail.com> 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: azeez@wso2.com cell: +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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org