MMBase: Is this right?

Hi,

Recently I've been asked to write an add-on for a content management system called MMBase (http://www.mmbase.org). After I read through their API documentation (http://www.mmbase.org/api/1.4/) to try and understand the product I was left with a strange feeling. Either I need to learn more about OOP than I thought or the guys who wrote this were on crack when they did so...

If you find the time, please check the API documentation (you need to spend just a few minutes) and tell me if you think I'm wrong when I say it is dead-wrong OOP, bad architecture with respect to design patterns and is a nightmare to maintain. I feel that writing stuff on top of MMBase is a waste of time. However, I'm just one person with an opinion. What I'm after here is fellow Java developers who can tell me whether or not MMBase is indeed bad Java/OOP...

Realizing a lot of you are professionals, I'm very greatful to anyone spending a few minutes of their valuable time in checking this out and letting me know what they think. And thanks for reading this.

[1076 byte] By [hdevaana] at [2007-9-28 4:04:22]
# 1

It does seem kinda weird. Much of their naming is pretty awkward (why name all you interfaces XxxInterface instead of just Xxx?), and the architecture is pretty vague to say the least. Of course, not all information can be stored in JavaDoc...

I have a feeling much of the code was developed before Design Patterns became common, in fact, some code probably dates back to JDK 1.0.2, as they have implemented their own CompareInterface (== Comparator) and Sortable (== Comparable).

hhora at 2007-7-7 23:36:20 > top of Java-index,Other Topics,Patterns & OO Design...