Is Annotated POJO a POJO ?

[karldmoore]

This means no annotations, not even my beloved @Configurable

Just going back to an earlier discussion, if we haven't got @Configurable what's the alternative approach? How to we achieve the same thing in a POJO way?

[debasishg]

Just going back to an earlier discussion, if we haven't got @Configurable what's the alternative approach? How to we achieve the same thing in a POJO way?

Karl -

I think you can subclass the abstract Spring aspect AbstractBeanConfigurerAspect. Using this, u you can write an aspect to configure all instances of objects defined in the domain model using prototypical bean definitions that match the fully-qualified class names. Please have a look at section 6.8.2 in Spring 2.0.4 docs. Last year I had blogged about this .. have a look at the comments where I discuss this.

Of course this is only valid if u consider adding aspects to a POJO as NOT violating its POJO behavior.

Cheers.
- Debasish

[karldmoore]

Of course this is only valid if u consider adding aspects to a POJO as NOT violating its POJO behavior.

Thanks for that, I'll check out your blog. After the whole dependency debate, I just thought it was interesting to know what the alternative is to @Configurable. I would have thought this is a pretty important feature. People want rich domain models made up of POJOs but don't want to be tied to Spring! If we are dealing with aspects then we don't have to modify the POJOs, sounds like it fits the bill.

This presentation also had some examples of this.
http://www.bejug.org/confluenceBeJUG...omments= true

[karldmoore]

Saw this and though it was interesting.
http://jroller.com/page/eu?entry=damned_guice

[schumnana]

I posted the new feature http://jira.springframework.org/browse/SPR-4602.