My comprehension (not again.... Its not flamey this time) is this:
Ted can release today under Beta 5 beta as is (with the known failed test) with all the work he did. Plus for this side is... who knows when is the next time a release will come, and no release for Java One?, that was the motivation here. So it's a step sideways to go forward. +1 means release Today, that is how I read it. It's just a name.
Else... someone else (who has tech. skills/experience of Ted) has to step forward, at another time to fix and build and release. So if you look at it as beta vs RC 2... it seems RC2! But when, a week? A month? What about the work done last few days? So a - 1 means.... wait.
If you say, hey, lets release something! that works and passes most tests in how it's used, and lets move towards final then ... beta 5.
+0 for B5.
.V
James Turner wrote:
Frankly, since these seem to be problems in the tests and demo
applications, rather than in the base code, I'd be -1 on this. Going to
a beta 5 seems to me to be a unnecessary step unless the problem is in
the actual core libraries themselves.
James
-----Original Message-----
From: Ted Husted [mailto:[EMAIL PROTECTED] Sent: Sunday, June 08, 2003 6:14 PM
To: Struts Developers List
Subject: [VOTE] Convert RC2 to Beta 5
In final testing of RC2, some compatibility issues have been found between Tomcat 3.3.1 and the struts-exercise-taglib application as well as the tiles-documentation application.
Martin Cooper has been looking into the problems and has found that for the struts-exercise-taglibs cookie test, it is the
<jsp:getProperty name="sess" property="name"/>
expression that is failing.
The <jsp:getProperty> tags earlier on the page succeeded. The only difference seems to be that the earlier ones all have setters as well as getters in the Tomcat CookieFacade class, whereas there is only a getter for 'name'. So this actually looks like some kind of JSP/reflection bug, not related to Struts. (The <bean:cookie> tag must have worked, because we know the <jsp:getProperty> tag is trying to access a cookie!)
Also, the (rather complex) comparison test is killing the JVM when run under TC3.
In the Tiles application, servlet exceptions are being noted. One example is the extendedDefinitionTag page, but there may be others.
Unless fixes to these problems are immediately forthcoming, I propose that we document the issues and release Stuts 1.1 beta 5.
By getting this milestone out to the community, we would have a better chance of resolving the remaining issues so that we can go to Struts 1.1. final as soon as possible
This proposal has my +1.
-Ted.
--------------------------------------------------------------------- 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]
