EntityModeler fails to recognize localized attributes in fetch specifications
EntityModeler fails to recognize localized attributes in fetch specifications
- Subject: EntityModeler fails to recognize localized attributes in fetch specifications
- From: Riccardo De Menna <email@hidden>
- Date: Tue, 17 Nov 2009 11:09:52 -0800
Hi,
If I write a Fetch Specification in entity modeler that uses a qualifier with an attribute name that contains an underscore (for instance when using localized attributes) my generated templates end up containing errors.
To be more clear... putting something like "visible = 1 and name_en = $name" in the qualifier field of the fetch specification.
Result: Any entry like ${binding.attributePath.childClassName} in the template fails to be resolved.
${binding.attributePath} alone returns [EORelationshipPath: <invalid>]
Is there a workaround? I'm stuck not being able to use fetch specifications if the argument is localized in the db.
Riccardo De Menna _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden