Return-Path: 
 <axis-user-return-6599-apmail-xml-axis-user-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-axis-user-archive@xml.apache.org
Received: (qmail 91491 invoked by uid 500); 22 Aug 2002 17:35:23 -0000
Mailing-List: contact axis-user-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@xml.apache.org
list-help: <mailto:axis-user-help@xml.apache.org>
list-unsubscribe: <mailto:axis-user-unsubscribe@xml.apache.org>
list-post: <mailto:axis-user@xml.apache.org>
Delivered-To: mailing list axis-user@xml.apache.org
Received: (qmail 91455 invoked from network); 22 Aug 2002 17:35:23 -0000
Message-Id: <4.3.2.7.2.20020822102622.025806f8@franklin.cisco.com>
X-Sender: riho@franklin.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 22 Aug 2002 10:35:18 -0700
To: axis-user@xml.apache.org
From: Ricky Ho <riho@cisco.com>
Subject: RE: Notification style operation
In-Reply-To: <59523CAF2AA3D111A8AB00805FE67F2E06D9391A@ewst03.exchange.m
 l.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
Status: O
X-Status: 
X-Keywords: 

Are we losing the benefit of SOAP (heterogeneous language and runtime 
environment) when we run SOAP over JMS (which is an API but not protocol) 
?  Because now both sides has to be JAVA, or even they have to be using the 
same JMS vendor.  Maybe OK for an intranet environment where both ends are 
controlled by the same organization.  But in such a well-controlled 
environment, why using a less efficient XML protocol ?

I see an evolving trend of using async messaging over HTTP.  In this case, 
the request and response are two separate "one-way" operations, correlated 
in a certain way.

Best regards,
Ricky

At 10:15 AM 8/22/2002 -0400, Maciejewski, Vincent (GMI - NY SWAPS) wrote:
>I agree with Eric. We are just talking about asynchronous messaging. SOAP 
>over JMS would be highly useful. I believe you will see a lot of vendor 
>support for that in the future.
>
>-----Original Message-----
>From: Jung, Eric (Contractor) [mailto:ejung@russellmellon.com]
>Sent: Thursday, August 22, 2002 10:05 AM
>To: 'axis-user@xml.apache.org'
>Subject: RE: Notification style operation
>
>
>I am achieving notification in my application this way:
>
>Client is also a SOAP server. It registers its endpoint with a server as
>Russell describes below. This works well, give it a try.
>
>A better solution is to have a central "Event Server" (e.g., JMS
>queue/topic) that decouples publishers from subscribers. Publishers send
>events only to the event server. The event server then notifies the
>appropriate subscribers. I haven't tried this in the SOAP world yet, but
>have done it in JMS and CORBA. There's no reason it shouldn't work.
>
>Eric H. Jung
>
>
>
>-----Original Message-----
>From: butek@us.ibm.com [mailto:butek@us.ibm.com]
>Sent: Thursday, August 22, 2002 8:45 AM
>To: axis-user@xml.apache.org
>Subject: Re: Notification style operation
>
>
>Notification is not supported by WSDL2Java, nor by AXIS (nor, in my opinion,
>by WSDL). In order to support notification, the client-side engine must
>become a server, and it must have some way to register itself as a listener
>for notifications. WSDL does not specify a means by which a client can
>register itself. We could always come up with something, but it would be our
>own AXIS-specific solution, it wouldn't be interoperable with anyone else.
>
>Russell Butek
>butek@us.ibm.com
>
>
>Please respond to axis-user@xml.apache.org
>To: <axis-user@xml.apache.org>
>cc:
>Subject: Notification style operation
>
>
>
>Hi all,
>
>Problem succinct:
>-----------------
>How do I implement notification style operations? Is their any example?
>
>
>Problem detailed:
>-----------------
>I want to write a service where a client can register. After
>registration the client will receive notification events. (asynchronous
>messages send by the server).
>
>WSDL
>I can model it in WSDL as follows (complete file below)
><message name="MonitoringResponse">
><part name="monitoringInfo" type="xsd:string"/>
></message>
>
>If I use WSDL2Java it tells me that notification style is not supported.
>IMO it should possible to code by hand. But how?
>
>
>
>
>_____
><?xml version="1.0" encoding="utf-8"?>
><definitions name="JobHandlerWS"
>targetNamespace="http://www.fhrg.fhg.de/schemas/JobHandler/"
>xmlns="http://schemas.xmlsoap.org/wsdl/"
>xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
>xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>xmlns:tns="http://www.fhrg.fhg.de/schemas/JobHandler/"
>xmlns:fhrg="http://www.fhrg.fhg.de/schemas/">
><message name="SubscribeRequest">
><part name="gridJobID" type="xsd:long"/>
></message>
><message name="SubscribeResponse">
><part name="testValue" type="xsd:string"/>
></message>
><message name="MonitoringResponse">
><part name="monitoringInfo" type="xsd:string"/>
></message>
>
><portType name="JobHandlerPortType">
><operation name="subscribeToMonitoring">
><input message="tns:SubscribeRequest"/>
><output message="tns:SubscribeResponse"/>
><fault message="tns:JotNotDefinedException"
>name="JotNotDefinedException"/>
><fault message="tns:InsufficientRightsException"
>name="InsufficientRightsException"/>
></operation>
><operation name="monitoringNotification">
><output message="tns:MonitoringResponse"/>
></operation>
></portType>
>
><binding name="JobHandlerSOAPBinding" type="tns:JobHandlerPortType">
><soap:binding style="rpc"
>transport="http://schemas.xmlsoap.org/soap/http"/>
><operation name="subscribeToMonitoring">
><soap:operation soapAction="subscribeToMonitoringJob"/>
><input>
><soap:body use="encoded"
>namespace="http://www.fhrg.fhg.de/schemes/"
>encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
></input>
><output>
><soap:body use="encoded"
>namespace="http://www.fhrg.fhg.de/schemes/"
>encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
></output>
></operation>
><operation name="monitoringNotification">
><soap:operation soapAction="monitoringNotification"/>
><output>
><soap:body use="encoded"
>namespace="http://www.fhrg.fhg.de/schemes/"
>encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
></output>
></operation>
></binding>
>
><service name="JobHandlerService">
><port name="subscribeToMonitoring"
>binding="tns:JobHandlerSOAPBinding">
><soap:address
>location="http://localhost:8070/servlet/rpcrouter"/>
></port>
><port name="monitoringNotification"
>binding="tns:JobHandlerSOAPBinding">
><soap:address
>location="http://localhost:8070/servlet/rpcrouter"/>
></port>
></service>
></definitions>