If it is a comma seperated list which should work like keywords, then no: then you should index as text, and use a comma seperated analyzer.
If they aren't keywords, it works for a comma seperated list as well. For example if you have property: 'foo bar,bar foo,ard,jeroen,nico jeroen' Then, with a comma seperated analyzer and indexed as text you will find a hit for: <s:property-contains>ard</s:property-contains> <s:property-contains>bar foo</s:property-contains> But not for <s:property-contains>bar</s:property-contains> If you have it String indexed, you will get hits for the <s:propsearch>ard</s:propsearch> <s:propsearch>bar foo</s:propsearch> <s:propsearch>nico</s:propsearch> But, probably, you do not want the latter behavior, right?? Ard > Jeroen, Ard, > > Does the proposed solutions also work for properties which > contain a comma separated list? > > > Kind regards > > Nico Tromp > > 2008/9/11 Ard Schrijvers <[EMAIL PROTECTED]> > > > Without re-indexing or having to change the indexing, for > example if > > you also want to use the property to sort on or use d:eq > with, you can > > replace s:property-contains with s:propsearch. > > > > Regards Ard > > > > > > > > Hi Eelco, > > > > > > this could happen if you did not specify the property to > be indexed > > > as text. Quoting the WIki: > > > > > > "The given property has to be of type text" > > > > > > You can find out if it's indexed as a text property by looking at > > > the indexer configuration. (might be called dasl-indexer.xml or > > > something similar). > > > > > > Regards, > > > > > > Jeroen > > > > > > Eelco Muller wrote: > > > > What goes wrong here?? > > > > > > > > > > > > Query: > > > > > > > > <?xml version="1.0" encoding="utf-8" ?> <d:searchrequest > > > > xmlns:s="http://jakarta.apache.org/slide/"; > > > > xmlns:h="http://hippo.nl/cms/1.0"; xmlns:d="DAV:"> > > > > <d:basicsearch> > > > > .. > > > > <d:where> > > > > <d:and> > > > > <d:not> > > > > <d:is-collection /> > > > > </d:not> > > > > <s:property-contains> > > > > <d:prop> > > > > <h:products_in_category /> > > > > </d:prop> > > > > <d:literal>id2</d:literal> > > > > </s:property-contains> > > > > </d:and> > > > > </d:where> > > > > </d:basicsearch> > > > > </d:searchrequest> > > > > > > > > Gives: > > > > > > > > <?xml version="1.0" encoding="UTF-8"?> <D:multistatus > > > xmlns:D="DAV:"> > > > > <D:response> > > > > <D:href>/default</D:href> > > > > <D:status>HTTP/1.1 400 Bad Request</D:status> > > > > <D:responsedescription>Factory: Uncomparable > > > expression 'property-contains' for property > > > 'products_in_category'.</D:responsedescription> > > > > </D:response> > > > > </D:multistatus> > > > > > > > > The products_in_category is set on xml with > > > > > > > > webdavService.executePropPatch > > > > > > > > > > > > > > > > > > > > ******************************************************************** > > > ** > > > > ************************ > > > > Disclaimer > > > > > > > > E-mail wordt door ANWB niet gebruikt voor het aangaan van > > > externe verplichtingen. > > > > Deze e-mail is uitsluitend bestemd voor geadresseerde(n). > > > Indien deze > > > > e-mail onverhoopt niet voor u is bestemd dan verzoeken wij u > > > > vriendelijk contact op te nemen met de afzender en daarna > > > het bericht > > > > te vernietigen. Deze e-mail mag niet worden > doorgestuurd, openbaar > > > > gemaakt of verveelvoudigd worden zonder de toestemming van > > > de afzender. > > > > ANWB betracht grote zorgvuldigheid bij het verzenden van > > > e-mails. ANWB > > > > kan echter niet garanderen dat deze e-mail juist, volledig, > > > tijdig en > > > > virusvrij wordt overgebracht. In een dergelijk geval is > > > ANWB op geen > > > > enkele wijze aansprakelijk voor enige schade, direct dan > > > wel indirect, in welke vorm dan ook. > > > > > > > > ANWB B.V. > > > > > > > > ******************************************************************** > > > ** > > > > ************************ > > > > > > > > ******************************************** > > > > Hippocms-dev: Hippo CMS 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 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 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 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 development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
