in 1.4.9 it worked because we did not take visibility of children into account. eg an invisible multipart component would make the form multipart as well. this was inconsistent so it was fixed.
as far as automatic detection - i think in this case it happens during an ajax update and going from non-multipart to multipart would require the form tag to be updated to add the encoding. if axl updated the formtag via ajax then everything would work, but i dont think it is the case. -igor On Tue, Jan 18, 2011 at 9:12 PM, Jeremy Thomerson <jer...@wickettraining.com> wrote: > On Tue, Jan 18, 2011 at 11:08 PM, Arjun Dhar <dhar...@yahoo.com> wrote: > >> >> Hi am not sure if a user vote is going on here. >> > > Nah - a vote would have [VOTE] in the subject, and they are typically only > on the dev@ list, not users@. But, we're *always* open to feedback here. > > My 2 cents for my own insecurities: Leave it as is! Its good enough. >> I'm pretty much screwing around with FileUpload in many ways and overall >> its >> great. >> > > Well, that's the thing. According to the original poster, the functionality > differs between 1.4.9 and 1.4.15. So, if that's the case, this was a minor > regression. So, which way should it be? Well, that's what I'm asking :) > > -- > Jeremy Thomerson > http://wickettraining.com > *Need a CMS for Wicket? Use Brix! http://brixcms.org* > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
