Hi,
Torgeir Veimo schrieb:
>
> On 3 Jan 2009, at 04:58, Felix Meschberger wrote:
>
>> Torgeir Veimo schrieb:
>>>
>>> Do you know when? I have sling trunk from a few days ago running. Where
>>
>> Rev. 725679 dates from the 11. Dec. 2008.
>
> If I take the current sling svn trunk code, do a mvn install in the
> root, then a mvn install in launchpad/webapp, then use the resulting war
> file in the target directory, then I should get the latest sling trunk
> code?
Yes. Note, though, that if you run this latest applications using an
existing ${sling.home} folder, the newest bundles will only be installed
if you remove the existing ${sling.home}/felix folder first.
(Or more specifically: if you remove the
${sling.home}/felix/bundle0/bootstrapinstaller.ser file and all Sling
bundles before starting the new Sling (web) app)
>
>>> is the correct way to configure this manually? I had a look at the
>>> configuration settings for the webdav servlet, but I couldn't find any
>>> setting for the default node type.
>>
>> The configuration to look for is "Simple WebDAV Servlet
>> (org.apache.sling.jcr.webdav.impl.servlets.SimpleWebDavServlet)". This
>> should provide a whole lot of options. One of which is the "Collection
>> Primary Type" option, which defaults to sling:Folder.
>
>
> The simple webdav servlet configuration only has options for the
> authentication realm and the root path. Am a bit at a loss here..
>
This means the newest WebDAV bundle is not being used.
Please note (I only realized yesterday), that the news WebDAV bundle has
a required dependency on the org.apache.jackrabbit.jsr283 package. This
package is available from the Jackrabbit API 1.5.0 bundle [1] which must
be deployed. (When building and running Sling from trunk, you should get
this bundle installed already)
After refreshing the packages (or redeploying the WebDAV bundle), the
new configuration should be available. You might also want to inspect
the log file (${sling.home}/log/error.log by default) for any errors.
Hope this helps.
Regards
Felix
