I can use either oslc.where or oslc.searchTerms on their own, but when I specify both of them I get error 501 (Not Implemented) - is there any way to get around this, or it is a bug?
My URL is:
If it is impossible to combine text search with a where clause it's a very serious limitation, as well as a violation of the OSLC v2 API that I thought CQ supported - as it says in http://open-services.net/bin/view/Main/OSLCCoreSpecQuery#oslc_searchTerms "When oslc.where is used with oslc.searchTerms then the set of resources searched for matches MUST be restricted to only those resources that satisfy the conditions in oslc.where".
I was able to use text search with a query using the older v1 OSLC api, and I'm quite frustrated that after investing lots of time upgrading everything to use the v2 API (which is quite an effort) the functionality seems to have significantly regressed (especially as there's nothing in the CQ documentation to warn people of this)
Any input on this would be a great help, especially if there's some way round it. I don't want to have to revert everything back to the v1 OSLC api!
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
4 replies Latest Post - 2013-01-07T09:59:10Z by cglockner
Pinned topic oslc.where and oslc.searchTerms no longer work together in OSLC v2
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-01-07T09:59:10Z at 2013-01-07T09:59:10Z by cglockner
cglockner 2700009784345 Posts
Re: oslc.where and oslc.searchTerms no longer work together in OSLC v22012-12-19T15:35:09Z in response to cglocknerHi Christian,
Just authorization and OSLC version:
headers = 'Basic %s'%credentials
headers = '2.0'
Is there any magic header I could set to get it to work? Or is it a known bug/limitation (i.e. I need to switch everything back to OSLC v1)?