Well as per Pedro and Igor's observation - if I setMultiPart(true) on the root form on initialisation, then I don't encounter exceptions any more using Wicket 1.4.15. I've applied this in our main development project and it seems to work fine.
As a quick test, I switched back to Wicket version 1.4.9 for our main development project and also reverted the above change (removed that setMultiPart(true) on our root form). The same kind of workflow worked without throwing a multipart related exception, so I suspect that in 1.4.9 the automatic multipart detection was able to correctly update the root form multipart setting. This is not to say that 1.4.9 is the correct behaviour, since I'm thinking that perhaps 1.4.15 enables greater manual control over how multipart works on each form. So I think Jeremy (and Pedro earlier?) asks a valid question as to whether the FileUpload should always be automatically updating the root form multipart properties depending on the FileUpload field being enabled and visible. As long as I can understand the expected behaviour, then either way should be fine as long as I can still do what I want to do :) Let us know what is decided... ----- Eric is learning how to use Wicket and enjoying the experience so far... -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Multipart-issues-in-Wicket-1-4-15-tp3221308p3224533.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
