[jira] Created: (ADFFACES-323) file upload: UPLOAD_MAX_MEMORY limit

["Jim Graf (JIRA)" <ad...@incubator.apache.org>]

file upload: UPLOAD_MAX_MEMORY limit
------------------------------------

                 Key: ADFFACES-323
                 URL: http://issues.apache.org/jira/browse/ADFFACES-323
             Project: MyFaces ADF-Faces
          Issue Type: Bug
          Components: Build
            Reporter: Jim Graf
            Priority: Minor


I stumbled across this issue when I changed UPLOAD_MAX_MEMORY to 3G:

org/apache/myfaces/trinidadinternal/webapp/UploadedFileProcessorImpl.java:

private long   _maxDiskSpace = -1;

but

_maxDiskSpace = Integer.parseInt(maxDiskSpace);

I think this makes more sense:

_maxDiskSpace = Long.parseLong(maxDiskSpace);

Occasionally we do need to allow a customer to upload a file greater then the 2G limit that the above code implies. I haven't (successfully) converted this app over to Trinidad yet and I'm unlikely to get any help from Oracle as I don't use jdeveloper and I don't have a contract.

thanks,
jim

ps. obviously _maxMemory should be treated the same way.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (ADFFACES-323) file upload: UPLOAD_MAX_MEMORY limit

["Matthias Weßendorf (JIRA)" <ad...@incubator.apache.org>]

     [ https://issues.apache.org/jira/browse/ADFFACES-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias Weßendorf updated ADFFACES-323:
----------------------------------------

    Affects Version/s: 1.0.1-incubating-core-SNAPSHOT

> file upload: UPLOAD_MAX_MEMORY limit
> ------------------------------------
>
>                 Key: ADFFACES-323
>                 URL: https://issues.apache.org/jira/browse/ADFFACES-323
>             Project: MyFaces ADF-Faces
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 1.0.1-incubating-core-SNAPSHOT
>            Reporter: Jim Graf
>            Priority: Minor
>
> I stumbled across this issue when I changed UPLOAD_MAX_MEMORY to 3G:
> org/apache/myfaces/trinidadinternal/webapp/UploadedFileProcessorImpl.java:
> private long   _maxDiskSpace = -1;
> but
> _maxDiskSpace = Integer.parseInt(maxDiskSpace);
> I think this makes more sense:
> _maxDiskSpace = Long.parseLong(maxDiskSpace);
> Occasionally we do need to allow a customer to upload a file greater then the 2G limit that the above code implies. I haven't (successfully) converted this app over to Trinidad yet and I'm unlikely to get any help from Oracle as I don't use jdeveloper and I don't have a contract.
> thanks,
> jim
> ps. obviously _maxMemory should be treated the same way.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.