Project: talendesb
Issue TESB-2359: Make jmx samples work and align it with the other samples
As a user I want to be able to sucessfully execute the jmx samples. When I was trying to execute the jmx samples according to the readme I encountered a lot of problems. See below for the problems I found *GENERAL* - Endpoint in SimpleClient is wrong. Defined is http://localhost:8080/services/simpleService, but in reality the service has the endpoint http://localhost:8080/simpleService/simpleService - In the war file below WEB-INF/classes there are again directories classes, META-INF, and WEB-INF. They shuld be removed. - The jmx sample should be splitted in one cxf sample and in one camel sample, both located directly under examples/talend/tesb with two different readme that describe how to build and run them. *README* - In general all steps should be described for Windows and Unix - Building the simple-service-war -- Instead of suggesting to add the CATALINA_OPTS property in some Tomcat start script (which one?) it should be described how to define it in the shell (Windows and Unix). The user should not be forced to change his Tomcat configuration. -- step 2: war file is not found in target, but simple-service-war/target -- step 4: you first have to change in directory simple-service-bundle before executing mvn exec:java -- step 4: you should configure the exec plugin with the main class in pom.xml, so user does not have to specify it explicitly. - Using jconsole to find MBean Attributes -- step 2: service:jmx:rmi:///jndi/rmi://localhost:6969/jmxrmi does not work Here I stopped trying out the samples. *Expectations* - Make sure the readme is up to date and complete, so anyone is able to run the samples. - The readme must equally well describe the Windows case and the Linux / Mac OS X case. - Split the cxf/jmx and the camel/jmx in two separate saples located directly under the examples directory. - For the cxf sample use the usual pattern for components in other samples (common, client, service, war) _Acceptance criteria_: PO is able to execute the demos following the instructions in the readme.
Story points: 3