Hi,

I have information stored in an entity's userInfo dictionary used to
categorise the entity.  What I would like to do is provide access to that
information from a subclass of EOEntityClassDescription (as the docs
suggest) and provide this subclass in a framework (among other things).
This extra entity information is to be used in a number of places -
different apps/frameworks and in places within EOF where all you have access
to is an entity name.  EOF provides an efficient way of handling class
descriptions (they are cached) and a convenient way to get one from an
entity name (EOClassDescription's static/class method).

The other reason for providing access to the extra entity info in this way
is that it hides the details of how the information is stored - the info may
need to be stored elsewhere, or in a different format, and each app that
uses this framework/eomodel wouldn't have to change the it accesses the
info.

(here's the problem!)

EOF's default way of providing needed EOClassDescriptions is through a
notification (EOClassDescriptionNeeded...) that the EOModel responds to - it
creates and registers an EOEntityClassDescription.  How can I get the
EOModel to create and register my subclass rather than the standard
EOEntityClassDescription class?

Thanks,

Richard

Reply via email to