On 8/8/05, Ted Husted <[EMAIL PROTECTED]> wrote: > Note that the Clssic 1.3.0 release plan wiki page has been renamed: > > * http://wiki.apache.org/struts/StrutsClassicRelease130 > > Some issues have been pushed forward to a 1.3.1 plan. > > * http://wiki.apache.org/struts/StrutsClassicRelease131 > > Here's a roundup of the remaining issues with issues on the 1.3.0 short list. > > ---- > > * [upload] org.apache.struts.upload.MultipartRequestWrapper doesn't > implement servlet 2.4 api fully > * http://issues.apache.org/bugzilla/show_bug.cgi?id=33132 > > > The reason for attaching the 1.3 changes for review, > > rather than committing them directly is that I > > understand Martin has some changes underway for file > > uploading and these changes either may not be required or may be > > inappropriate. > > Any objections to this patch?
I haven't looked at the patch itself, but I guess I'm OK with going ahead on this. The upload changes I want to make are dependent on FileUpload 1.1, which in turn is dependent on IO 1.1, which isn't in danger of happening any time soon, unfortunately, based on the number of nudges so far. So I'd say upload refactoring isn't going to happen until Struts 1.4.x. ;-( > ---- > > * use charsets given by browser for form field encodings > * http://issues.apache.org/bugzilla/show_bug.cgi?id=34445 > > Unless File Upload 1.1 is imminent, we could leave this for Classic 1.3.1 Let's leave it and see what happens in Commons-land in the meantime. > ---- > > * [taglib] All Javascript validation fails when <html:xhtml... > * http://issues.apache.org/bugzilla/show_bug.cgi?id=35127 > > Unless Commons Validator 1.15 is imminent, we could live this for Classic > 1.3.1 I'm pretty sure that Validator 1.1.5 is coming any time soon, so I'd say push this to later. > ---- > > * multiform validation > * http://issues.apache.org/bugzilla/show_bug.cgi?id=35513 > > Confirm report during testing. May be support issue. The description could be more clear, but this looks like a misunderstanding of the way Struts works. (i.e. yes, a validation error causes a return to the 'input' page.) Looks like an INVALID to me, but I could be misreading it. > ---- > > * Attributes with <rtexprvalue>false</rtexprvalue> > * http://issues.apache.org/bugzilla/show_bug.cgi?id=35895 > > Is there a reason why these tag attributes are marked RE false? I strongly suspect there was, but not knowing what it was, I can't say whether or not it's still valid. My first guess would be because of rules about exposing new variables from tags, but perhaps Craig or David K could chime in on this one. -- Martin Cooper > bean > * cookie.id > * define.id > * header.id > * anchor.id > * page.id > * parameter.id > * resource.id > * size.id > * struts.id > > html > * javascript.dynamicJavascript > * javascript.staticJavascript > * messages.id > > logic > * collection.id > * iterate.indexId > > ---- > > * Remove deprecations prior to 1.3.0 release > * http://issues.apache.org/bugzilla/show_bug.cgi?id=35953 > > Hubert, will you still be able to handle this? (Pretty please ..) > > --- > > -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]
