+1 on Beta 2 soon (although my company isn't shutting down next week :). +1 also on reviewing the tags. I fixed one or two of these a while ago - they showed up after I started using Resin 2.x - but there are likely more that I didn't stumble across. A systematic review would be good.
Related to the tag issue, I had the thought that perhaps we should remove (almost) all of the release() implementations in the Struts tags. I think many people are confused about when release() is (supposed to be) called, and the implementations we have foster the belief that it will be called to reset property values between uses of a tag instance. Or would this be too drastic a change for now? -- Martin Cooper > -----Original Message----- > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, June 26, 2002 11:05 AM > To: [EMAIL PROTECTED] > Subject: Planning for 1.1 beta 2 > > > I'd like to continue swatting the remaining bugs in 1.1, and > improve the > existing documentation, with a goal to release a beta 2 of > Strust 1.1 in > the near future (ideally by July 8 or so). Part of my > motivation for the > timing is that Sun is shutting down next week, so I will have > some quality > time hours available when I'm actually awake :-). > > Are the other committers interested in working towards such a goal? > > One thing I'd like to add to the TODO list is a review of all > our custom > tag implementations versus the JSP spec requirements -- > particularly in > the area of tag pooling and when the bodyContent can be accessed. The > recent work on Jasper2 (in Tomcat 4.1.x), which will support > tag pooling, > has indicated we probably have some tags that don't > completely conform to > the contracts -- and we need to fix that before any final release. > > Craig > > > > -- > 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]>
