| Possible idea for a solution if you don't want to modify your existing working code and if having a separate app instance for auto cleanup is feasible:
- Add a "isAutoCleanupInstance" property that if true, results in the EOModel being dynamically modified on startup to remove the EOModel qualifier - If the property is true, a timer for periodically running the auto cleanup task is established at startup - If the property is true, only SysAdmin can log in to this auto cleanup instance (prevent accidental login by normal users and them seeing invisible EOs) - Create a new AutoCleanup Application in WOMonitor that points to the same app executable - Set the isAutoCleanupInstance property to true in the WOMonitor config for the AutoCleanup application
YMMV, Kieran On Apr 10, 2013, at 8:39 AM, George Domurot < email@hidden> wrote: I've never used an entity based qualifier (I didn't even know that was possible).
Try using EOUtilities.objectWithPrimaryKeyValue with the entity name and primary key. If that doesn't work, then I'd assume your crafty entity level qualifier is overriding all fetching.
-G
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
|