I dont think we can talk about a standalone mode, more of an check that MMBase will not be started by calling the MMCICould as well make that implicit when using the 'mmbase.config' property, because using it implies that you're problably trying to run mmbase outside a servlet environment.
Hwat about appservers which don't unwar the WAR-file. The mmbase config
has to be on the file system. A -Dmmbase.config can fix this. It will
definitienly go wrong when Mmbase thinks it is running standalone.
If you would not load any servlets, and you try to access MMBase from within the jsp you will get the message: "mmbase has not been started, and cannot be started by this class". (could even be reported as an bug)
If you still want to start MMBase you can put the do the following call previously: org.mmbase.module.core.MMBase.getMMBase(); (assumed that the mmbase.config is configured allright). This is also done in the servlets to get the system running. There is an check in the CloudContext which checks if MMBase is already running, and if not it will produce the error. I would like to see this changed in such a way that it will use start MMBase when it is not running.
-- Time is on my side,....
Eduard Witteveen +316 414 789 23
