Re: [JavaEOGenerator] Bug when generating fetchSpecification methods

A class property is by definition visible, so if you have not marked it as visible no method returning a property will see it. An Attribute or a Relationship may be non-visible but an therefore not a property. EOEntity.anyRelationshipNamed or EOEntity.AnyAttribteNamed will return attributes

Re: [JavaEOGenerator] Bug when generating fetchSpecification methods

Hi Art, Thanks for your reply. "Non visible attribute" -> An attribute(database column) included in the eomodel, but not marked as a class property. I have already tested EOEntity._propertyForPath(), and it returns null for attributes not marked as class property. Cheers, Bueno On Dec

Re: [JavaEOGenerator] Bug when generating fetchSpecification methods

On Dec 20, 2007, at 11:43 AM, Oswaldo Bueno wrote: I'm using JavaEOGenerator to auto-generate my entity classes. When it generates methods to access EOFetchSpecifications on the eomodeld, it suppresses bindings associated with a non-vi

[JavaEOGenerator] Bug when generating fetchSpecification methods

Hi, I'm using JavaEOGenerator to auto-generate my entity classes. When it generates methods to access EOFetchSpecifications on the eomodeld, it suppresses bindings associated with a non-visible attribute. Trying to debug I identif