DataTable and UploadFile

[Michele Mazzilli]

Hello everyone,

Goal: In a jsf page, I defined a dataTable and a uploadFile. For Each file uploaded, the datatable will must update. I use a primefaces lib.

The code that i wrote:

@ManagedBean(name = "article")
@RequestScoped
public class EditArticle {
         @ManagedProperty(value = "#{param.id}")
         private Long id;
         // other properties and then
         private List<Attachment> attachments;

        public EditArticle() {
           setAttachments(new ArrayList<Attachment>());
        }

   public Long getId() { return id;}
   public void setId(Long id) { this.id = id;}

       public void setAttachments(List<Attachment> attachments ) {
      this.attachments = attachments ;
   }
       public List<Attachment> getAttachments() {
      return attachments ;
   }

       public void handleFileUpload(FileUploadEvent event) {
            // code to process file upload => create Attachment attachment
            getAttachments().add(attachment);
       }
}

article.xhtml
<h:form>
       <p:fileUpload fileUploadListener="#{article.handleFileUpload}"
                  mode="advanced"               
                  sizeLimit="1000000" update="fileList"
                  allowTypes="png,gif,jpg" >
        </p:fileUpload>
           
      <p:dataTable id="fileList" var="att" value="#{article.attachments}">
            <p:column>           
                               <f:facet name="header">File name</f:facet>
                              <h:outputText value="#{att.fileName}" />
                    </p:column>
         </p:dataTable>
</h:form>

Well, the problem is:
For each successfull upload file, dataTable show always last entry inserted because attachments in EditArticle managedBean is always empty.

Any idea??? Heeeelp
Thanks for all...

[Guy deLyonesse]

What's the scope of your managed bean?

[Michele Mazzilli]

Guy deLyonesse wrote:What's the scope of your managed bean?

hello Guy deLyonesse,

first, thank you for replay.
The scope is request, because i load from Db the Article with attachments if param.id is valorized.

[Guy deLyonesse]

I was just looking at a portlet I built that does exactly the same thing (except the files are uploaded as opposed to coming from a DB) but I'm using JSF 1.2 so I'm not sure how useful the code would be to you if you're in JSF 2.0.

In my backing bean:

private final List fileList = Collections.synchronizedList(new ArrayList());

The upload method:

    public void uploadFile(ActionEvent event) {
        InputFile inputFile = (InputFile) event.getSource();
        FileInfo fileInfo = inputFile.getFileInfo();
        if (fileInfo.getStatus() == FileInfo.SAVED) {
            // reference our newly updated file for display purposes and
            // added it to our history file list.
            currentFile = new InputFileData(fileInfo);

            synchronized (fileList) {
                fileList.add(currentFile);
            }

        }
    }

And the relevant part of the view.xhtml

			<ice:outputLabel for="file" value="Attachment(s)"/>
				<ice:inputFile id="file"
					autoUpload="true"
					actionListener="#{feedbackBacking.uploadFile}"/>

			<ice:dataTable width="450px" value="#{feedbackBacking.fileList}" var="file">
            <ice:column>
                <f:facet name="header">
                    <ice:outputLabel value="Filename"/>
                </f:facet>
                <ice:outputText value="#{file.fileInfo.fileName}"/>
            </ice:column>

            <ice:column>
                <f:facet name="header">
                    <ice:outputText value="Remove"/>
                </f:facet>
                <ice:commandLink value="Remove" partialSubmit="true" actionListener="#{feedbackBacking.removeUploadedFile}">
                    <f:param name="fileName" value="#{file.fileInfo.fileName}"/>
                </ice:commandLink>
            </ice:column>
        </ice:dataTable>

I'm using ICEfaces but the idea is the same for straight JSF.

[Michele Mazzilli]

Nada ... the attachment list is always empty.
maybe why the call is not Ajax?

tnx