You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by David Kennedy <da...@us.ibm.com> on 2006/08/15 15:25:24 UTC

Litmus setup to run against jackrabbit

I'm trying to run litmus against my jackrabbit webdav install, but am 
getting a Forbidden response when the litmus begin test attempts to run 
delete and/or mkcol for 'litmus'.  Is there something I need to change 
about the litmus tests to run them against jackrabbit? 

David

Re: Litmus setup to run against jackrabbit

Posted by Angela Schreiber <an...@day.com>.
David Kennedy wrote:

> When 
> you responded previously that the testcases you used to drive the webdav 
> server were the litmus tests, I'd assumed that the same tests could be 
> used against either servlet.  

ah? so you didn't read my follow-up remark?

http://www.mail-archive.com/dev@jackrabbit.apache.org/msg02118.html

and even the original post points to a JIRA issue that
only affects the simple server... btw. JCR-416 is fixed
in the meantime... this may answer your questions below
regarding PROPPATCH.

> Do you have a test suite you use to drive 
> the JCRWebdavServerServlet?

http://www.mail-archive.com/dev@jackrabbit.apache.org/msg02118.html

since the client is not completed yet (again this clearely
stated in the index.jsp and in multiple previous posts),
the answer is no... there is no need for a separate test
suite... the TCK was delivered with JSR 170.

regards
angela


Re: Litmus setup to run against jackrabbit

Posted by David Kennedy <da...@us.ibm.com>.
Angela Schreiber <an...@day.com> wrote on 08/15/2006 10:21:46 AM:

> David Kennedy wrote:
> 
> > I'm running JCRWebdavServerServlet (not the simple server).
> 
> hm. this doesn't make sense from my point of view.
> 

I guess you're saying it doesn't make sense that I'd be running litmus 
against the JCRWebdavServerServlet and not that the problem is occurring. 
I didn't realize "all bets are off" with JCRWebdavServerServlet and that 
only the SimpleWebdavServlet is modeled to be compliant.  I thought the 
remoting with the JCRWebDavServerServlet was still an attempt to be 
compliant (with additional extensions where needed).  My mistake.  When 
you responded previously that the testcases you used to drive the webdav 
server were the litmus tests, I'd assumed that the same tests could be 
used against either servlet.  Do you have a test suite you use to drive 
the JCRWebdavServerServlet?

btw, as I'm sure you are aware, the reason the tests wouldn't run is 
because based on the URL, 
http://<host>:<port>/<contextroot>/server/litmus, that is parsed litmus is 
parsed to be the workspace (which I adjusted the config so my default 
workspace was created as litmus) and the Resource path is /.  This will 
cause the RootItemCollection to be created which, when requested for its 
collection, returns the parent or RootCollection representing the 
workspace.  This collection does not permit addMember or removeMember.

My litmus tests did run against the SimpleWebdavServlet with the exception 
of propmanyns of prop (possibly the patch you recently contributed) and 
propget of prop (No value given for property {kappa}somename)

So is there a suite of tests to run against JCRWebdavServerServlet?

> litmus expects that a MKCOL can be performed without request
> body, that a simple file can be created and modified and
> last but not least that any kind of properties can be set
> and removed and reset.
> 
> the simple server was built keeping dav compliance in mind.
> 
> in contrast this was never the aim for the jcr-server. the
> aim of the jcr-server was and is - as i keep pointing out -
> to allow remoting of jcr calls via webdav. this is a different
> thing and complete dav compliance was never the goal.
> example:
> MKCOL is used to call Node.addNode(). Under certain conditions
> providing a jcr name only might not be sufficient and a
> nodetype name must be specified. this would be done by building
> a request body.
> 
> the differences between simple and jcr-server have been
> explained various times in the dev list and a summary is
> also present in the index.jsp.
> 
> regards
> angela
> 
> 
> 
> 

Re: Litmus setup to run against jackrabbit

Posted by Angela Schreiber <an...@day.com>.
David Kennedy wrote:

> I'm running JCRWebdavServerServlet (not the simple server).

hm. this doesn't make sense from my point of view.

litmus expects that a MKCOL can be performed without request
body, that a simple file can be created and modified and
last but not least that any kind of properties can be set
and removed and reset.

the simple server was built keeping dav compliance in mind.

in contrast this was never the aim for the jcr-server. the
aim of the jcr-server was and is - as i keep pointing out -
to allow remoting of jcr calls via webdav. this is a different
thing and complete dav compliance was never the goal.
example:
MKCOL is used to call Node.addNode(). Under certain conditions
providing a jcr name only might not be sufficient and a
nodetype name must be specified. this would be done by building
a request body.

the differences between simple and jcr-server have been
explained various times in the dev list and a summary is
also present in the index.jsp.

regards
angela





Re: Litmus setup to run against jackrabbit

Posted by David Kennedy <da...@us.ibm.com>.
Angela Schreiber <an...@day.com> wrote on 08/15/2006 09:37:19 AM:

> David Kennedy wrote:
> > I'm trying to run litmus against my jackrabbit webdav install, but am 
> > getting a Forbidden response when the litmus begin test attempts to 
run 
> > delete and/or mkcol for 'litmus'.  Is there something I need to change 

> > about the litmus tests to run them against jackrabbit? 
> 
> you shouldn't have to with the simple server.
> after fixing JCR-416 even proppatch is expected
> to work without any configuration changes.
> 
> do you run the test with the simple server?
> what is the reason for the Forbidden?
> 
> angela
> 

I'm running JCRWebdavServerServlet (not the simple server).  The reason 
for the Forbidden is that the removeMember (for DELETE) is attempted 
against the RootCollection (tracking down why I'm getting that). Similarly 
for the addMember (for MKCOL).

David

Re: Litmus setup to run against jackrabbit

Posted by Angela Schreiber <an...@day.com>.
David Kennedy wrote:
> I'm trying to run litmus against my jackrabbit webdav install, but am 
> getting a Forbidden response when the litmus begin test attempts to run 
> delete and/or mkcol for 'litmus'.  Is there something I need to change 
> about the litmus tests to run them against jackrabbit? 

you shouldn't have to with the simple server.
after fixing JCR-416 even proppatch is expected
to work without any configuration changes.

do you run the test with the simple server?
what is the reason for the Forbidden?

angela