To add to your last point.

This is one aspect where Test Driven Development really champions.  If
you run your test suite against your product with any stable release,
then validating stability should be as simple as re-running your tests
after upgrading.

The more I work with Cactus, the more I love it, and I'm sure once I
dive into StrutsTestCase, it will become my new best friend as well.


--
James Mitchell
Software Engineer/Struts Evangelist
http://www.open-tools.org/

"The man who does not read good books has no advantage over the man who
cannot read them."
        - Mark Twain (1835-1910)







> -----Original Message-----
> From: Robert Leland [mailto:[EMAIL PROTECTED]] 
> Sent: Wednesday, February 19, 2003 11:24 AM
> To: Struts Users Mailing List
> Subject: Re: How stable is struts 1.1 beta 3
> 
> 
> Jagannayakam wrote:
> > Hi ,
> > 
> > We already developed a J2EE product . Now we think of 
> implementing the
> > struts framework for better navigation , exception framework .
> > 
> > Any sugesstions on - how stable is this release of struts 
> 1.1 beta 3 .
> > Are there any major known issues in this ?
> 
> 1) Search Buzilla
> http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=NEW&b
ug_status=ASSIGNED&bug_status=REOPENED&chfieldto=Now&&product=Struts&ver
sion=1.1+Beta+1&version=1.1+Beta+2&version=1.1+Beta+3&version=Nightly+Bu
ild&cmdtype=doit

2)
A general note on stability, we have been using struts in released
products since 1.0 beta 2. We have applications out in the field using
struts 1.1b1, and 1.1b2. Generally the bugs we hit are in the lesser
used features such as:  --this is fictitious --, problems with modules 
used in conjunction with nested tags accessing multiple resource files.

3) With that said
Test your application, especially at the boundry conditions. With the 
version of jars you will deploy with, and on a system as close to the
deployed one as possable.

-Rob


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to