Hi Chris This is not a reactor problem at all - most times we use this method it has nothing to do with reactor. Furthermore we have two levels of initialisation that can be triggered via the URL, one for Mach-II and ColdSpring and a second for those two + Reactor files. Both are 'go make a coffee' slow. Reactor *is* in production mode.
I too hope someone at Adobe finds a way to reduce createObject()'s exec time - it is increasingly becoming a workflow nightmare. I agree that messing with the core files is a bad idea and I am prepared to roll my changes out at short notice. There is no way we are going to be making our application dependent on this stuff. But I still maintain it would be great to have the ability to refresh a bean at a time. Look forward to the productivity enhancements. Mark -- Mark Stanton Gruden Pty Ltd http://www.gruden.com
