Hi Amedeo, maybe just two examples for usage of the user-info dictionary in an eomodel:
We keep all our database documentation into the user-info, so we have just one place to keep updated. We have an application to create a html-format database documentation with model information extended with the description from the user info dictionary.
Furthermore we keep some handling information for attributes in there. The model allows you to generic handle eo data by going through the list of attributes of an enterprise object and do whatever you like (e.g. copying, de-/serialization). If you want special handling for only some of the defined attributes you can put a flag into the user-info, and dynamically call special methods in case the flag is set.
Regards, Susanne _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
