I found it somewhat ironic that the same day I posted my blog somewhat blasting Oracle’s J2EE offerings, TheServerSide posted an announcement that Oracle has released a new demo application called “Toy Store”. There were quite a few very critical and insightful comments made by developers, and it seems that I am not alone in my frustration with Oracle’s Toolset!
My own critique of the “Toy Store” would follow a few of the other comments posted:
Code Generation is excessively abused! See my previous blog why code templating should be used instead of code generation.
XML is not code. The argument that XML is used to CONFIGURE the code is pretty ridiculous if it takes you just as much XML as Java to configure the Java. This tells me that there is a severe design flaw in the application. How is it possible to even refactor the application, when you are so tightly bound to these configuration files? Why not look into something much more elegant like AOP?
Oracle’s documentation and communication is absolutely horrible. Seems like the comment that open sourcing Java would lead to bad documentationis absolutely moot when you have terrible documentation comming from a commercial company. Has anyone out there tried to use their OTN!?!
It appears that there is one sole personchampioning knowledge of how the Oracle Tool Suite is intended to work. Maybe this is because Oracle’s own documentation is so poor that no one else has figured it out yet (including their own consultants).