For a bean developer
The next specification for Enterprise Java Beans
is now available, albeit an early draft. Though its objective is to simplify
EJB model from a bean developer perspective, it has only managed to be
implicit in its intricacies and requirements.
Enterprise business processes are complex by their definition. Software development is a complicated and trying exercise. With this knowledge, I am always suspicious of simplification by abstraction. This always leads to new developers not having a clue why certain things are done they are. This how the EJB developer community got into trouble, by not knowing the underlying principles informing the EJB model. With this new level of abstraction (my bad: simplification), a new crop of developers will enter the market without a clear understanding of objects remote/local and ensuing best practices.
