We have an object which is subject to Aop advice and one weird thing we observed on it today..
– All the class level variables were being persisted across instances
Then we realized that it has got something to do with Aop configuration, so we tried making Singleton=false on the advised class, and Spring complained that the configuration cannot be that way.. So I guess we’ll have to live with that impediment..
UPDATE: I have to take it back, the problem was that the context was initialized in a static constructor. We moved it to a function and get a new context everytime; Now the singleton behavior is removed.