Lms is an acronym for Logging Meta Service
; its goal and use are very similar to the Axis' TCP monitor's goals: it logs any TCP communication and gives developers the opportunity to review any request.
Just as Axis' TCP monitor is, Lms is particularly useful in debugging SOAP communication operating like a transparent proxy and logging any HTTP traffic (header and body). The most important Lms added value is that it is a web application accessible from all developer team members using a common browser; moreover, Lms hasn't Axis' limitation of requiring an AWT-compatible environment.
Lms is a JBoss-deployable application (an EAR) and has a jmx mbean as application core and a Seam user interface to make its use easier. In the user interface you have to bind a symbolic name to a real HTTP address (in most cases a ws endpoint address). You can start/stop the logging functionality (in stopped logging mode Lms acts just like a proxy), delete the binding, clean all communication logs.
See the original blog post describing the idea:
And here you can download it from Sourceforge: