Hello folks, I have recently participated in discussions on openmeetings management interface. Open of possible options we have discussed was having admin module separated from the code base. Modularity helps debugging things and shipping releases. Also being modular helps others to re-use our code, and re-usability if one of our competitive advantages. BTW, that's why I support our client code to be in a separate module - people want having their client UIs customized.
Java has a special API for managing applications [1]. It basically provides the ability of changing internal state of the application (flags, parameters, etc) with minimal UI beautification. While there is no requirement to use this interface, at least it worth taking a look. This allows using standard jconsole or other HTTP-based consoles to manage an applications. Which questions help understanding if some functionality worth a separate module? * Does this module have a different customer base? (May be true for whiteboard, and the server code with client code excluded.) * Is the module big enough? (True for both client and server modules.) * Are changes to this module independent from openmeetings changes? (True for whiteboard, webstart client, admin console UI.) I wonder if it is possible to build independent modules in wicket. [1] http://en.wikipedia.org/wiki/Java_Management_Extensions -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095
