Terracotta Discussion Forums

I'm using Terracotta 3.1.0 and Spring 2.5.6; and I was wondering how I should go about sharing Objects that have been advised with Spring AOP.

The way the proxy class was generated, I had no choice but to instrument the JdkDynamicProxy(sp?). But under it, I had made the advised field transient; that is until one of my shared Objects needed it after the Application Client was restarted...

I haven't seen any TIMs for it, and google searches haven't been helping much. Any advice?

We have nothing for this at the moment. Can you tell us what problems you are having?

I would have though that AOP is creating dynamic proxies but eventually POJO getters and setters are being called and everything works at least on the JVM that created the object. SO, is the problem when an object moves to a JVM that didn't create it and the proxy is no longer wrapping it? Total guess.

--Ari

Well, the only real problem so far is that I didn't want to have to go in and instrument Spring Framework and Spring AOP by hand. Looking into this further, it seems as though our AspectJ Advised classes are doing just fine.

But we're also using Spring Integration and their Gateway constructs; which basically create proxies around an interface to make sending Messages easier.

When I originally went down the route of trying to instrument Spring Integration and Spring AOP by hand; it got to the point where I was attempting to share absolutely everything, since the "advised" field references Classloaders and the BeanFactory.

So, I'm trying to figure out the best way to set this up without sharing every object in my Application.

Thinking about it now, I'm wondering if it would be best to not share the Gateways....