While I'm closely tracking the discussions, reviews and talkings on the next generation EJB architechture (and really glad to see the officially acceptance of POJOs and DIs/IOCs by major vendors), I do agree with Dion on the concerns he has.
Really why should they see the backward compatibility as mandatory while they're going to go for simplicity by changing the whole model and architechture? A trick to keep the current vendors still as the main players without allowing any new comers to expose what they have for EJB 3.0 only ?
Look at Spring ... I'm sure there will be many guys out there, want to drive their projects by EJB 3.0 only. No need to have application servers to support all those nasty and foolish 1.x/2.x classes, interfaces and architechture, to call them EJB 3.0 compliant :-( I wish this can be changed in the final version!
Armond
Posted by armond at May 8, 2004 04:59 PM