[ 
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

        

Reply via email to