Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 39389 invoked from network); 27 Feb 2008 14:09:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Feb 2008 14:09:45 -0000 Received: (qmail 1856 invoked by uid 500); 27 Feb 2008 14:09:38 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 1794 invoked by uid 500); 27 Feb 2008 14:09:38 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 1783 invoked by uid 99); 27 Feb 2008 14:09:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2008 06:09:38 -0800 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of barrettj@us.ibm.com designates 32.97.110.150 as permitted sender) Received: from [32.97.110.150] (HELO e32.co.us.ibm.com) (32.97.110.150) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2008 14:09:01 +0000 Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e32.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id m1RE8enh005271 for ; Wed, 27 Feb 2008 09:08:40 -0500 Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v8.7) with ESMTP id m1RE993k195124 for ; Wed, 27 Feb 2008 07:09:10 -0700 Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m1RE9903022622 for ; Wed, 27 Feb 2008 07:09:09 -0700 Received: from d03nm119.boulder.ibm.com (d03nm119.boulder.ibm.com [9.17.195.145]) by d03av02.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id m1RE99EH022605 for ; Wed, 27 Feb 2008 07:09:09 -0700 In-Reply-To: To: axis-dev@ws.apache.org MIME-Version: 1.0 Subject: Re: [Axis2] Moving Axis2 code base into JDK 1.5 X-Mailer: Lotus Notes Release 7.0 HF277 June 21, 2006 From: Jeff Barrett Message-ID: Date: Wed, 27 Feb 2008 08:09:08 -0600 X-MIMETrack: Serialize by Router on D03NM119/03/M/IBM(Release 7.0.2FP2HF300 | September 14, 2007) at 02/27/2008 07:09:09, Serialize complete at 02/27/2008 07:09:09 Content-Type: text/plain; charset="US-ASCII" X-Virus-Checked: Checked by ClamAV on apache.org Hi Folks, If we choose to stay on 1.4, remember that JAXWS requires Java 1.5 (due to the spec-required use of generics). I think there are a couple of modules that require Java 1.5 to build. Also note that in order to run the JAXWS 2.1 TCK, that will also require Java 1.5 since the TCK will test the use of generics. So, staying on Java 1.4 and supporting JAXWS probably means something like: - We have to be building with Java 1.5 to get JAXWS built - We state that Axis2 can be run on 1.4 without JAXWS (as was true in the past) - To use Axis2 with JAXWS, you have to use Java 1.5 Thanks, Jeff IBM Software Group - WebSphere Web Services Development Phone: 512-838-4587 or Tie Line 678-4587 Internet e-mail and Sametime ID: barrettj@us.ibm.com "Jeremy Hughes" Sent by: jpjhughes@gmail.com 02/27/2008 05:15 AM Please respond to axis-dev@ws.apache.org To axis-user@ws.apache.org cc "axis-dev@ws.apache.org" Subject Re: [Axis2] Moving Axis2 code base into JDK 1.5 +1 to moving to Java 5. I think maintenance releases could be key in keeping those users tied to Java 1.4, interested in Axis2 until they're ready to move up to Java 5 themselves. Jeremy On 27/02/2008, Paul Fremantle wrote: > Yes I guess that makes sense. > However, its most likely that we would roll up whatever is in the trunk. > > I guess that there might be also end up being a 1.4.1 maintenance > release as well. > > > Paul > > > On Wed, Feb 27, 2008 at 10:36 AM, Michele Mazzucco > wrote: > > Paul, > > > > if so, I think release 1.4 should focus on fixing as much bugs as > > possible, not on adding new features. > > > > Michele > > > > > > > > On 27 Feb 2008, at 09:59, Paul Fremantle wrote: > > > > > My concern is that I think there has been a lot of work done since the > > > last release and the JDK1.4 users will never get that benefit. > > > > > > So - how about this for a plan. > > > > > > Release 1.4 asap based on JDK 1.4. > > > Then do a 1.5 release *very soon after* based on JDK1.5. > > > > > > That way even the names match :) > > > > > > Axis2 1.4 can be the last major release targeted at JDK1.4. > > > > > > As for 1.5, I think in fact it will need two releases - once we start > > > targeting 1.5 we probably need to do some 1.5 specific stuff like > > > generating code that takes advantage of generics. > > > > > > Paul > > > > > > On Wed, Feb 27, 2008 at 6:28 AM, Dennis Sosnoski > > > wrote: > > >> From my experiences working with companies moving to Axis2 I'd say > > >> about half are still using JDK 1.4. If they can't count on that > > >> support > > >> being maintained I think they're likely to reconsider adopting > > >> Axis2. > > >> Just having an archived 1.3 version of Axis2 won't be enough to > > >> convince > > >> them, unless they're already committed to moving to JDK 1.5 anyway. > > >> > > >> It seems like bad timing to give up one of the major advantages > > >> of Axis2 > > >> over the Glassfish code and such. So -0 from me. > > >> > > >> - Dennis > > >> > > >> -- > > >> Dennis M. Sosnoski > > >> SOA and Web Services in Java > > >> Axis2 Training and Consulting > > >> http://www.sosnoski.com - http://www.sosnoski.co.nz > > >> Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 > > >> > > >> > > >> > > >> > > >> > > >> Deepal Jayasinghe wrote: > > >>> Hi all , > > >>> > > >>> As you might remember few months back Glen asked the list about > > >>> moving > > >>> to JDK 1.5 and I think we got very positive feedback. So I > > >>> thought of > > >>> asking again and change the code to work with JDK 1.5 . The main > > >>> reason behind sending this mail is due the dependency we have for > > >>> annogen. As I can see that project is dead one and there is no > > >>> development happening so I do not think it is a good idea to > > >>> depend on > > >>> such a project. In the meantime we have few issues with annogen as > > >>> well ,first inner class problem (I have locally fixed that both in > > >>> Axis2 and Annogen will commit soon) , second is the final class > > >>> problem. I request a release from annogen after the changes that > > >>> Dims > > >>> did , but we did not get any reply so far. > > >>> > > >>> We all know that we get better annotation support from JDK 1.5 so if > > >>> we move to JDK 1.5 we can get rid of the annogen dependency and > > >>> we can > > >>> just use JDK for annotation processing. Other problem is generic > > >>> support , if we move to JDK 1.5 we can have generic support in our > > >>> POJOs. In addition to POJO we can get better concurrent support in > > >>> JDK 1.5 as well. > > >>> > > >>> So if we move to JDK 1.5 we can get better support , and I do not > > >>> think any advantage of staying in 1.4 . If some user want to use > > >>> Axis2 > > >>> in JDK 1.4 they can happily use Axis2 1.3 , which is very stable > > >>> version and working fine in 1.4 and 1.5. > > >>> > > >>> If any user or developers have any concern on moving to JDK 1.5 > > >>> please > > >>> come forward and reply to this mail that will be very helpful for > > >>> all > > >>> of us. > > >>> > > >>> Here is my +1 for moving to JDK 1.5 to and release Axis2 1.4 in > > >>> JDK 1.5 > > >>> > > >>> Thank you, > > >>> Deepal > > >>> > > >>> > > >>> -------------------------------------------------------------------- > > >>> - > > >>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > > >>> For additional commands, e-mail: axis-user-help@ws.apache.org > > >>> > > >> > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > > >> For additional commands, e-mail: axis-user-help@ws.apache.org > > >> > > >> > > > > > > > > > > > > -- > > > Paul Fremantle > > > Co-Founder and VP of Technical Sales, WSO2 > > > OASIS WS-RX TC Co-chair > > > > > > blog: http://pzf.fremantle.org > > > paul@wso2.com > > > > > > "Oxygenating the Web Service Platform", www.wso2.com > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > > > For additional commands, e-mail: axis-user-help@ws.apache.org > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > > For additional commands, e-mail: axis-user-help@ws.apache.org > > > > > > > > -- > Paul Fremantle > Co-Founder and VP of Technical Sales, WSO2 > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > paul@wso2.com > > "Oxygenating the Web Service Platform", www.wso2.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > For additional commands, e-mail: axis-user-help@ws.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-dev-help@ws.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-dev-help@ws.apache.org