Marco,
As you might expect I really like POJOs.
This is once of those instances where simple or plain objects are much more powerful than not-so-simple
EJB 1/2. For example, here is some "simple" Java code:
class Person {
String name; List<Person> dependents; ...}
class Employee extends Person { Person Manager; ...}
(slightly contrived example that but...)
Some things to note.
1 I can
test this code without deploying it in an application server or without needing a database. The edit-compile-debug cycle is fast.
2 A developer who familiar with the problem domain but is not an EJB (or other infrastructure framework) can work on this code.
3 When its time to implement database access, its straightforward to do that with Hibernate, JDO or EJB3.
4 I can switch/upgrade infrastructure frameworks without rewriting my code
None of these things are true if I am using a snazier, not so plain technologies such as EJB2.
1. Code tends to be coupled to the application server and/or database, which slows down and complicates testing.
2. EJB2 beans are coupled to the framework requiring developers to have EJB expertise.
3. EJB2 could not easily persist even this simple domain model.
4. Upgrading your code from EJB version N to EJB version N+1 requires changing it.
Just a few reasons why I prefer the power of Plain Object Java Obejcts.
Chris
that (especially the bit about the rapid development-debug cycle) but it's good to hear it from someone like you!
