Eclipse Community Forums: OCL » OCL query failing for the 'matches' function of String

Help

Home

Home » Modeling » OCL » OCL query failing for the 'matches' function of String

Show: Today's Messages :: Show Polls :: Message Navigator

OCL query failing for the 'matches' function of String [message #1451313]

Thu, 23 October 2014 16:48

Laurent Le Moux

Messages: 184
Registered: September 2011

Senior Member

Hi all,

I try to look for CDO resources using an OCL query based on a regular expression.

The following query works fine :

eresource::CDOResource.allInstances()->select(r:eresource::CDOResource | r.name='security')

Whereas the one using the 'matches' function fails :

eresource::CDOResource.allInstances()->select(r:eresource::CDOResource | r.name.matches('security'))

All I get, is the following error message with no more details in the log file :

OCL query evaluated to 'invalid'. Run with '-Dorg.eclipse.ocl.debug=true' and visit the log for failure details.

Any idea why this is happening ?

Kind regards,

Laurent

Report message to a moderator

Re: OCL query failing for the 'matches' function of String [message #1451693 is a reply to message #1451313]

Fri, 24 October 2014 06:41

Ed Willink

Messages: 7655
Registered: July 2009

Senior Member

Hi

You probably have a resource with a null name, so r.name.matches behaves
rather like Java; you get an invalid (NPE).

Try r.name <> null and ...

OCL 2.5 may introduce a safe navigation operator.

Regards

Ed Willink

On 23/10/2014 17:49, Laurent Le Moux wrote:
> Hi all,
>
> I try to look for CDO resources using an OCL query based on a regular
> expression.
>
> The following query works fine :
>
> eresource::CDOResource.allInstances()->select(r:eresource::CDOResource |
> r.name='security')
>
>
> Whereas the one using the 'matches' function fails :
>
> eresource::CDOResource.allInstances()->select(r:eresource::CDOResource |
> r.name.matches('security'))
>
>
> All I get, is the following error message with no more details in the
> log file :
>
> OCL query evaluated to 'invalid'. Run with
> '-Dorg.eclipse.ocl.debug=true' and visit the log for failure details.
>
>
> Any idea why this is happening ?
>
> Kind regards,
>
> Laurent

Report message to a moderator