.NET Framework 3.0: Indigo issues
The first two versions of Enterprise JavaBeans had a crucial problem: "enterprise" objects had a life-cycle different than that of "plain old Java objects." Types were loaded differently, instantiated differently, and the rules for them going away were different. The justification boils down to "things are different over the network …
more ...