Re: Cotribute Module

Hi Hang,

Thanks for expressing interest to help.

Here is the current state(look below) of what the monitor does and  
what its weakness is. What do you have as plans in terms of  
contributing to this module?

I am ccing Milan, who did the below write-up.

  HTTP Monitor

The current implementation of HTTP Monitor consists of 2 parts :

     * Server part
           o customized default web.xml with filter and filter-mapping  
elements
           o couple of jar files (e.g. the filter implementation,  
schema2beans used to log requests by filter in xml style)

     * Client part
           o Client Servlet deployed on internal Http Server
           o HTTP Monitor UI

The role of the server part is following :

     * Servlet filter, deployed on particular target server  
(GlassFish, Tomcat) is logging requests sent to server,
     * The servlet filter converts request header information +  
request parameters to a specific XML document
     * The XML document, prepared by the filter, is send to IDE Http  
Server (to client monitor servlet) in the form of text/xml message.

The role of the client part is following :

     * the Client Servlet deployed on internal Http Server (it's some  
old version of Tomcat) is responsible for
           o opening the Http Monitor panel
           o filling the Http Monitor panel by request information  
(taken from the XML content of the request)
           o saving the requests to a stack to enable seeing the  
requests history and replaying the requests

HTTP Monitor functionality

     * monitors the HTTP requests sent to particular target server  
(Tomcat, GlassFish)
     * introspects requests in a smart Http Monitor panel
     * the monitor is able to re-send requests back to server

HTTP Monitor weaknesses

     * not able to monitor requests to different server (e.g. requests  
that call WS Operation)
           o the Http Monitor is not able to monitor SOAP Requests
     * not able to display the content of the request/response (for  
web app monitoring this was not important as the response is shown in  
browser)
           o since this, the HTTP Monitor is not suitable for AJAX  
applications (XmlHttpRequest)


Thanks,
- Vidhya

On May 5, 2008, at 2:49 AM, Hang Loose wrote:

> I would like to start contributing to a module in the Enterprise  
> Cluster called the HTTP Monitor.
> Does anyone started working on this module already ?!
> If so, I would like to help.
>
> Thanks