rich:fileUpload - cancel upload from listener method and sho

[mail]

Hi all.
My situation is as follows:

I upload the file to DB (works wonderfully). Now I want to check if the file (name constraint) already exists in the DB. If yes, I want to cancel the upload and show the user an error message. How can I do it?

I tried this:

public void uploadDocument(UploadEvent event) throws Exception{
 UploadItem item = event.getUploadItem();
 logger.debug("uploadDocument: " + item.getFileName() + ":" + item.getFile() + ":" + item.getFileSize()
 + ":" + item.getContentType());

 if (checkFileExistsInDb(item.getFileName())) {
 FacesMessages.instance().addToControl("documentUpload", Severity.ERROR, "This file already exists!", new Object());
 } else {
 //do the uploade
 }
}

This error message never shows up.

Thanks in advance for your help.

Regards
Tathagat

[ilya_shaikovsky]

Yes, as the FU component sends a request per file and FacesMessage lives only for one request - them will be lost after next one and you will not be able to show them onuploadcomplete. Try to store them on some bean session or conversation scoped as a workaround and show after upload complete. The validation mechanism improvements for FU already planned in jira.

[mail]

Thanks for the prompt reply!
I understand the problem.

What about using validator attribute? I tried (by registering validator using Seam annotations) and it doesn't even get called. I also found a JIRA which says this.

https://jira.jboss.com/jira/browse/RF-7625
Also some more links that say the same:
http://lists.jboss.org/pipermail/richfaces-issues/2008-June/019943.html

Is there a way to call a validator?

Thanks again!

Regards
Tathagat[/url]

[ilya_shaikovsky]

currently validator will not helps you as messages will be lost in any way. So try to workaround it by storing messages manually.

[mail]

Alright. Thanks! Storing manually works fine.