I have a question for the class. To caveat this.. I can't share code or anything specific so please don't ask. I have a strange situation w/ a FW/1 app. The app, even in production, needs to have reload on every request enabled. If not, strange errors happen all over the place. I have some ideas as to what I am looking for to fix this. But was wondering if anyone else has ran into something like this and what they may have discovered was their fix.

sounds like you've got one or more beans (or services, etc.) in the wrong scope. which is to say if you have a service that handles or direct-references session scope (bad practice) and it's being treated as a singleton and is therefore actually in the application scope

yea... I was thinking this as well. Just trying to track it down is a challenge when the errors are inconsistent at best.

what kind of behavior are you seeing

random errors of things claiming they don't exist but clearly do

not much to go on. i'd check to ensure you're not using any properties for state in any singletons

yea sorry... I have to be intentionally vague. But thanks for the ideas on where to look.

I had some issues a long time ago with a multi-tenant FW/1 app because I wasn't using appropriate application names and that ended up polluting websites with improper objects

Think I found the issue... just not sure how to solve yet. The system is using a loadlistener for diconfig . If the app is not reloaded the config is not being persisted and appears that most of the config is not present on subsequent loads. I haven't used a loadlistener in a while but I don't think this was implemented properly.