One thing about Spring 2.0, and this was mentioned when they were talking about exactly that (anemic domain objects). Spring 2 has much greater support for AspectJ, so they can do compile time weaving. There's far less overhead there, and makes more sense when dealing with transient objects

On Mar 5, 2006, at 8:22 PM, Kurt Wiersma wrote:

On 3/5/06, Sean Corfield <[EMAIL PROTECTED]> wrote:
The other roadblock I've hit is also somewhat philosophical: I really
want to apply AOP to Reactor record objects - but those are stateful
and are created on the fly during each request. AOP feels too
heavyweight for that scenario. I know ColdSpring isn't really designed
for managing transient stateful objects like that...

On the java side I think in Spring 2.0 they have setup Spring so that can be used with AOP to provide these types of functions for model objects. I believe the goal was to help with the anemic domain model problem. It is probably something I read more about to see if there is anything worth applying to ColdSpring.

--Kurt
 


Reply via email to