Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 73717 invoked from network); 22 Nov 2006 17:46:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Nov 2006 17:46:01 -0000 Received: (qmail 40576 invoked by uid 500); 22 Nov 2006 17:46:01 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 40563 invoked by uid 500); 22 Nov 2006 17:46:01 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 40552 invoked by uid 99); 22 Nov 2006 17:46:01 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Nov 2006 09:46:01 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of baschtikoehler@gmx.de designates 213.165.64.20 as permitted sender) Received: from [213.165.64.20] (HELO mail.gmx.net) (213.165.64.20) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 22 Nov 2006 09:45:48 -0800 Received: (qmail invoked by alias); 22 Nov 2006 17:45:26 -0000 Received: from p5080E502.dip.t-dialin.net (EHLO waldschrat1) [80.128.229.2] by mail.gmx.net (mp016) with SMTP; 22 Nov 2006 18:45:26 +0100 X-Authenticated: #12928842 From: =?iso-8859-1?Q?Bastian_K=F6hler?= To: Subject: AW: [AXIS2]Savan Module - possible to notify client instead of another service? Date: Wed, 22 Nov 2006 18:45:28 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Thread-Index: AccNw/TJEvJ8HOZxTweFmJ7kFYwMyQAk82bw In-Reply-To: <9d4ec10b0611211522s63409430o32e773d1d6001051@mail.gmail.com> X-Y-GMX-Trusted: 0 X-Virus-Checked: Checked by ClamAV on apache.org Message-Id: <20061122174551.1BAA810FB007@herse.apache.org> Hi Chamikara, Thanks for your answer. I tried it today as suggested, but it didn't = work. The problem is, that i do not get any exception or axis fault, but the messages aren't delivered to my client.=20 I first start a http server on the client side and register the service (POJO), which will be the endpoint for the messages. ... ConfigurationContext context =3D ConfigurationContextFactory.createConfigurationContextFromFileSystem(null= , null); AxisService service =3D AxisService.createService(ListnerService1.class.getName(), context.getAxisConfiguration()); context.getAxisConfiguration().addService(service); =20 SimpleHTTPServer server =3D new SimpleHTTPServer(context, 8081); server.start(); ... Then the Subscription is done. String address =3D = "http://127.0.0.1:8081/axis2/services/ListnerService1"; EventingClientBean bean =3D new EventingClientBean (); String id =3D "id1"; bean.setDeliveryEPR (new EndpointReference (address)); =20 eventingClient.subscribe(bean,ID); The http-Server on the client side is running (http://localhost:8081/axis2/services/ListnerService1 shows the = generated wsdl) and on the server side the=20 Messages are generated.=20 In the API there is another method to create a service "createClientSideService". Do i have to use this method instead?=20 Bastian. >-----Urspr=FCngliche Nachricht----- >Von: Chamikara Jayalath [mailto:chamikaramj@gmail.com]=20 >Gesendet: Mittwoch, 22. November 2006 00:22 >An: axis-user@ws.apache.org >Betreff: Re: [AXIS2]Savan Module - possible to notify client=20 >instead of another service? > >Hi Bastian, > >Yes. The way u suggested will certainly work. All u need to=20 >have is a endpoint that is capable of capturing the events=20 >send by the EventSource. > >You can set this endpoint as the delivery EPR, of the EventingClient.=20 >e.g.: > String address =3D "address of your desired delivery endpoint"; > EventingClientBean bean =3D new EventingClientBean (); > String id =3D "id1"; > bean.setDeliveryEPR (new EndpointReference (address)); =20 > eventingClient.subscribe(bean,ID); > > >Thanks, >Chamikara > > > >On 11/20/06, Bastian K=F6hler wrote: > > Hi, > I have a question about the Axis2 Savan Module, which=20 >provides WS-Eventing > support. > I downloaded the sample application code from the svn=20 >repository. In the > example a listenerservice is notified about new events=20 >(produced by another=20 > service). > Is it also possible to send the notification messages=20 >to the client instead > of another Webservice? I want the client(s) to be=20 >notified about events (or > new data). And the second question is, how to do that.=20 >My first idea was to=20 > use the simplehttpserver on the clientside and register=20 >a service, which is > then used as the Listenerservice...Does this make sense=20 >or are there any > better solutions to my problem. >=09 > Any suggestion would be helpful. Thanks in advance.=20 >=09 >=09 > Bastian >=09 >=09 >=09 >--------------------------------------------------------------------- > To unsubscribe, e-mail:=20 >axis-user-unsubscribe@ws.apache.org=20 >=20 > For additional commands, e-mail: axis-user-help@ws.apache.org >=09 >=09 > > > --------------------------------------------------------------------- To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org For additional commands, e-mail: axis-user-help@ws.apache.org