[symfony-users] Re: Using sfEvent in propel objects. NOT behaviors

2009-07-02 Thread JoeZ
Frank. You've got your point. The whole point of using this event for me is not to care about where is within the app code the invocation of the setDesync(true) method, but to just let it happen wherever it happens, and have some listener to act accordingly. In my understanding, what you say

[symfony-users] Re: Using sfEvent in propel objects. NOT behaviors

2009-07-02 Thread Bernhard Schussek
Hi Joe, On Thu, Jul 2, 2009 at 11:23 PM, JoeZjzar...@gmail.com wrote: So I came out with this (I'm not yet sure it will work. I can tell you it compiles). You should never let your model rely on the context or on the configuration. Further more, you should try to avoid calling Singletons in

[symfony-users] Re: Using sfEvent in propel objects. NOT behaviors

2009-06-26 Thread Frank Stelzer
Hi, Using the sfContext instance in the model layer is a very often discussed topic in the last days. The latest one is this: http://groups.google.com/group/symfony-users/browse_thread/thread/75b9b1df4398b195?hl=en Fetching the context in the model is a very bad practise and you should find