When we do a step back and view at the "ugly" things then we should also look at other frameworks how they handle them. MMBase is a persistency layer with additional services and features. Hibernate, EJB3 and jsr-170 have some concepts which might be appliable to MMBase. For example, Hibernate makes a clear distinction between POJO's and RowSets. A POJO is our MMObjectNode and the ClusterNode matches more or less with a RowSet. We also could make that distinction instead of inheritance?
After using Hibernate,prevayler and spring for different projects I learned to enjoy the ease of development and testing with such products. While I know MMBase very whell I choosed to use those products for serious development. The main reason was that I really needed to be able to get performance out of my application that does stuff like saving scores. MMBase just lacked the ability to do this efficiently. I know that a tool like hibernate uses transactions and is used in enterprise level applications an I know that the features provided by those exceed my needs. It never felt right to extend Builder to add functionality. That never worked good enough for my needs. The real problem IMHO is that it's not easy to program against MMBase using java. My solution is well known. I just write a lot of jsp/taglib code and that just works , it doesn't need the compile/deploy cycle and develops quite fast. and if you are creating website at least You know where to find the code. While it's a solution , to me it's telling me that MMBase is great product for fast/ad-hoc development(If you already know MMBase that is) but You need to compare it to other emerging technology like the Rails framework or just for that matter good old php/MysqlAdmin. I totally agree with nico about the session stuff and vague concepts. I also agree with Michiel he is trying to make MMBase "perfect / better", tha'ts nice but I don't think that's what will help MMBase to grow or be used in different way's. Still it's good/great work and you can't build a framework on top of a rotten core. Michiels proposals are very important but are not concentrating on what the developer want or what the user want :) IOW , I still use MMBase for website work (mm:images,the generic editors and the way MMBase does relations are the main resons). A nice addition would be a framework that support the Strong points of MMBase (no compile/deploy cycle). so more scripting, and simple MVC framework where all components can be scripted. I should be fun and we should be able to do AJAX and such stuff in a breeze or am I missing the point? _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
