Re: in-memory filter by Expression accessing regular methods

2017-04-18 Thread Maik Musall
Hi Michael, in the meantime I remembered I had already implemented NSKeyValueCodingAdditions for my DataObject subclass, so I just used that :-) Maik > Am 18.04.2017 um 18:23 schrieb Michael Gentry : > > Hi Maik, > > I'm late to this, but you likely could've used > obj.readProperty("responsib

Re: in-memory filter by Expression accessing regular methods

2017-04-18 Thread Michael Gentry
Hi Maik, I'm late to this, but you likely could've used obj.readProperty("responsibleUser") as well. mrg On Sun, Apr 16, 2017 at 7:13 AM, Musall, Maik wrote: > Wow, Mark, good guess! > > That's it. Added a get… method around each part of the path's accessed > methods, and it works. Didn't occ

Re: in-memory filter by Expression accessing regular methods

2017-04-18 Thread Mark Wardle
Glad it worked! Mark -- Dr. Mark Wardle Consultant Neurologist, Cardiff, UK (Sent from my mobile) > On 16 Apr 2017, at 12:13, Musall, Maik wrote: > > Wow, Mark, good guess! > > That's it. Added a get… method around each part of the path's accessed > methods, and it works. Didn't occur to m

Re: in-memory filter by Expression accessing regular methods

2017-04-16 Thread Musall, Maik
Wow, Mark, good guess! That's it. Added a get… method around each part of the path's accessed methods, and it works. Didn't occur to me at all, because those methods are not getters in the strict sense. But I could have discovered this before, by looking at the BeanAcccessor implementation. Dan

Re: in-memory filter by Expression accessing regular methods

2017-04-15 Thread Mark Wardle
Can't try it as only have phone at the moment but have you tried adding "get" as a prefix to your method declaration? I still find it difficult to not name getters without the get. -- Dr. Mark Wardle Consultant Neurologist, Cardiff, UK (Sent from my mobile) > On 13 Apr 2017, at 10:44, Musall

Re: in-memory filter by Expression accessing regular methods

2017-04-13 Thread Musall, Maik
Hi John, can you elaborate that on this example? Previously, I did this to filter: result = ExpressionFactory.matchExp( filterPath, filterValue ).filterObjects( result ); Now I tried: result = result.stream() .filter( obj -> PropertyUtils.getProperty( obj, filt

Re: in-memory filter by Expression accessing regular methods

2017-04-12 Thread John Huss
Ok, you can use property utils in conjunction to call a method using reflection (with a string name) On Wed, Apr 12, 2017 at 6:07 PM Musall, Maik wrote: > Hi John, > > how do you mean that? Those filter paths come from the UI, passed on by > the user assembling filter criteria. I wouldn't use str

Re: in-memory filter by Expression accessing regular methods

2017-04-12 Thread Musall, Maik
Hi John, how do you mean that? Those filter paths come from the UI, passed on by the user assembling filter criteria. I wouldn't use string filter paths if the criteria would be constant. Maik > Am 12.04.2017 um 19:03 schrieb John Huss : > > Just use a java 8 stream and lambda in addition or

Re: in-memory filter by Expression accessing regular methods

2017-04-12 Thread John Huss
Just use a java 8 stream and lambda in addition or instead of. On Wed, Apr 12, 2017 at 4:48 PM Musall, Maik wrote: > Hi, > > when filtering a list of objects by expression.filterObjects( list ), is > there a way for the expression to access regular methods instead of Cayenne > db properties? > >

in-memory filter by Expression accessing regular methods

2017-04-12 Thread Musall, Maik
Hi, when filtering a list of objects by expression.filterObjects( list ), is there a way for the expression to access regular methods instead of Cayenne db properties? Use Case: I have a class A that has several relationships to class B, and it depends on a number of factors which is relevant