Hi, I noticed that in case the parameter org.apache.myfaces.trinidad.UPLOAD_TEMP_DIR points to an unexisting directory, an exception is thrown by UploadedFileImpl, but it has no chance to be caught by application code, since occurring from withing the TrinidadFilter. The final result is that users try to save uploaded files, but nothing happens and no errors are shown. Very frustrating from the user point of view. This is the typical situation when things appears running fine at the developer site, while they don't run at all at the customer site, just because a directory is missing.
Any workaround to catch that exception and to report it gently to the user ?
Or is there any way to check that parameter consistency in advance, being usually a static issue ?

-- Renzo

Reply via email to