I wrote earlier on Adaptive Object Model Architectural Style hypothesizing that Aspect Oriented Programming (AOP) should be applied to them instead of Plain Old Java Objects (POJOs).

James Strachan chimes in and has some comments about it:

Typically data comes from databases or remote services which requires runtime marshalling and typechecking anyways - so much of the compile-time benefits of using typesafe objects are often moot. It can often simplify development, particularly of front ends, to keep the data seperate from the business logic and use something like DynaBeans as an AOM style API to your data.

 I thought nobody was reading my stuff!

Then, Lo and Behold! Rickard delivers the proof again:

Just a little note: coincidentally AOP and RDF work very well together. Both are about attaching stuff to object identifiers. In the case of AOP it's about attaching code, and in the case of RDF it's about attaching data. I.e. the perfect way to store AOP objects is as RDF tuples, where each namespace represents an AOP "extension"(Java interface).