Well, I looked and the code is still in there. It must not be working
right. Can someone post a trace of a failing request?
-James
On Sat, 2005-02-05 at 23:48 +0200, Roman D wrote:
> That thread from 25-Jan-2005 is indeed about this same issue.
> I build from HEAD and tests fail with reference implementation.
> Well he said it "should" be fixed. hmm... "should" doesn't mean "had"
> I wonder if patch got lost on the way or something.
>
>
> John Rousseau wrote:
> > I thought James Mason submitted a patch for this recently (he sent mail
> > on 24 Jan, copied below) after I reported the same issue. Unfortuantely,
> > I have not yet had a chance to verify it myself.
> >
> > -John
> >
> >
> > On 2005-01-24 at 11:17 +0500 James Mason wrote:
> >
> > > This should be fixed in Slide HEAD now.
> >
> >
> > Roman D wrote:
> >
> >>
> >> Thank you for the patch! that fixed NPE!
> >> My WCK store saves properties and return them exactly as they were set
> >> by client.
> >> Still I have litmus failures;
> >>
> >> -> running `props':
> >> 0. init.................. pass
> >> 1. begin................. pass
> >> 2. propfind_invalid...... pass
> >> 3. propfind_invalid2..... pass
> >> 4. propfind_d0........... pass
> >> 5. propinit.............. pass
> >> 6. propset............... pass
> >> 7. propget............... FAIL (No value given for property
> >> {http://webdav.org/neon/litmus/}prop9)
> >> 8. propextended.......... pass
> >> 9. propmove.............. pass
> >> 10. propget............... FAIL (No value given for property
> >> {http://webdav.org/neon/litmus/}prop9)
> >> 11. propdeletes........... pass
> >> 12. propget............... FAIL (No value given for property
> >> {http://webdav.org/neon/litmus/}prop9)
> >> 13. propreplace........... pass
> >> 14. propget............... FAIL (No value given for property
> >> {http://webdav.org/neon/litmus/}prop9)
> >> 15. propnullns............ pass
> >> 16. propget............... FAIL (No value given for property
> >> {}nonamespace)
> >> 17. prophighunicode....... pass
> >> 18. propget............... FAIL (No value given for property
> >> {http://webdav.org/neon/litmus/}high-unicode)
> >> 19. propvalnspace......... pass
> >> 20. propwformed........... pass
> >> 21. propinit.............. pass
> >> 22. propmanyns............ pass
> >> 23. propget............... FAIL (No value given for property
> >> {kappa}somename)
> >>
> >>
> >> Is it WCK problem or Is there anything I can do to improve situation?
> >>
> >> Is WCK supposed to be litmus-proof?
> >>
> >> Thanks.
> >>
> >> Oliver Zeigermann wrote:
> >>
> >>> Thanks for reporting. Of course no test should cause a
> >>> NullPointerException. I have committed a patch that adapts WCK to the
> >>> new PropertyName version that should fix this issue.
> >>>
> >>> Oliver
> >>>
> >>>
> >>> On Sat, 05 Feb 2005 05:07:08 +0200, Roman D <[EMAIL PROTECTED]> wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> I have store with WCK, and when testing with litmus I get a
> >>>>
> >>>> java.lang.NullPointerException
> >>>> at
> >>>> org.apache.slide.common.PropertyName.getPropertyName(PropertyName.java:121)
> >>>>
> >>>>
> >>>> at
> >>>> org.apache.slide.content.NodeProperty.<init>(NodeProperty.java:117)
> >>>> at
> >>>> org.apache.slide.simple.store.WebdavStoreAdapter$TransactionId.retrieveRevisionDescriptor(WebdavStoreAdapter.java:625)
> >>>>
> >>>>
> >>>>
> >>>> It has something to do with namespaces, and it happens when litmus test
> >>>> for setting property "http://something/something/";, value "something"
> >>>>
> >>>> Storing of properties implemented same as reference WebdavFileStore, so
> >>>> I am wondering,
> >>>>
> >>>> Is WCK WebDAV-compliant according to litmus test?
> >>>> Should WCK-based implementation be expected to pass all litmus tests ?
> >>>>
> >>>> Thanks.
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>>> For additional commands, e-mail: [EMAIL PROTECTED]
> >>>>
> >>>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
