LMS released

Javalinux.it team (me and Stefano infact) is proud to announce the
first release of Lms.
What is Lms? Lms is an acronym for Logging Meta Service; Lms’ goal and
use are very similar to the axis’ tcp monitor ones: it logs any tcp communication
and gives developers the opportunity to review any request-response
communications.
Lms is a JBoss deployable application (an ear) and have a jmx mbean as application core and a seam user interface to make its use easy.
In the user interface you have to bind a symbolic name to a real http
address (in most cases a ws endpoint address):

LMS binding

You can start/stop the logging functionality (in stopped logging mode Lms acts just like a proxy), delete the binding, clean all
communication logs. After that, you should use the binding you’ve just defined: as a matter of fact Lms creates a virtual address given by your application server host & port followed by /Lms/servlet/auth/log/ and the name you choose for your binding.

LMS usage

Selecting a binding you will see all the logged communications:

LMS Communications list

Finally clicking on Show you’ll see request/response logged in this communication:

LMS Show functionality

It’ s very simple but very very useful for debugging, as you can figure
out if you are a developer. If you like it or you are simply curious and want to give it a try, download it here.
To install it proceed as follows:

• add policy named no-auth to your login-config.xml: <application-policy name = "no-auth">
<authentication>
<login-module code = "org.jboss.security.ClientLoginModule"
flag = "required">
</login-module>
</authentication>
</application-policy>
• deploy Lms.ear
• make sure your binding target addresses can by reached from your host

Finally, if you want to take a look at the code download it here.