blob: 74c0061e330cb19044323eebbdab0fa3eb65ee0d [file] [log] [blame]
Manuel L. Santillana5ebc702006-09-27 22:59:34 +00001WITH ECLIPSE
2If you are using eclipse:
31. Init a workspace to be maven-compatible (see maven site)
42. Run maven eclipse:eclipse to create the .project file
5FOR ALL
63. Run maven install to add jmood to your M2_REPO
7or just mvn package to generate the bundle in target/
84. To test it you can just run the FelixLauncher class under
9src/test/java. This creates a temporary './cache' directory for Felix.
10Note that no shell is available so you can only interact with felix
11remotely through JMood
125. Connect to JMood using your favorite general purpose JMX console
13(for example, jconsole, bundled with java 5) or help us building one ;-)
14The url is printed in the console but it should be:
15-> service:jmx:rmi:///jndi/rmi://${host}:1199/server
16where ${host}=your_hostname or 'localhost' if no non-loopback interface is found.
17
18ISSUES
19- If you are using java1.4 the framework won't find the javax.management and
20javax.management.remote packages so it will not resolve JMood. You can choose between Sun's reference
21or mx4j (http://mx4j.sourceforge.net) implementations. Just bundle them and export those
22two packages and everything should work fine.
23- If running on Java 5+, JMood uses the java.lang.management PlatformMBeanServer
24else (java.version<1.5.0) it creates an independent MBeanServer and
25JVM MBeans are not available any more.
26- MBeans for some compendium services are created if those services are available
27but no static dependency is needed.
28- JMood creates an RMIRegistry on port 1199, this value is hard-coded for the moment, so be sure it is free
29- JMood automatically creates a policy manager with a dummy policy if none found. Note that it has not been
30very much tested with *real* security, and that many management operations need AdminPermission to work fine.
31