On 07.09.2010, at 12:59, Navid Mitchell wrote: >> anyway, it was just an example about a general concern i have with >> annotations. for one they need to still enable extending, that being said in >> many cases extending will obviously be limited by whats possible without >> breaking the "is a" relation, in which case its mainly >overwriting a >> previous definition with another value and not necessarily removing or >> adding entirely new things that need to be merged. but just like my routing >> example, there are some things that simply shouldnt be moved into the >> controller or whatever definition. > > I definitely agree that some things are better not included in a class > directly. For example your database configuration data, this > particular data is a requirement but does not necessarily relate to > any specific objects implementation.
Another thing that had me concerned a bit is the tight coupling Doctrine2 proposes to the ORM or ODM. Then again quite a bit of code inside the models will depend on the ORM/ODM query language. regards, Lukas Kahwe Smith [email protected] -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
