/thread/14630 [original link is broken]I find this very interesting. Hope as a result of this we would get a possibility of composing enterprise services according to our needs. With standard EJB model we have it prepacked: transactions, security, threading, persistency. Latest trends in the Java community show that people prefer to separate this stuff with a number of techniques, AOP being not the latest. I'm really looking forward at what would emerge from this. Hope that such an effort would bring us closer to declarative middleware. What do I mean by declarative middleware? For example you have a POJO(Plain Old Java Object). You need to add transaction support to one of the methods, which does something with the database. One of the tricks to achieve this is to use annotations and/or AOP(Aspect Oriented Programming). Or you can go forward with Decorator design pattern, doing transaction management manually. Or you can choose a 'standard' approach with session beans. So, may be we'll see POJO persistency in the declarative form soon, who knows? 🙂
