Accessing spring services from hibernated domain objects

[jasonab]

Indeed, the overhead for this functionality is pretty low. The cost of the reflective invocation to inject dependencies is near zero now and the actual process of intercepting the creation of a new domain object is very quick due to the AspectJ weaving process.

Apologies for resurrecting a dead thread, but I was wondering if this was still the case now that Spring 2 is in production? I can't find any actual numbers or testimony on this topic.

jason

[karldmoore]

Its a fair question to back up the statement with numbers. In the absence of an answer, you could write some simple tests and prove it. Obviously it would be nice to see those results as well .

There are some general performance stats here. These are a little old though.
http://docs.codehaus.org/display/AW/AOP+Benchmark

[cepage]

I saw several complaints about poor performance using load-time weaving when Spring 2 was released. I don't know how much progress has been made in the subsequent point releases.

I use compile-time weaving. I don't have the hard numbers in front of me, but it has been nice and speedy for me.

[debasishg]

I have also been using @Configuable with compile time weaving without any performance complaint. Initially we had some problems with LTW, but since we switched to compile time weaving, things work out like a charm. The only problem, not related to performance though, is that the dependencies do not get re-injected upon deserialization (if u have such a use case). This is an issue recorded in Spring JIRA and for which Ramnivas has also provided a fix. The fix, will however be 100% fullproof when the next release of AspectJ comes up. But with the current patch, things work out pretty well.

Cheers.
- Debasish