This post originated from an RSS feed registered with Java Buzz
by Marc Logemann.
Original Post: I love standards: Toplink and Enhanced CMP
Feed Title: Marc's Java Blog
Feed URL: http://www.logemann.org/day/index_java.xml
Feed Description: Java related topics for all major areas. So you will see J2ME, J2SE and J2EE issues here.
Perhaps TSS needed some page impression boost, so they decided to put another object persistence thread on the page. This time in form of an interview with some Oracle/Toplink guys. The interview was quite boring, but the postings to it were funny, after Robin Roos usual "use JDO or die" statement we had someone using Toplinks enhanced CMP solution (the fact that there is an enhanced CMP solution available shows the state of current EJB specs IMO). He pointed out some problems with it and one Toplink guy responded:
--- snipp ---
Glad you are liking the value that TopLink adds to CMP. Our CMP for WLS product makes use of an interface between the Container and the CMP Bean Manager. While this works really well, that interface is not standardized and WLS can change it whenever they want. This is just a reality of writing on top of 3rd party software. Of course this annoyance doesn't exist when we are integrated with the OC4J Container, so I would recommend using OC4J to be rid of this problem forever :-)
--- snipp ---
This is so crazy, people using J2EE because its a standard platform, they use CMP because its standard. Then they chose an enhanced and proprietary CMP solution because it seems that "normal" CMP sucks, then they are unhappy because its not standard anymore and things can be broken in future releases, but then the Toplink guy jumps in to say that the best thing is to use the Oracle Container.
What in gods name have all this to do with J2EE or standards? Nothing. And you cant blame the customer for using such solutions, because CMP cant handle it. So what to do? Ask Robin, he knows the answer ;-)
Previous Topic
