axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael <>
Subject Re: Pub\Sub Web Service
Date Tue, 24 Feb 2009 02:01:19 GMT

I looked at this before I started my design.  As a standards document it did not provide much
help with how I might implement the standard in a bottom-up Java web service implementation.
 The only thing I could get out of it is that one other option I did not list in my original
email was to send the notification back to the client as a SOAP message I would construct
dynamically from my Java server side code and use the WS-Addressing endpoint that I could
extract from the SOAP message the client sent when they subscribed.

Is that what you are suggesting by recommending this specification?

  ----- Original Message ----- 
  From: Doug Davis 
  Sent: Monday, February 23, 2009 6:51 PM
  Subject: Re: Pub\Sub Web Service

  checkout ws-baseNotification:

  STSM |  Standards Architect  |  IBM Software Group
  (919) 254-6905  |  IBM 444-6905  | 

        Michael <> 
        02/23/2009 06:47 PM Please respond to

              Subject Pub\Sub Web Service 



  I am developing a publish\subscribe engine and have exposed both the publish and subscribe
services with web services. 
  I am looking for advice on how I might implement a push notification.  Since the occurrence
of some event will trigger notification of all users that subscribed to the publication of
that event how do I go about "pushing" the notification back out to the clients from the server?

  I have provided for several options in my design.  I am allowing the subscribers to tell
me how they would like to be notified.  The options I provided are 1) provide an IP address
and port and I will send the notification using; 2) provide a URL and I will send
the notification using; and 3) provide a URL and WSDL file and the name of a web
service method to call and I will use the Axis2 API to generate Java code for the WSDL and
call designated method.  Do these options sound reasonable, particularly the third one? 
  Also, I was wondering if the Axis2 asynchronous call capability might be a good candidate
for this, either in addition to these methods or to replace them? 
  If anyone has any ideas I would love to hear them. 
  Thanks, Mike   


  No virus found in this incoming message.
  Checked by AVG - 
  Version: 8.0.237 / Virus Database: 270.11.3/1968 - Release Date: 02/23/09 18:22:00

View raw message