Well, a couple things: if Axis 1.1 is going to stabilize, we need to
absolutely freeze development on any new features (e.g. notice I haven't
done any additional work on the async stuff in a while :-) ...) and work
strictly on bug fixes AND we need to set a target release date. My vote
would be that by the end of next week we cut an Axis 1.1 Beta 2 and target
Axis 1.1 final for the end of Feb and focus on *nothing* but bug fixes
between now and then.
Can we *please* start setting and voting on milestone goals that include a
detailed list of the new features and bug fixes we plan for each upcoming
point release?
Regarding the servlet.jar, it's the EngineConfigurationFactoryFinder class
that's looking for the default EngineConfigurationFactory. It apparently
tries to init DefaultEngineConfigurationFactoryServlet which requires the
ServletContext class to be present. Richard Sitze did some work to
address this but it appears to still be a problem under JDK 1.4.
- James Snell
IBM Emerging Technologies
[EMAIL PROTECTED]
(559) 587-1233 (office)
(700) 544-9035 (t/l)
Programming Web Services With SOAP
O'Reilly & Associates, ISBN 0596000952
Have I not commanded you? Be strong and courageous.
Do not be terrified, do not be discouraged, for the Lord your
God will be with you whereever you go. - Joshua 1:9
"Steve Loughran" <[EMAIL PROTECTED]>
01/31/2003 05:02 PM
Please respond to axis-dev
To
<[EMAIL PROTECTED]>
cc
bcc
Subject
Re: Axis 1.1?
----- Original Message -----
From: "James M Snell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 31, 2003 15:13
Subject: Axis 1.1?
> Btw, when are we looking at releasing Axis 1.1?
good q: ask the release manager.
I think the long beta release has actually been pretty beneficial; takeup
of
1.1beta has been high and its given us chance to stabilise something and
get
some extra fixes in there. Also some gotchas are still surfacing, such as
the servlets.jar need.
On the subject of servlets.jar, what bit of client side code is it that
needs it?
