About "Upload and download files from ADF into blob type colum."

Question

hi
Using JDeveloper 10.1.3.3.0 I have tried the example available for download from this blog post by Jakub Pawlowski:
"Upload and download files from ADF into blob type colum."
at http://kuba.zilp.pl/?id=1
First a thank you to Jakub for this interesting example.
I have a question about a PDF file that I uploaded using the example.
The file has a size of 10445518 bytes.
After I upload that file, the blob column has a value with a size of 10445516 bytes, 2 bytes less.
SQL> select file_name, dbms_lob.getlength(stored_file) from blob_table;
FILE_NAME
DBMS_LOB.GETLENGTH(STORED_FILE)
ADF-DeveloperGuide-4GL-B25947_01.pdf
                       10445516If I download that file using the example, it has the same size as the blob value, 10445516 bytes.
If I open the downloaded file, using Adobe Reader 8.1.1, it first shows this message:
"The file is damaged but is being repaired."
After that, there is not problem using the PDF file in Adobe Reader.
I have tried this with both Internet Explorer 6 and Firefox 2.0.0.11.
I have also tried this with other (smaller) files, and those upload and download correctly.
question:
Why are those 2 bytes lost during upload?
many thanks
Jan Vervecken

Answer 1

Hi!
I can only post you my code that works for me and as I said I had same problems but can't remember what solved them. My code:
  public void fileUploaded(ValueChangeEvent event)
    FacesContext fc = FacesContext.getCurrentInstance();
    UploadedFile file = (UploadedFile) event.getNewValue();
    if (file != null && file.getLength() > 0)
      // here I have some messages written and a call to the method on AM to save the uploaded file to the DB
  private BlobDomain newBlobDomainForInputStream(InputStream in)
    throws SQLException, IOException
    BlobDomain loBlob = new BlobDomain();
    OutputStream out = loBlob.getBinaryOutputStream();
    writeInputStreamToWriter(in, out);
    in.close();
    out.close();
    return loBlob;
  private static void writeInputStreamToWriter(InputStream in,
                                               OutputStream out)
    throws IOException
    byte[] buffer = new byte[8192];
    int charsRead = 0;
    while ((charsRead = in.read(buffer, 0, 8192)) != -1)
      out.write(buffer, 0, charsRead);
   * Launch the upload - see fileUploaded() for actual upload handling.
   * @return null navigation event - we stay on this page
  public String UploadButton_action()
    if (this.getMyInputFile().getValue() == null)
      FacesContext context = FacesContext.getCurrentInstance();
      FacesMessage message =
        new FacesMessage(FacesMessage.SEVERITY_WARN, JSFUtils.getStringFromBundle("fileupload.emptyfielderror"),
                         null);
      context.addMessage(this.getMyInputFile().getId(), message);
    return null;
   * Setter for inputFile UI Component.
   * @param inputFile inputFile UI component
  public void setMyInputFile(CoreInputFile inputFile)
    this.myInputFile = inputFile;
   * Getter for inputFile UI Component.
   * @return inputFile UI component
  public CoreInputFile getMyInputFile()
    return myInputFile;
  }fileUploaded is a valueChangeListener on inputFile and UploadButton_action is as the name says the action for upload button.
Hope this helps. If not, than your problem is probably not the same as mine was, although the message about file corrupted was the same.
Next thing you can check in this case is if your file exceeds max file upload size. I don't know the exact default value, but if the file is too long I think this upload logic will upload only a part of the file and save it to the DB which can also lead to the same file corrupted error.
You can set the max upload value in web.xml like this:
<context-param>
<!-- Maximum memory per request (in bytes) -->
<param-name>oracle.adf.view.faces.UPLOAD_MAX_MEMORY</param-name>
<!-- Use 5000K -->
<param-value>5120000</param-value>
</context-param>
<context-param>
<!-- Maximum disk space per request (in bytes) -->
<param-name>oracle.adf.view.faces.UPLOAD_MAX_DISK_SPACE</param-name>
<!-- Use 10,000K -->
<param-value>15360000</param-value>
</context-param>