PAX Exam to write integration tests when developing applications using Karaf. Starting with Karaf 3.0 we've also included a component briding between Karaf and Pax Exam making it easier to write integration Exception { assertTrue(true); } } COMMANDS Basically the Pax Exam - Karaf bridge introduced with 3.0 should support all commands you know from Pax Exam 2.x. In addition we've added various additional

repository/org/apache/servicemix/bundles/ org.apache.servicemix.bundles.cglib/3.0_1/org.apache.servicemix.bundles.cglib-3.0_1.jar 35859 2013-12-06 10:52 repository/org/springframework/osgi/spring-osgi-io/1 │ true │ false │ 1 zabbix/zabbix-java-gateway │ Zabbix Java Gateway │ true │ false │ 13 jetty It’s not always easy to use a JMX client with the RMI protocol. Some monitoring tools (Nagios, Zabbix, …) are not native JMX clients. But most of them can use HTTP. More over, you may want to write

multicast and tcp-ip enabled in the same time. In Hazelcast 3.3.x (the version currently used by Cellar 3.0.x), only one discover mechanism can be enabled at a time. Cellar uses multicast by default (tcp-ip tcp-ip by default. Due to a change in Hazelcast, it’s no more possible to have both. Now, in Cellar 3.0.x, the default configuration is multicast enabled, tcp-ip disabled. See Core Configuration section xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/ javaee/web-app_3_0.xsd" version="3.0"> hazelcast-filter com.hazelcast.web.WebFilter

multicast and tcp-ip enabled in the same time. In Hazelcast 3.3.x (the version currently used by Cellar 3.0.x), only one discover mechanism can be enabled at a time. Cellar uses multicast by default (tcp-ip tcp-ip by default. Due to a change in Hazelcast, it’s no more possible to have both. Now, in Cellar 3.0.x, the default configuration is multicast enabled, tcp-ip disabled. See [Core Configuration|hazelcast]