On Mon, 12 Aug 2002 [EMAIL PROTECTED] wrote:
> Date: Mon, 12 Aug 2002 09:05:07 -0400
> From: [EMAIL PROTECTED]
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: RE: The state of 1.1 Beta 2
>
>
> For what I am worth, I would agree with fixing the blank-webapp... I
> encountered this early on and it was very frusterating when I started
> learning struts (i assumed the blank-app was configured correctly).
>
Nobody is arguing that doing this would be a waste of time. What's most
important is for someone to take the time to *do* it. Patches are
welcome!
Given that this is a beta release, however, I'm not convinced that this
issue should be used to hold up all the people who would be willing to use
a beta release for testing (but not a nightly build) to get us more
feedback on bugs that need to be fixed.
Craig
>
> -----Original Message-----
> From: jeremy [mailto:[EMAIL PROTECTED]]
> Sent: Monday, August 12, 2002 3:17 AM
> To: struts-dev
> Subject: Re: The state of 1.1 Beta 2
>
>
> My 2-cents......
>
> Many people who will start using struts will use the latest
> beta release.....and start with the struts-blank webapp.
> Havning this not working is going to discourage a lot of
> first timer's away from the project, as well as second
> timer's waiting for a more stable release. I would say that
> some of the problems listed below definitely warrent holding
> up the beta 2 release.
>
> toodles....
>
>
> ---- Original message ----
> >Date: Sun, 11 Aug 2002 22:08:46 -0700
> >From: "Martin Cooper" <[EMAIL PROTECTED]>
> >Subject: The state of 1.1 Beta 2
> >To: "'[EMAIL PROTECTED]'" <struts-
> [EMAIL PROTECTED]>
> >
> >The CVS tree was tagged on Saturday night, per the release
> plan, and I have
> >a build from that code base ready to be uploaded to the web
> site. (The CVS
> >tree for corresponding Commons and Commons Sandbox
> components was also
> >tagged.)
> >
> >However, in my testing, I uncovered some issues that I
> wanted to mention
> >before making the build available, in case any of the
> committers think we
> >should hold Beta 2 until they are resolved. So, here's what
> I found.
> >
> >Unit Tests
> >==========
> >
> >The JUnit tests, and tests against Tomcat 4.0.4, passed.
> However, tests
> >against Tomcat 3.2.4 failed. The reason appears to be a
> class loader bug in
> >that version of Tomcat. Note that the release plan does not
> call for working
> >with Tomcat 3.2.4, although we have unit tests for that
> environment.
> >
> >Sample Webapps
> >==============
> >
> >I tested with the following containers:
> >
> >* Tomcat versions 3.2.4, 3.3.1, 3.3.2-dev, 4.0.4
> >* Resin versions 1.2.10, 2.1.2, 2.1.4
> >
> >Because of the apparent class loader bug noted above, I did
> little testing
> >with Tomcat 3.2.4 beyond confirming that the example webapp
> fails in the
> >same way as the unit tests.
> >
> >In addition, test results for Tomcat 3.3.1 and 3.3.2-dev
> appeared identical,
> >as did the results from Resin 2.1.2 and 2.1.4.
> >
> >Here are the issues I found.
> >
> >All containers
> >--------------
> >
> >* The struts-blank webapp does not work in any of the tested
> containers. The
> >issue is related to message resources not being found.
> Apparently, this
> >webapp has two separate resource files, although only one is
> configured in
> >the Struts config file. This just needs someone to expend a
> little TLC to
> >put it back into working order.
> >
> >* The tiles-documentation webapp has several broken links in
> the main
> >navigation bar. The includes are failing because they are
> referencing
> >non-existent files. (Only Resin provided the information
> about which files
> >it was looking for and failing to find.) The four links I
> found that were
> >broken were to the tutorial, installation, user guide and
> Javadocs.
> >
> >Tomcat 3.3.1 and 3.3.2-dev
> >--------------------------
> >
> >* The <html:cookie> test throws an exception because a
> method being accessed
> >is not public. Given that all other containers pass this
> test, I suspect
> >that this is a bug in these versions of Tomcat, but I have
> not investigated
> >this further.
> >
> >* The Comparison Tags test fails rather dramatically, with a
> JVM error
> >shutting down the container, and complaining about a
> problematic thread.
> >This happened both with JDK 1.4.0_01 and with JDK 1.3.1_01.
> I don't know
> >whether this is a JVM bug exposed only by Tomcat 3.3.x, or a
> Tomcat 3.3.x
> >bug, or something else. It seems unlikely to be a Struts bug.
> >
> >All versions of Resin
> >---------------------
> >
> >* The <html:cookie> test shows "null" in the Correct Value
> column, while the
> >Test Result column shows a missing table cell. In contrast,
> all versions of
> >Tomcat show a missing table cell in the Correct Value
> column. I have not
> >investigated this further.
> >
> >Resin 2.1.2 and 2.1.4
> >---------------------
> >
> >* The struts-example webapp seems to keep losing the session
> id, so that any
> >time you try to edit your registration data, you are taken
> to the logon page
> >again, even if you just finished logging on. I suspect that
> this is a Resin
> >bug, given some of the recent comments on the Resin mailing
> list, but it's
> >possible that this is a tag handler reuse issue with the
> example webapp. I
> >have not investigated this further.
> >
> >Conclusion
> >==========
> >
> >Although there are some nasty problems described above, many
> of them appear
> >to be container specific. Those that are not, such as the
> bugs in
> >struts-blank and tiles-documentation, are not, in my
> opinion, sufficiently
> >severe to warrant holding up a Beta 2 release, although they
> certainly need
> >to be fixed before a 1.1 Final release.
> >
> >My recommendation, therefore, is to proceed with the Beta 2
> release, based
> >on the current tagged code base, and to resolve the Struts
> related issues
> >described above shortly thereafter.
> >
> >Comments?
> >
> >--
> >Martin Cooper
> >
> >
> >--
> >To unsubscribe, e-mail: <mailto:struts-dev-
> [EMAIL PROTECTED]>
> >For additional commands, e-mail: <mailto:struts-dev-
> [EMAIL PROTECTED]>
> >
>
>
> ===================================
> Experience is something you don't
> get until just after you need it.
> ===================================
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
