[coldspring-dev] Refreshing beans

Thu, 01 Mar 2007 05:32:50 -0800

You guys are not going to like this answer, but... 

I totally do not agree with this approach. For one thing, Tom, why would you need to bounce the server? You should be able to just reinit your app. Unless you are working off of a production system, and I don't see why you would do this. When Mark brought this up before I realized that he was looking for a ColdSpring solution to a Reactor issue, not actually a ColdSpring issue. You change a bean managed by ColdSpring, and I understand you want to reload it, but the reason really is you do not want to wait for Reactor to regenerate everything. I think that for Mark's issue, you should be looking at keeping your Reactor in a production setting when you are not messing with domain objects. I have done this in the past on a very large project and saw considerable drops in reload time. Like from I am getting a coffee and pissed to, oh, I can work with this! For now, we are all having to come to grips with the fact that more and more OO frameworks are coming together, which means more and more CFC creation, and the truth of the matter is, CFC creation is slow. Hopefully Adobe is looking at that for a future release, who knows, but for now, we are stuck with it, and I just don't fully think that ColdSpring is responsible for solving it. Question, Tom, what other frameworks are you using? Maybe there are other ways to skin this cat.

I don't mean this in a harsh way, but messing with ColdSpring core files is a really bad idea. I have stuff to be committed that you have just written yourself out of, and believe me we are talking serious productivity enhancements. 

C 



On Mar 1, 2007, at 6:32 AM, Mark Stanton wrote:

Hi Tom

I agree. I have found a way, but it meant hacking a new method into
the framework which I realise is bad karma - see my post at

Cheers

Mark
-- 
Mark Stanton
Gruden Pty Ltd


Reply via email to