axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjiva Weerawarana" <sanj...@opensource.lk>
Subject Re: Axis version
Date Wed, 25 Aug 2004 01:11:13 GMT
If I understand Arkady properly that won't help him ... he needs
it to be 1.2.

Dims, can we identify a specific to-do list for the 1.2 release
in terms of perf objectives and anything else? Let's post that
here and then I'll also try to get some help with getting it
completed. Let's get this puppy out!

Sanjiva.

----- Original Message ----- 
From: "Aleksander Slominski" <aslom@cs.indiana.edu>
To: <axis-dev@ws.apache.org>
Sent: Wednesday, August 25, 2004 4:38 AM
Subject: Re: Axis version


> Dims,
>
> i see your point.
>
> why not call it RC1 and keep releasing candidate RCx versions until
> performance problems are solved?
>
> however to do good performance analysis and tuning you need to have some
> well defined version otherwise it is like trying to shoot moving target
> and hard to see progress ...
>
> thanks,
>
> alek
>
> Davanum Srinivas wrote:
>
> >Guess what all the soap engine vendors are going to do if we do that?
> >Every single vendor already has voluminous whitepapers and ppt's
> >comparing their thingy to axis releases and use that to create FUD in
> >the market. users can still use the named releases...right?
> >
> >-- dims
> >
> >On Mon, 23 Aug 2004 21:47:46 -0500, Aleksander Slominski
> ><aslom@cs.indiana.edu> wrote:
> >
> >
> >>Dims,
> >>
> >>if none of performance problems are showstoppers (are there any?) then
> >>why not release what is currently in CVS (after freeze period and
> >>release testing) and then do performance tuning with subsequent 1.2.x
> >>releases?
> >>
> >>thanks,
> >>
> >>alek
> >>
> >>
> >>
> >>Davanum Srinivas wrote:
> >>
> >>
> >>
> >>>There are some performance issues that need to be found and fixed
> >>>before we can declare 1.2 as final. It may take a month or two
> >>>(hopefully). Of course, we can do it sooner if we get some good
> >>>patches. See
http://marc.theaimsgroup.com/?l=axis-dev&m=109271477419756&w=2
> >>>for a list of suggestions from Nishant. I wish we could get a few
> >>>patches from Nishant :) :)
> >>>
> >>>-- dims
> >>>
> >>>On Mon, 23 Aug 2004 10:28:53 +0300, Arkady Kasianski
<arikka@amdocs.com> wrote:
> >>>
> >>>
> >>>
> >>>
> >>>>1.1 was released june 2003. When 1.2 will be released!
> >>>>
> >>>>Davanum, Could you answer please ?
> >>>>
> >>>>Lael Beta expels our customers....
> >>>>
> >>>>-AK
> >>>>
> >>>>-----Original Message-----
> >>>>From: Will Sargent [mailto:will_sargent@yahoo.com]
> >>>>Sent: Sunday, August 22, 2004 8:55 PM
> >>>>To: axis-user@ws.apache.org
> >>>>Subject: Re: Axis version
> >>>>
> >>>>Nelson Minar wrote:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>>We are using Axis 1.2 beta 2 in our big Web services project.
Our
> >>>>>>product management insist to use GA 1.1 release, since using
beta
> >>>>>>product in the production environment is unacceptable.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>This is a bad decision - 1.2 is much, much better than 1.1. If I
had
> >>>>>recalcitrant PMs, I'd just tell them that 1.1 was lower quality than
> >>>>>the current 1.2beta and that it'd be too hard to port your code back
> >>>>>to 1.1 anyway.
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>But this doesn't say anything about 1.2.  Is 1.2 "good enough" quality
> >>>>to use in a production environment?  Especially when it has the beta
> >>>>label on it?
> >>>>
> >>>>Quite frankly, I've given up on using Axis altogether, and I'm using
> >>>>SAAJ.  It's way lower-level, but it's well documented and stable, and
I
> >>>>can build the features I need myself in much less time than it would
> >>>>take me to work around the bugs in Axis and figure out what it's
doing.
> >>>>
> >>>>Will.
> >>>>
> >>>>The information contained in this message is proprietary of Amdocs,
> >>>>protected from disclosure, and may be privileged.
> >>>>The information is intended to be conveyed only to the designated
recipient(s)
> >>>>of the message. If the reader of this message is not the intended
recipient,
> >>>>you are hereby notified that any dissemination, use, distribution or
copying of
> >>>>this communication is strictly prohibited and may be unlawful.
> >>>>If you have received this communication in error, please notify us
immediately
> >>>>by replying to the message and deleting it from your computer.
> >>>>Thank you.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>-- 
> >>The best way to predict the future is to invent it - Alan Kay
> >>
> >>
> >>
> >>
> >
> >
> >
> >
>
>
> -- 
> The best way to predict the future is to invent it - Alan Kay
>
>


Mime
View raw message