Hi everybody, I've been using my own EOJDBCPostgresqlCustomPrototypes for quite some time. I add a few prototypes of my own and I override some definitions from EOJDBCPostgresqlPrototypes. From day one I've lived with warnings like this one:
"MCSaaS/MCAbstractPerson/dateLastLogin references a prototype attribute named dateTime that does not exist in EOJDBCPostgresqlCustomPrototypes" Despite the warnings, everything works as expected, i.e. the prototype attribute is taken from EOJDBCPostgresqlPrototypes instead. Now, to make the warnings go away, I tried copying all attributes from EOJDBCPostgresqlPrototypes to EOJDBCPostgresqlCustomPrototypes, skipping the ones that I do actually override. While everything's nice and quiet (and all tests still pass), I feel this is not what I really want: * if a bug gets fixed in EOJDBCPostgresqlPrototypes (which does seem unlikely), I'll have to do something to benefit * it's much harder to understand which prototype definition I actually do override (currently 3 out of 40) So, is my use of custom prototypes different from what others do? Do you ignore the warnings? Do you copy everything from the Wonder set? Fabian _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
