Hi Nilupa; When we collect messages from a one location by installing proper handler that will intercept and send messages to to that one location (this one location can be a single server, pub/sub channel etc). There is many ways to make sense of those collected messages. What Andreas mentioned (following complete transaction) is a one possibility.
I think you should come up with few scenarios on how you would make sense of the message. Thanks Srinath On Sun, Mar 28, 2010 at 9:46 PM, nilupa bandara <nilu...@gmail.com> wrote: > Hi, > > First let me thank you for commenting. > > As far as I understood, what you would like to see from the proposed > tool is to view set of messages that are exchanged in reponse to a > particular input message. With the understanding that I am having at > the momnet, one way to do it is to filter out the central repository > of messages based on 'To' , 'From' headers and try to contruct the > message chain from it. We can allow the client GUI wich connects to > the central repository to provide the paramenters (For instance the > value of 'To' header) from which an intelligent filtering can be done > for the set of messages avialable at the central repository. > > Perhaps someone has an idea of a better way of doing it and is willing > to share it with us. It would be really nice to hear from them. > > Thanks in advance ..!! > > Best Regards, > Nilupa > > On Sat, Mar 27, 2010 at 6:40 PM, Andreas Veithen > <andreas.veit...@gmail.com> wrote: >> Personally, I think that the added value of extending the SOAP monitor >> module to collect messages in a central place is too limited to >> attract enough interest from the user community, so that it will be >> difficult to ensure the evolution of such a project in the future. >> However, what many people are looking for is a tool that allows to >> track the flow of a message through a distributed system, or more >> generally to track the sequence of events triggered by a given input >> message (sort of end-to-end transaction monitoring). >> >> On Wed, Mar 24, 2010 at 23:03, nilupa bandara <nilu...@gmail.com> wrote: >>> Hello, >>> >>> I am graduate student at Politecnica de Madrid and I am thinking of >>> proposing a GSoC project this summer. I would like to take project >>> "Distribute TCP Monitor" descried[1] which is very interesting and >>> also should be helpful to any Java developer using Apache Axis2 Web >>> services middleware. I will submit more detailed proposal later. I >>> would really like to hear any feedback from you. Any suggestions or >>> features that you would like to see in a "Distributed TCP Monitor" are >>> most welcome. >>> >>> Best Regards, >>> Nilupa Bandara >>> >>> [1] >>> >>> Distributed TCP monitor >>> >>> To use TCP monitor we have to tweak the endpoints, which is bit hard >>> sometimes (e.g. two channels Async case for Axis2). We can solve the >>> problem by writing a Axis2 module (Handler) that intercept messages >>> comes in and goes out of a Axis2 server and send to a UI (via a >>> pub/sub channel or a message Box e.g. ) or record them so user can >>> pull those messages. Also, we can do something to turn the module on >>> and off remotely, so users can have his module deployed, but turn it >>> on only when they want to debug the system. >>> >>> Then we can take this to next level by adding this module to all >>> services in a system , configuring modules to send all collected >>> messages to a pub/sub channel, and subscribing to those messages via a >>> UI, and depicting those messages through a UI. Then users have a >>> TCPMon for a whole system. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org >>> For additional commands, e-mail: java-dev-h...@axis.apache.org >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org >> For additional commands, e-mail: java-dev-h...@axis.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org > For additional commands, e-mail: java-dev-h...@axis.apache.org > > -- ============================ Srinath Perera, Ph.D. WSO2 Inc. http://wso2.com Blog: http://srinathsview.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
