Spring.Aop singleton behavior

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.


About vijayvepa

I'm a software consultant for Software Specialists Inc. currently working at Philips Respironics, Pittsburgh

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: