Yes, if you look at org.apache.soap.transport.SOAPTransport, then the implementations in the http and smtp packages, you should get a clear picture of how to write the client transport.
Virtually all the server software is based on providers running in a J2EE Web container. Support for SMTP on the server is accomplished by the org.apache.soap.server.SMTP2HTTPBridge class. This is basically a POP3 client that polls for messages, forwards them to an HTTP-based SOAP server, then sends the responses back using SMTP. This model would be the easiest to follow for other non-HTTP protocols. These comments relate to Apache SOAP, however, not Axis. I am not familiar with the Axis source, so it may be that there are provisions for more direct support of other transports on the server. Scott ----- Original Message ----- From: "Sebastian" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, November 27, 2001 7:27 AM Subject: Re: Using alternative transport? BEEP > Hello there, > > For Fitting BEEP in SOAP I would recommend looking at SOAPTransport first, > this is the main class for transporting SOAP Messages. I am right now also > trying to accomplish SOAP over BEEP and my main concern is the server > side, which is kind of complicated because there are a lot of classes > interacting which I don't really see through yet. If anyone has any > experience in using another protocol than HTTP for SOAP I would be happy > to hear from them. > > So long, > > Sebastian > > -- > __________________________________________________________________________ > sebastian thiebes [EMAIL PROTECTED] > > "Jetzt koennte ich hier tierisch die lange Inhaltsangabe Auflisten aber > ich rechne mit Eurer Integenz" - gefunden bei eBay >
