From: <ant...@he...> - 2005-12-22 12:38:44
|
I noticed that most of our SPOPS configurations look pretty much the same (or follow the same pattern). It would be nice to be able to set some default values or generation rules for all of the SPOPS classes in one project - at least our spops configuration entries could in most cases drop from the current: [my_object] class = OpenInteract2::MyObject field_discover = yes id_field = my_object_id increment_field = yes is_secure = no no_insert = my_object_id no_update = my_object_id base_table = my_object to: [my_object] class = OpenInteract2::MyObject The easiest way to do this would be to modify OI2::Setup::ReadSPOPSConfig but currently there is no way to extend or replace that piece of code. This reminds me of the problems with ActionResolvers, since the problem stems from the discovery of "all applicable factories". To me it seems that using an automatic find mechanism to determine which classes should be used for setup / action resolving is causing problems and I propose that the find mechanism would be replaced with a list of modules in a configuration file (probably server.ini). This way one could replace ReadSPOPSConfig with a custom one so that it would still qualify for other tasks that depend on 'read spops config'. Even if there would be a way to make this SPOPS default configuration using some global configuration file and specialized syntax for generation rules (which I'm sure there would), I think it is very important that changes like these are made possible. - Antti |