You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2011/09/09 15:09:09 UTC

[jira] [Created] (SLING-2215) DavEx servlet creates a jackrabbit/tmp directory

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


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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Reopened] (SLING-2215) DavEx servlet creates a jackrabbit/tmp directory

Posted by "Jukka Zitting (Reopened) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting reopened SLING-2215:
----------------------------------


Reopening. The SLING-2301 changes didn't touch the org.apache.sling.jcr.davex bundle.
                
> 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

        

[jira] [Commented] (SLING-2215) DavEx servlet creates a jackrabbit/tmp directory

Posted by "Brandon Biondo (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SLING-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165682#comment-13165682 ] 

Brandon Biondo commented on SLING-2215:
---------------------------------------

On systems with more stringent security restrictions for these kinds of directories, this is not a minor bug. It would be nice to get this patch in sooner rather than later.
                
> 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
>         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

        

[jira] [Resolved] (SLING-2215) DavEx servlet creates a jackrabbit/tmp directory

Posted by "Carsten Ziegeler (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-2215.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: JCR DavEx 1.1.0

This has been fixed by SLING-2301
                
> 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

        

[jira] [Updated] (SLING-2215) DavEx servlet creates a jackrabbit/tmp directory

Posted by "Jukka Zitting (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated SLING-2215:
---------------------------------

    Attachment: 0001-SLING-2215-DavEx-servlet-creates-a-jackrabbit-tmp-di.patch

It turns out that the jackrabbit/tmp path was hardcoded in the SlingDavExServlet class. The code dates back to revision 1199645 of SLING-2275, where the temporary folder path got set to ${sling.home}/jackrabbit/tmp to avoid the default plain jackrabbit/tmp path.

The attached patch removes the hardcoded path. Nowadays the default is to use the standard ${java.io.tmpdir} folder for temporary files.
                
> 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, 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

        

Re: Temporary Files in Sling (Re: [jira] [Commented] (SLING-2215) DavEx servlet creates a jackrabbit/tmp directory)

Posted by Bertrand Delacretaz <bd...@apache.org>.
On Mon, Jan 23, 2012 at 3:47 PM, Justin Edelson
<ju...@justinedelson.com> wrote:
> ...This just seems like another thing to configure. We should just use
> java.io.tmpdir to store temporary files...

I was going to say that: what's wrong with File.createTempFile() ?

-Bertrand

Re: Temporary Files in Sling (Re: [jira] [Commented] (SLING-2215) DavEx servlet creates a jackrabbit/tmp directory)

Posted by Justin Edelson <ju...@justinedelson.com>.
Hi,

This just seems like another thing to configure. We should just use
java.io.tmpdir to store temporary files.

Justin

On Mon, Jan 23, 2012 at 3:56 AM, Felix Meschberger <fm...@adobe.com> wrote:
> 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
>>
>>
>

Temporary Files in Sling (Re: [jira] [Commented] (SLING-2215) DavEx servlet creates a jackrabbit/tmp directory)

Posted by Felix Meschberger <fm...@adobe.com>.
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
> 
> 


[jira] [Commented] (SLING-2215) DavEx servlet creates a jackrabbit/tmp directory

Posted by "Jukka Zitting (Commented) (JIRA)" <ji...@apache.org>.
    [ 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

        

[jira] [Assigned] (SLING-2215) DavEx servlet creates a jackrabbit/tmp directory

Posted by "Justin Edelson (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Edelson reassigned SLING-2215:
-------------------------------------

    Assignee: Justin Edelson
    
> 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
>            Assignee: Justin Edelson
>            Priority: Minor
>             Fix For: JCR DavEx 1.1.0
>
>         Attachments: 0001-SLING-2215-DavEx-servlet-creates-a-jackrabbit-tmp-di.patch, 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

        

[jira] [Resolved] (SLING-2215) DavEx servlet creates a jackrabbit/tmp directory

Posted by "Justin Edelson (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Edelson resolved SLING-2215.
-----------------------------------

    Resolution: Fixed

thanks for the patch!

applied in r1234217
                
> 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
>            Assignee: Justin Edelson
>            Priority: Minor
>             Fix For: JCR DavEx 1.1.0
>
>         Attachments: 0001-SLING-2215-DavEx-servlet-creates-a-jackrabbit-tmp-di.patch, 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

        

[jira] [Issue Comment Edited] (SLING-2215) DavEx servlet creates a jackrabbit/tmp directory

Posted by "Brandon Biondo (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SLING-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165682#comment-13165682 ] 

Brandon Biondo edited comment on SLING-2215 at 12/8/11 11:49 PM:
-----------------------------------------------------------------

On systems with more stringent security restrictions for these kinds of directories, this is not a minor bug. It would be nice to get this patch in sooner rather than later.

edit: I should look before I type. Latest source already has the update! Thanks ^_^
                
      was (Author: brandondash):
    On systems with more stringent security restrictions for these kinds of directories, this is not a minor bug. It would be nice to get this patch in sooner rather than later.
                  
> 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
>         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

        

[jira] [Updated] (SLING-2215) DavEx servlet creates a jackrabbit/tmp directory

Posted by "Jukka Zitting (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated SLING-2215:
---------------------------------

    Attachment: 0001-SLING-2215-DavEx-servlet-creates-a-jackrabbit-tmp-di.patch

Proposed patch.
                
> 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
>         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