Well put. Also, the containers (Orion, JBoss) deliver functionality to Sun's spec (J2EE, EJB) that has components and a meta model. Many people subset now, having had pain with entity beans. That proves two things - 1) things evolve, 2) huge design up front does not always work. Both related I guess.
The containers also have internal component lacing for their kernel. It's their proporatary design. People will always design another, and avoid a defacto standard if they think it is best for their mission. Meta-mission people are not even going to complete this quest in the first strike. EOB deliberately avoids meta info, but then it is a specialized container rather than a general one. - Paul > I still disagree rather strongly with you. Take a look at J2EE. Sun > wrote the specs and the compliance testing framework. They even have > a reference implementation--which I may add they do not recommend for > prime-time. The real J2EE systems are written by third parties like > JBoss, BEA, IBM, etc. > > I don't see how having one super-container is going to help. I doubt > we would be able to come to one vision. The fact that consumers have > to choose between systems with largely overlapping functionality in > J2EE systems proves that consumers are intelligent enough to find out > what their needs are. What we need to do is provide enough information > to help the consumer make their decision. > __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
