Hi Markus, Personally I prefer keeping rules in a single file. If you do use multiple rule files, make sure you use a model group file to allow easy searching over all files.
Maybe you could split the EOModel into different parts, given its size. Then you could maintain a rule file per model. You could also override additionalModelNames() in ERD2WModel to get all entities and assume there's a rule file for each – which may not really be needed. Fabian > Am 26.11.2015 um 11:17 schrieb Markus Ruggiero <[email protected]>: > > Hi list, > > A D2W app usually has the 2 rule files user.d2wmodel and d2w.d2wmodel. A > wonder property allows to add more rule files > (er.directtoweb.ERD2WModel.additionalModelNames). Up to now I have all my > rules in those 2 default files. I am thinking about having one rule file per > entity name. This works but is a nuisance because I have to maintain the > value for this property. We currently have about 50 entities, thus 50 rule > files, and therefore a rather large property value. During ongoing > development new entities will be needed, others will go away. How are you > folks handling this? All rules in one file? Separate files? How many? How to > decide what to put where? And how to maintain the contents of the > additionalModelNames property? > > Thanks for any hints. > > ---markus--- > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/lists.fabian%40e-lumo.com > > This email sent to [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
