Let's say you have application.cs which is your PARENT_BEAN_FACTORY. You have 10 other users hitting the site, they are in the middle of a request to index.cfm which is using an already-initialized Model-Glue and they are happily processing requests.
Now, I start the process of ?reinit=true which in my OnRequestStart, first calls onApplicationStart() (or just recreates application.cs) and then subsequently re-initializes Model Glue. But, the nanosecond application.cs is reassigned, the other 10 users with in-progress requests piped through Model-Glue to the service layer begin acting crazy because, as you correctly point out, the beanfactory to which MG has a reference no longer exists. We need some way of locking model-glue from performing a request while we recreate the bean factory and assign it. Brian On Monday, November 5, 2012 4:45:46 PM UTC-8, Dan Wilson - [email protected] wrote: > > Isn't that because the bean factory is, in essence, gone? > > While we have a feature intended to not reload the bean factory, and just > reload MG Configs, I do not believe we have a feature to make the bean > factory disappear in the middle of a request. Isn't this what you are > doing? > > In short, I think what you may need to try, is reload your parent bean > factory, then reload MG through the built in mechanism provided. It is > locked and handles the reloading in a specific order. > > If I'm not understanding correctly,maybe try explaining again. > -- Model-Glue Sites: Home Page: http://www.model-glue.com Documentation: http://docs.model-glue.com Bug Tracker: http://bugs.model-glue.com Blog: http://www.model-glue.com/blog You received this message because you are subscribed to the Google Groups "model-glue" 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/model-glue?hl=en
