Don't know about the event trigger problem, but...
On Apr 20, 2004, at 3:08 AM, Chris Joelly wrote:
btw: is the exception handling in 2.3 better than in 2.2 when a user tries to upload a file BIGGER than configured with TurbineResources.properties?
No. It would appear to be exactly the same as before, with the exception that the File Upload code is now located in commons-fileupload. However, the trick that I am using now is to specify a max upload size that is my desired max * 10 and I am detecting in my field validation code that a file is larger than it should be, and reporting that back using our standard method of field validation. We are only handling image uploads at this point, so it is unlikely that someone would miss our limit by an order of magnitude, and if they do they just get that nasty page that currently comes back. However, in either case we have to upload the file before knowing how big it is so this really isn't any extra work (right?)
I had at one point changed the upload service to actually add an Exception to the parameter parser in place of a FileItem, so that I could detect within my field validation that the file was too large, but this code ultimately died due to other problems.
Hope this helps...
-Brian
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
