OSLC where and wildcard

[philchudley]

Hi All

I have been playing around with Version 11 and OSLC

It appears that wildcard query is not supported, for example the following works just fine

http://localhost:804/ea_demo/oslc/qc/?oslc.where=ss:type="Functional"

but the following returns an HTTP 400 Bad Request error

http://localhost:804/ea_demo/oslc/qc/?oslc.where=ss:type="%Funct%"

Does Version 11 support OSCL wildcard queries?  If not is support for wildcards planned?

Cheers

[qwerty]

No idea what you are talking about but have you tried "*" instead of "%"?

q.

[philchudley]

Thanks for the suggestion I have tried * and % but both have same effect

[Geert Bellekens]

Hi Phil,

Ten years later, I stumbled upon this post trying to find a solution for the same problem.

Do you know if they have somehow resolved this problem?
Or if there is another way to get a list of all elements that have a certain term in their name or description?

WebEA seems to be able to do it, so there must be a way.

Geert

[Eve]

https://sparxsystems.com/enterprise_architect_user_guide/16.1/the_model_repository/oslc_where.html

The wildcard (defined by the standard) appears to be '*'.

[Geert Bellekens]

https://sparxsystems.com/enterprise_architect_user_guide/16.1/the_model_repository/oslc_where.html

The wildcard (defined by the standard) appears to be '*'.

We found that, but it appears that you can only use the wildcard to specify the properties to look into.
Not to find say all elements that have "searchTerm" somewhere in their comments.

I was hoping we could use

Code: [Select]

...where=dcterms:description="*searchTerm*"But that doesn't work.

I did some googling, and it appears we would need to use oslc.searchTerms="searchTerm" but that doesn't seem to be implemented by PCS.

Is there an alternative for this?

I really feel like I'm missing something. I know WebEA has a search function, and Prolaborate has even much more advanced query possibilities; but I don't see anything in the OSCL interface that I could use to implement such a search function myself.

It feels like there should be some kind of equivalent for Repository.SQLQuery in the PCS interface, but I can't seem to find it.

Geert