axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Szekely" <b...@cornell.edu>
Subject Re: What do we do with operation types: notification, solicit-response?
Date Fri, 16 Nov 2001 02:59:06 GMT
I've been working on how to implement solicit-response and notification
services using instant messaging as the transport.  The way I do it is I
create a custom Java Provider which passes IM identities and pressence
(awareness) information to the service object.  I have some demos of this
that I did for soap 2.2.  I have two different IM transports for Axis which
I could easily write providers for.

 Ben

----- Original Message -----
From: "Sanjiva Weerawarana" <sanjiva@watson.ibm.com>
To: <axis-dev@xml.apache.org>
Sent: Thursday, November 15, 2001 9:33 PM
Subject: Re: What do we do with operation types: notification,
solicit-response?


> +1
>
> The semantics of solicit-response and output-only are not quite
> fully defined. I'd rather have the semantics fixed properly
> rather than do any implementation of it.
>
> Sanjiva.
>
> ----- Original Message -----
> From: "Tom Jordahl" <tomj@macromedia.com>
> To: <axis-dev@xml.apache.org>
> Sent: Friday, November 16, 2001 12:03 AM
> Subject: RE: What do we do with operation types: notification,
> solicit-response?
>
>
> >
> > I would say generating a warning (and adding an option to suppress
> warnings)
> > and ignoring the operation would be a reasonable thing to do.
> >
> > This would allow someone to use a WSDL file which had one-way operations
> in
> > it in addition to the request-response operations that they wanted to
use.
> >
> > --
> > Tom Jordahl
> >
> >
> > -----Original Message-----
> > From: Russell Butek [mailto:butek@us.ibm.com]
> > Sent: Thursday, November 15, 2001 12:59 PM
> > To: axis-dev@xml.apache.org
> > Subject: What do we do with operation types: notification,
> > solicit-response?
> >
> >
> > WSDL defines 4 operation types:
> >    request-response:  in message, out message, fault message optional
> >    one-way: in message
> >    solicit-response:  out message, in message, fault message optional
> >    notification:  out message
> >
> > JAX-RPC says "JAX-RPC 1.0 specification supports the mapping of
operations
> > with request-response and one-way transmission primitives.  The standard
> > Java mapping of operations defined with other transmission primitives
> > (notification, solicit-response) is considered out of scope in the
JAX-RPC
> > 1.0 specification."
> >
> > Earlier we had decided to throw an exception if Wsdl2java encounters a
> > notification or solicit-response operation.  But now that I'm thinking
> > about implementing this check, I have a question.  Do we complain and
> > ignore the operation, generating everything else?  Or do we fail
outright
> > and not generate anything?
> >
> > Russell Butek
> > butek@us.ibm.com
>


Mime
View raw message