RE: Need details on setting up server for SOAP using own HTTP code(without Apache/IIS/etc.)

["Eric M. Dashofy" <ed...@ics.uci.edu>]

Derek:

I have a lightweight all-Java HTTP server implementation that runs
RPCRouterServlet (and other Java servlets) quite reliably, requires no
installation, and is very easy to understand and extend.  It's based on Jef
Poskanzer's Acme server (http://www.acme.com/) but I made some significnt
additions to make it conform better to the HTTP spec (I added HTTP POST
support, cookie support, file-upload support, fixed some bugs, etc.)  It's
got some limitations, most notably the lack of ServletContext and HTTP
session support, but for lightweight object services, it works just fine.

If you want to take a look, it's included with my Hermit package available
at:

http://www.ics.uci.edu/~edashofy/index-research.html

Hope that helps!

Regards,
-----
  Eric M. Dashofy <ed...@ics.uci.edu>
  Graduate Student Researcher, Information & Computer Science
  University of California, Irvine
  http://www.ics.uci.edu/~edashofy

-----Original Message-----
From: Derek Brown [mailto:dbrown@emeta.com]
Sent: Thursday, August 31, 2000 12:50 PM
To: soap-user@xml.apache.org
Subject: Re: Need details on setting up server for SOAP using own HTTP
code(without Apache/IIS/etc.)


I neglected to mention that this is with Java on Unix boxes- Solaris and
Linux primarily.

On Thu, 31 Aug 2000, Derek Brown wrote:

> I'm investigating using SOAP to allow two standalone applications
> (independent of Apache/IIS/etc.) to make requests of each other
> (so they'd function as both client and server).
>
> I've read a lot of docs online and looked through numerous
> example code (address book, calculate area/geometry, etc.), but
> am having trouble understanding how to set the app up as a
> server.  The bulk of the documentation seems oriented towards
> using JSP/servlets/etc., but even then I still haven't seen
> exactly what needs to be done to get the server-side set up.
>
> Looking at rpcrouter.jsp, it looks like it would receive the
> request from a web server and hand it off to whatever class had
> been registered to handle it (and then send back the reply).  I
> assume the majority of this code can be inserted into any code I
> write to serve the HTTP server function itself.
>
> So my questions are:
>
> o what does one need to do to SOAP-enable one's own HTTP server?
> That is, after the easy part of implementing the HTTP protocol,
> what needs to be done to get the incoming SOAP request handled?
>
> o are the server-side classes that actually read, hand off to the
> target class, and create SOAP replies a part of the
> org.apache.soap.* packages?
>
> o how does one register the target class (that implements the
> method) with the registry?
>
> o is the client-side as simple as GetAddress makes it look?
>
> Thanks for any answers,
> Derek
>
>