TopLink Wiki: TopLinkWeaknesses

Line 5 was replaced by line 5

- * TopLink is complex. The API is complicated (one say could it's rich). It's a very powerful product, and it can do almost everything. Seriously. The downside is that it's nearly impossible to understand all that's going on. As a result, when it doesn't do what you expect, you're in for a tough ride. DebugTopLink is sometimes the quickest solution.

+ * TopLink is complex. The API is complicated (one could say it's rich). It's a very powerful product, and it can do almost everything. Seriously. The downside is that it's nearly impossible to understand all that's going on. As a result, when it doesn't do what you expect, you're in for a tough ride. DebugTopLink is sometimes the quickest solution.

Line 7 was replaced by line 7

- * TopLink is proprietary: the source is closed (although see DebugTopLink), and while it complies to some standards (EJB, JDO, etc.) in many ways it is its own beast with its set of idiosyncracies.

+ * TopLink is proprietary: the source is closed (although see TopLinkSourceCode), and while it complies to some standards (EJB, JDO, etc.) in many ways it is its own beast with its set of idiosyncrasies.

Line 9 was replaced by line 9

- * TopLink has some bugs. I'm always surprised when that happens. The product is over 10 years old at this point, has been in the hands of 3 different companies, is an industry standard, yet there is still some basic stuff (or so I thought) that doesn't work. I'm not talking about insane concurrency issues or rare corner cases, just simple stuff that's documented and a regular user expects to work.

+ * TopLink has some bugs. I'm always surprised when that happens. The product is over 10 years old at this point, has been in the hands of 3 different companies, is an industry standard, yet there is still some stuff that doesn't work. I'm not talking about arcane concurrency issues or rare corner cases, just simple stuff that's documented and a regular user expects to work. Maybe I just got unlucky with advanced object models.

Line 11 was replaced by line 11

- * The documentation is/was bad. OracleCorp has significantly improved this, so it's getting there, but for a long time it was just bad. That certainely contributed to the feeling of opacity.

+ * The documentation is/was bad. OracleCorp has significantly improved this, so it's getting there, but for a long time it was just bad. That certainly contributed to the feeling of opacity.