Wouter Heijke wrote: > > > At least a Module is an Object, so you only need to recompile... Tut > > mir leit, but what can we do? It's a very minor change, but definitely > > an improvement, IMHO. > > My point is that I need to maintain several versions, and will get > questions about it why this exception is being thrown....
This is valid for about every application on MMBase, I think (in applications and contributations modules). Yes, it would be nice if one can make applications which are binary compatible between MMBase versions. But as long as silly methods as Object getModule are present, and called, in such applications, this is simply not feasible. > While you're at it... take a look at a proper solution to check if MMBase > (and it's applications) was started. The current 'system' and the cause of > my problem is very vague. If you decide tomorrow to change the startup > order MMBase may not be started then the mmadmin module is loaded.... > Perhaps MMBase.getMMBase().getState() if using core or CloudContext#isUp() if using bridge. I think that in 1.8 I have ensured that MMBase.getMMBase always returns the same instance (to eliminate the risque of starting more than one). It's not necessary 'up' already but I felt everything is better than accidentely starting up a second mmbase. I was needing isUp for a similar reason, namely code which was trying to get an mmbase cloud during startup. I'm not quite sure that MMBase.getMMBase makes sense now though. May be you feel like testing if the 1.8 situation is useable for you. Michiel -- Michiel Meeuwissen mihxil' Peperbus 111 MediaPark H'sum [] () +31 (0)35 6772979 nl_NL eo_XX en_US _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
