not from the top of my head, regards Ard
On Tue, Mar 16, 2010 at 9:37 PM, Karel Reinhard <[email protected]> wrote: > I agree about the overhead. > Only i'm using this no-acl option for performance improvement for an > existing anwb app so I hoped it would be backward compatible. > Are the're any other options wich aren't allowed? > > Karel Reinhard > > 2010/3/16 Jasha Joachimsthal <[email protected]> > >> On 16 March 2010 15:50, Ard Schrijvers <[email protected]> wrote: >> >> > On Tue, Mar 16, 2010 at 3:46 PM, Karel Reinhard >> > <[email protected]> wrote: >> > > Hello Jasha, >> > > >> > > Maybee it has something to do with this? >> > > In the nl.hippo.slide.webdav.method.SearchNoACLMethod.java >> > > At line 290 this method is called Iterator props = >> > > requestedProperties.getRequestedProperties(); >> > > When I look up this code in the api of >> > > >> > >> http://jakarta.apache.org/slide/javadoc-2.1/javadoc/org/apache/slide/common/RequestedProperties.htmlis >> > > see this: >> > > * >> > > /// >> > > getRequestedProperties >> > > >> > > public java.util.Iterator getRequestedProperties() >> > > >> > > Method getRequestedProperties >> > > >> > > Returns: >> > > an Iterator to retrieve all RequestedProperty items >> > > Throws: >> > > java.lang.IllegalStateException - when isAllProp == true* >> > >> > only indexed and stored properties can be returned. Think when I wrote >> > it back in those days, I decided that allprops would not be allowed >> > >> > Ard >> > >> > Now that I think of it more, it's a good thing, because in most cases >> it's >> very inefficient to search for all props. You're probably only interested >> in >> a subset and all the unused properties cause a lot of overhead / >> datatraffic. >> >> Jasha >> >> > /// >> > > >> > > >> > > So it look like the select allprops dasl isn't implented/not supported >> > with >> > > search noacl? >> > > >> > > Regards Karel Reinhard >> > > >> > > 2010/3/16 Karel Reinhard <[email protected]> >> > > >> > >> Hello Jasha, >> > >> >> > >> This is the dasl this one works with the SEARCH method given in the >> http >> > >> head and doesn't work with the SEARCH-NOACL method in the head. >> > >> >> > >> Karel Reinhard >> > >> >> > >> <d:searchrequest xmlns:h="http://hippo.nl/cms/1.0"; xmlns:d="DAV:" >> > >> xmlns:s="http://jakarta.apache.org/slide/";> >> > >> <d:basicsearch> >> > >> <d:select> >> > >> <d:allprop /> >> > >> </d:select> >> > >> <d:from> >> > >> <d:scope> >> > >> <d:href /> >> > >> <d:depth> >> > >> 2 >> > >> </d:depth> >> > >> <s:minimum-depth> >> > >> 1 >> > >> </s:minimum-depth> >> > >> </d:scope> >> > >> </d:from> >> > >> <d:where> >> > >> <d:eq> >> > >> <d:prop> >> > >> <d:displayname /> >> > >> </d:prop> >> > >> <d:literal> >> > >> reis-en-cadeauartikelen.xml >> > >> </d:literal> >> > >> </d:eq> >> > >> </d:where> >> > >> </d:basicsearch> >> > >> </d:searchrequest> >> > >> >> > >> 2010/3/16 Jasha Joachimsthal <[email protected]> >> > >> >> > >> On 16 March 2010 13:10, Karel Reinhard <[email protected]> >> > wrote: >> > >>> >> > >>> > Hello, >> > >>> > >> > >>> > I'm trying to get the dasl's no-acl option to work with my portal >> > >>> > application. >> > >>> > I,m using the portal in combination with >> > >>> > hippo-repository-webdav-client-2.11.03.jar >> > >>> > >> > >>> > Most af the no-acl dasl queries working fine but with some of the >> > >>> queries i >> > >>> > get a http 500 >> > >>> > >> > >>> At the same time this stackttrace(below) is shown in the server.log >> > from >> > >>> the >> > >>> > repository/ >> > >>> > >> > >>> > Some extra information: >> > >>> > I added the storeAll option to the dasl-indexer.xml removed the >> > lucine >> > >>> > index >> > >>> > and restarted the repository. >> > >>> > The same dasl work fine with the standard SEARCH but with the >> > >>> SEARCH-NOACL >> > >>> > it fails. >> > >>> > >> > >>> > Any advice would be appreciated. >> > >>> > >> > >>> >> > >>> That's a bit hard to say if we don't know the queries. Can you give >> an >> > >>> example of a working query and a non working query? >> > >>> >> > >>> >> > >>> Jasha Joachimsthal >> > >>> >> > >>> [email protected] - [email protected] >> > >>> >> > >>> www.onehippo.com >> > >>> Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam >> +31(0)20-5224466 >> > >>> San Francisco - Hippo USA Inc. 185 H Street, suite B, Petaluma CA >> 94952 >> > +1 >> > >>> (707) 7734646 >> > >>> >> > >>> >> > >>> > >> > >>> > >> > >>> ******************************************** >> > >>> Hippocms-dev: Hippo CMS 6 development public mailinglist >> > >>> >> > >>> Searchable archives can be found at: >> > >>> MarkMail: http://hippocms-dev.markmail.org >> > >>> Nabble: http://www.nabble.com/Hippo-CMS-f26633.html >> > >>> >> > >>> >> > >> >> > > ******************************************** >> > > Hippocms-dev: Hippo CMS 6 development public mailinglist >> > > >> > > Searchable archives can be found at: >> > > MarkMail: http://hippocms-dev.markmail.org >> > > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html >> > > >> > > >> > ******************************************** >> > Hippocms-dev: Hippo CMS 6 development public mailinglist >> > >> > Searchable archives can be found at: >> > MarkMail: http://hippocms-dev.markmail.org >> > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html >> > >> > >> ******************************************** >> Hippocms-dev: Hippo CMS 6 development public mailinglist >> >> Searchable archives can be found at: >> MarkMail: http://hippocms-dev.markmail.org >> Nabble: http://www.nabble.com/Hippo-CMS-f26633.html >> >> > ******************************************** > Hippocms-dev: Hippo CMS 6 development public mailinglist > > Searchable archives can be found at: > MarkMail: http://hippocms-dev.markmail.org > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > ******************************************** Hippocms-dev: Hippo CMS 6 development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
