Hi,
While I am basically ok to use the Jackrabbit Defaults, another old discussion
pops up again: Generic temporary file handling in Sling.
We currently have a number of places, where temporary files are created and
used. For example the Commons FileUpload library in the Engine or the
Jackrabbit based WebDAV bundles.
I wonder, whether we should provide a service which has the following:
* Provides access to a sling-wide temporary location (configurable,
default: ${sling.home}/tmp)
* Provides functionaliy to manage tmp files
* (For completeness) provides a method to create tmp files (based
on File.createTempFile using the configured tmp location)
This way, we could configure the FileUpload library and the WebDAV bundles
accordingly.
WDYT ?
Regards
Felix
Am 19.01.2012 um 20:24 schrieb Jukka Zitting (Commented) (JIRA):
>
> [
> https://issues.apache.org/jira/browse/SLING-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189313#comment-13189313
> ]
>
> Jukka Zitting commented on SLING-2215:
> --------------------------------------
>
> Sorry, the SLING-2301 change did indeed touch this bundle, even though it
> mentions the simple webdav bundle instead of the davex bundle.
>
> Anyway, there's still something wrong as the jackrabbit/tmp directory gets
> created when I start the davex bundle. I'll investigate.
>
>> DavEx servlet creates a jackrabbit/tmp directory
>> ------------------------------------------------
>>
>> Key: SLING-2215
>> URL: https://issues.apache.org/jira/browse/SLING-2215
>> Project: Sling
>> Issue Type: Bug
>> Affects Versions: JCR DavEx 1.0.0
>> Reporter: Jukka Zitting
>> Priority: Minor
>> Fix For: JCR DavEx 1.1.0
>>
>> Attachments:
>> 0001-SLING-2215-DavEx-servlet-creates-a-jackrabbit-tmp-di.patch
>>
>>
>> The DavEx servlet bundle added in SLING-1393 doesn't set the "home" and
>> "temp-directory" init parameters of the JcrRemotingServlet base class it
>> uses from Jackrabbit. As a result Jackrabbit defaults to "jackrabbit/tmp" as
>> the location
>> for temporary files, and creates such a directory under the current working
>> directory.
>> This problem is solved in the latest Jackrabbit trunk as of JCR-3029 where
>> the default location for temporary files was set
>> to the standard one defined by the java.io.tmpdir system property, so I
>> guess the easiest way to solve this is simply to
>> upgrade the dependency in Sling once the Jackrabbit 2.3.0 release is
>> available.
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators:
> https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
