Re: valueForBinding and indirectly referenced types

Thanks Mike, that was it. I'm curious as to why I don't get any build or runtime errors with synchronising components when these jars aren't exported, but once valueForBinding is introduced to the component it explodes. Is it possible there was always a potential for runtime issues but I ha

Re: D2W Available Entities Drop-down

On 2009-10-03, at 10:41 AM, Ray Kiddy wrote: On Oct 2, 2009, at 10:26 AM, David LeBer wrote: On 2009-10-02, at 1:01 PM, Don Lindsay wrote: Thank you David. You're welcome Don. I added this to the D2W rule cookbook page

Re: Searching Question

Hi Don, It might be worth your time to look into using Lucene for this, and using the ERIndexing framework a search returns EOs. The query syntax is very flexible and a range search like you are describing could just be the the start: http://lucene.apache.org/java/2_3_2/queryparsersyntax.

Re: D2W Available Entities Drop-down

On Oct 2, 2009, at 10:26 AM, David LeBer wrote: On 2009-10-02, at 1:01 PM, Don Lindsay wrote: Thank you David. You're welcome Don. I added this to the D2W rule cookbook page Is any of this inform

Re: valueForBinding and indirectly referenced types

This error means the class you are referencing refers to some other class in one of its method signatures (or inheritance tree) that your calling class can't find. This usually means you didn't export a jar file from the framework the referenced class is in. Go to the framework that contain

valueForBinding and indirectly referenced types

I'm trying to change an existing component to be non-synchronising. The component imports classes from my framework that extend classes from jar files that are included in my frameworks class path. My component only accesses methods from these subclasses. When I cast the result of valueFor