Return-Path: Delivered-To: apmail-axis-java-dev-archive@www.apache.org Received: (qmail 32000 invoked from network); 1 Apr 2010 00:29:47 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 1 Apr 2010 00:29:47 -0000 Received: (qmail 73709 invoked by uid 500); 1 Apr 2010 00:29:46 -0000 Delivered-To: apmail-axis-java-dev-archive@axis.apache.org Received: (qmail 73312 invoked by uid 500); 1 Apr 2010 00:29:46 -0000 Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@axis.apache.org Delivered-To: mailing list java-dev@axis.apache.org Received: (qmail 73304 invoked by uid 99); 1 Apr 2010 00:29:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Apr 2010 00:29:46 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=AWL,FREEMAIL_FROM,HTML_MESSAGE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of samisa.abeysinghe@gmail.com designates 74.125.83.45 as permitted sender) Received: from [74.125.83.45] (HELO mail-gw0-f45.google.com) (74.125.83.45) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Apr 2010 00:29:40 +0000 Received: by gwaa20 with SMTP id a20so412643gwa.32 for ; Wed, 31 Mar 2010 17:29:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:content-type; bh=uiwqBce2GJ+S6FUs7Pvqe4xMpIWFr/ikU3KwqdHBPmo=; b=AgzqOB5ZZoUh5ReCO1aQcWQL9TyTFSClBBChUgPeP2CkAt63gdVBUynfFZ2U7wNQl5 RfuujU0ftpHDqWnNKIFgYdU7PQptypYuBBIgj9y4GZfojn+aOI1TwvRiS9BoT7zbQO4t q6qKJI9Ri3z9lwpvcdC2ys/DPlIm8Mc4Ge0TM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=wEs7PrNphMdAvBAv+tPPI5vBsOLd9NdGQlsxFmRmgwiAtxYVosEbPohbW96gvmKWrs pDhvalf4zAj/usOSPPTgbzLuLwncxaWhy6HYCqUbSUJSa90InuGCE08lHApiuWc6PNUM kaX6RQdfm13S8pddtNfO+cZGCEjhKRAjenOtU= MIME-Version: 1.0 Received: by 10.231.153.137 with HTTP; Wed, 31 Mar 2010 17:29:18 -0700 (PDT) In-Reply-To: References: <3054da0f1003241438n62153ab8hf7201a18d98a58c4@mail.gmail.com> <3054da0f1003241503x4805a81bt10c2b2f44300bc0b@mail.gmail.com> Date: Thu, 1 Apr 2010 05:59:18 +0530 Received: by 10.101.153.5 with SMTP id f5mr740889ano.234.1270081758836; Wed, 31 Mar 2010 17:29:18 -0700 (PDT) Message-ID: Subject: Re: [GSoC Project Proposal] Distributed TCP Monitor From: Samisa Abeysinghe To: java-dev@axis.apache.org Content-Type: multipart/alternative; boundary=0016e68fcfa2123803048321f45b --0016e68fcfa2123803048321f45b Content-Type: text/plain; charset=ISO-8859-1 On Thu, Apr 1, 2010 at 4:47 AM, nilupa bandara wrote: > On Wed, Mar 31, 2010 at 4:51 PM, Samisa Abeysinghe > wrote: > >> 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. > > > > What pub/sub model do you plan to use? WS-Eventing? > > Something which allows the publisher ( or the Log service which > collects log messages from different nodes) to notify its subscribers > (or the clients which show the topology of particular message > sequence) the arrival of a message which belongs to a particular > sequence of messages that they are interested in. Is far as I > understood this notification will be based on SOAP. WS-Eventing sounds > like something that can be used but I guess I have to explore more > (rather than reading some introductory notes on WS-Eventing) to give a > concrete answer. > If you are using eventing, you might want to look at what we have done in BAM. We basically use an Axis2 module with Axis2 based eventing API to pub/sub. Since this is an Axis2 module, you can use the code as it is. We do not have any other dependency. Samisa.... > > > Best Regards, > Nilupa > > > > > Samisa... > > -- > > blog: http://samisa-abeysinghe.blogspot.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org > For additional commands, e-mail: java-dev-help@axis.apache.org > > Samisa... -- blog: http://samisa-abeysinghe.blogspot.com/ --0016e68fcfa2123803048321f45b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Thu, Apr 1, 2010 at 4:47 AM, nilupa b= andara <nilupas@g= mail.com> wrote:
On Wed, Mar 31, 2010 at 4:51 PM, Samisa Abeysinghe
<samisa= .abeysinghe@gmail.com> wrote:
>> Then we can take this to next level by add= ing 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 v= ia a
>> UI, and depicting those messages through a UI.
>
> What pub/sub model do you plan to use? =A0WS-Eventing?

Something which allows the publisher ( or the Log service which
collects log messages from different nodes) to notify its subscribers
(or the clients which show the topology of particular message
sequence) the arrival of a message which belongs to a particular
sequence of messages that they are interested in. Is far as I
understood this notification will be based on SOAP. WS-Eventing sounds
like something that can be used but I guess I have to explore more
(rather than reading some introductory notes on WS-Eventing) to give a
concrete answer.

If you are using event= ing, you might want to look at what we have done in BAM. =A0We basically us= e an Axis2 module with Axis2 based eventing API to pub/sub.=A0
Since this is an Axis2 module, you can use the code as it is. We= do not have any other=A0dependency.=A0

Samisa....=


Best Regards,
Nilupa

>
> Samisa...
> --
> blog:=A0http://samisa-abeysinghe.blogspot.com/

-----------------------------------= ----------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

Samisa...
--<= br>blog:=A0http://samisa= -abeysinghe.blogspot.com/=A0


--0016e68fcfa2123803048321f45b--