You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@xml.apache.org by Amy L Therrien <th...@us.ibm.com> on 2001/05/03 00:24:06 UTC
Lightweight WebServer/Servlet Implementation
Hi folks,
Is anyone aware of a lightweight Java implementation of SOAP for those who
want remote procedure call functionality only? In other words, I would
like a Java API that includes some sort of mimalized webserver/servlet
server than only understands the SOAP RPCs requests. Then, I could
instaniate this server from my code current Java "server" to listen on a
specified port.
This desire is inspired by the fact that I do not want to install Tomcat or
WebSphere right now, but will at a later date. Currently, I have no needs
for a servlet engine so it seems like such a waste to install
Tomcat/WebSphere, etc, when I simply want to make calls from one java
process to another remote java process.
The eventual goal is to go from a java server and java client (using an Orb
for remote calls) to a java server with generic client (using SOAP for
remote calls). Ideally, we would like to make the transition gradual by
converting ORB Java API to SOAP Java API. Then, at some point, publish
some sort of doc. so other non-java types of clients can XML for the remote
procedure calls.
Currently, XML-RPC has a nice implementation for RPCs without requiring an
external servlet/webserve engine, but it, obviously, does not use the SOAP
standard for XML. For those interested, it is available at
www.xml-rpc.com/.
Amy L Therrien
ESS Software Development Engineer
IBM Storage Systems Group
therrien@us.ibm.com
Text Page: 1132755@mobilecomm.net
RE: Lightweight WebServer/Servlet Implementation
Posted by graham glass <gr...@mindspring.com>.
hi amy,
i think that my company's product, GLUE, does what you want.
it includes a fast SOAP implementation, dynamic WSDL generation,
dynamic proxies, UDDI client, UDDI server, servlet engine,
web server, persistent XML storage engine, and fast XML parser
in just 340K. it will work stand-alone or hosted in a 3rd party
servlet engine. you can strip out the stuff you don't need.
it is free for most commercial uses.
check it out at http://www.themindelectric.com.
hope this helps!
cheers,
graham
-----Original Message-----
From: Dave Winer [mailto:dave@userland.com]
Sent: Saturday, May 19, 2001 10:44 PM
To: soap-dev@xml.apache.org
Subject: Re: Lightweight WebServer/Servlet Implementation
Amy, as I was reading your message I was getting ready to forward it to the
xml-rpc mail list. I think you've defined a very nice feature-set for a
lightweight SOAP-for-Java implementation. We've got a bunch of Java people
in the xml-rpc commmunity. If you'd like I could forward it, or you could
raise the question there. Dave
----- Original Message -----
From: "Amy L Therrien" <th...@us.ibm.com>
To: <so...@xml.apache.org>
Sent: Wednesday, May 02, 2001 3:24 PM
Subject: Lightweight WebServer/Servlet Implementation
> Hi folks,
>
> Is anyone aware of a lightweight Java implementation of SOAP for those who
> want remote procedure call functionality only? In other words, I would
> like a Java API that includes some sort of mimalized webserver/servlet
> server than only understands the SOAP RPCs requests. Then, I could
> instaniate this server from my code current Java "server" to listen on a
> specified port.
>
> This desire is inspired by the fact that I do not want to install Tomcat
or
> WebSphere right now, but will at a later date. Currently, I have no needs
> for a servlet engine so it seems like such a waste to install
> Tomcat/WebSphere, etc, when I simply want to make calls from one java
> process to another remote java process.
>
> The eventual goal is to go from a java server and java client (using an
Orb
> for remote calls) to a java server with generic client (using SOAP for
> remote calls). Ideally, we would like to make the transition gradual by
> converting ORB Java API to SOAP Java API. Then, at some point, publish
> some sort of doc. so other non-java types of clients can XML for the
remote
> procedure calls.
>
> Currently, XML-RPC has a nice implementation for RPCs without requiring an
> external servlet/webserve engine, but it, obviously, does not use the SOAP
> standard for XML. For those interested, it is available at
> www.xml-rpc.com/.
>
> Amy L Therrien
> ESS Software Development Engineer
> IBM Storage Systems Group
> therrien@us.ibm.com
> Text Page: 1132755@mobilecomm.net
>
>
Re: Lightweight WebServer/Servlet Implementation
Posted by Dave Winer <da...@userland.com>.
Amy, as I was reading your message I was getting ready to forward it to the
xml-rpc mail list. I think you've defined a very nice feature-set for a
lightweight SOAP-for-Java implementation. We've got a bunch of Java people
in the xml-rpc commmunity. If you'd like I could forward it, or you could
raise the question there. Dave
----- Original Message -----
From: "Amy L Therrien" <th...@us.ibm.com>
To: <so...@xml.apache.org>
Sent: Wednesday, May 02, 2001 3:24 PM
Subject: Lightweight WebServer/Servlet Implementation
> Hi folks,
>
> Is anyone aware of a lightweight Java implementation of SOAP for those who
> want remote procedure call functionality only? In other words, I would
> like a Java API that includes some sort of mimalized webserver/servlet
> server than only understands the SOAP RPCs requests. Then, I could
> instaniate this server from my code current Java "server" to listen on a
> specified port.
>
> This desire is inspired by the fact that I do not want to install Tomcat
or
> WebSphere right now, but will at a later date. Currently, I have no needs
> for a servlet engine so it seems like such a waste to install
> Tomcat/WebSphere, etc, when I simply want to make calls from one java
> process to another remote java process.
>
> The eventual goal is to go from a java server and java client (using an
Orb
> for remote calls) to a java server with generic client (using SOAP for
> remote calls). Ideally, we would like to make the transition gradual by
> converting ORB Java API to SOAP Java API. Then, at some point, publish
> some sort of doc. so other non-java types of clients can XML for the
remote
> procedure calls.
>
> Currently, XML-RPC has a nice implementation for RPCs without requiring an
> external servlet/webserve engine, but it, obviously, does not use the SOAP
> standard for XML. For those interested, it is available at
> www.xml-rpc.com/.
>
> Amy L Therrien
> ESS Software Development Engineer
> IBM Storage Systems Group
> therrien@us.ibm.com
> Text Page: 1132755@mobilecomm.net
>
>
Re: Lightweight WebServer/Servlet Implementation
Posted by Naggi Rao <na...@softhome.net>.
Hi Amy,
I guess Apache SOAP it self is a very light weight Engine
Although I have heard about a much lighter version written in Perl.
I guess you could use Apache's implementation just out of the box or I would
rather prefer writing a simple/very light SOAP Emulator/Engine if I wanted
anything lighter..
although A few light weight Servlet engines could be found at :
http://www.inside-java.com/articles/servlets/sengines.htm
Although check http://www.pocketsoap.com if you could find anything for your
self
--Naggi
----- Original Message -----
From: "Amy L Therrien" <th...@us.ibm.com>
To: <so...@xml.apache.org>
Sent: Wednesday, May 02, 2001 3:24 PM
Subject: Lightweight WebServer/Servlet Implementation
> Hi folks,
>
> Is anyone aware of a lightweight Java implementation of SOAP for those who
> want remote procedure call functionality only? In other words, I would
> like a Java API that includes some sort of mimalized webserver/servlet
> server than only understands the SOAP RPCs requests. Then, I could
> instaniate this server from my code current Java "server" to listen on a
> specified port.
>
> This desire is inspired by the fact that I do not want to install Tomcat
or
> WebSphere right now, but will at a later date. Currently, I have no needs
> for a servlet engine so it seems like such a waste to install
> Tomcat/WebSphere, etc, when I simply want to make calls from one java
> process to another remote java process.
>
> The eventual goal is to go from a java server and java client (using an
Orb
> for remote calls) to a java server with generic client (using SOAP for
> remote calls). Ideally, we would like to make the transition gradual by
> converting ORB Java API to SOAP Java API. Then, at some point, publish
> some sort of doc. so other non-java types of clients can XML for the
remote
> procedure calls.
>
> Currently, XML-RPC has a nice implementation for RPCs without requiring an
> external servlet/webserve engine, but it, obviously, does not use the SOAP
> standard for XML. For those interested, it is available at
> www.xml-rpc.com/.
>
> Amy L Therrien
> ESS Software Development Engineer
> IBM Storage Systems Group
> therrien@us.ibm.com
> Text Page: 1132755@mobilecomm.net
>
>
>
Re: Lightweight WebServer/Servlet Implementation
Posted by Scott Nichol <sn...@computer.org>.
I know of listings of implementations at http://www.soapware.org/directory/4/implementations and http://www.xml.com/pub/rg/SOAP_Software.
Scott
----- Original Message -----
From: "Amy L Therrien" <th...@us.ibm.com>
To: <so...@xml.apache.org>
Sent: Wednesday, May 02, 2001 6:24 PM
Subject: Lightweight WebServer/Servlet Implementation
> Hi folks,
>
> Is anyone aware of a lightweight Java implementation of SOAP for those who
> want remote procedure call functionality only? In other words, I would
> like a Java API that includes some sort of mimalized webserver/servlet
> server than only understands the SOAP RPCs requests. Then, I could
> instaniate this server from my code current Java "server" to listen on a
> specified port.
>
> This desire is inspired by the fact that I do not want to install Tomcat or
> WebSphere right now, but will at a later date. Currently, I have no needs
> for a servlet engine so it seems like such a waste to install
> Tomcat/WebSphere, etc, when I simply want to make calls from one java
> process to another remote java process.
>
> The eventual goal is to go from a java server and java client (using an Orb
> for remote calls) to a java server with generic client (using SOAP for
> remote calls). Ideally, we would like to make the transition gradual by
> converting ORB Java API to SOAP Java API. Then, at some point, publish
> some sort of doc. so other non-java types of clients can XML for the remote
> procedure calls.
>
> Currently, XML-RPC has a nice implementation for RPCs without requiring an
> external servlet/webserve engine, but it, obviously, does not use the SOAP
> standard for XML. For those interested, it is available at
> www.xml-rpc.com/.
>
> Amy L Therrien
> ESS Software Development Engineer
> IBM Storage Systems Group
> therrien@us.ibm.com
> Text Page: 1132755@mobilecomm.net
>
>
RE: Lightweight WebServer/Servlet Implementation
Posted by graham glass <gr...@mindspring.com>.
hi amy,
GLUE includes a web server, servlet engine, SOAP engine,
dynamic WSDL generation, a UDDI client, UDDI server,
dynamic proxy generation, fast XML parser and more in just 340K.
you can start a server and export an unmodified java object
as a web service in two lines of code, and bind to any remote
SOAP object in just one line of code.
the core GLUE functionality is free for more commercial uses,
and can be downloaded from http://www.themindelectric.com.
hope this helps,
cheers,
graham
-----Original Message-----
From: Amy L Therrien [mailto:therrien@us.ibm.com]
Sent: Wednesday, May 02, 2001 5:24 PM
To: soap-dev@xml.apache.org
Subject: Lightweight WebServer/Servlet Implementation
Hi folks,
Is anyone aware of a lightweight Java implementation of SOAP for those who
want remote procedure call functionality only? In other words, I would
like a Java API that includes some sort of mimalized webserver/servlet
server than only understands the SOAP RPCs requests. Then, I could
instaniate this server from my code current Java "server" to listen on a
specified port.
This desire is inspired by the fact that I do not want to install Tomcat or
WebSphere right now, but will at a later date. Currently, I have no needs
for a servlet engine so it seems like such a waste to install
Tomcat/WebSphere, etc, when I simply want to make calls from one java
process to another remote java process.
The eventual goal is to go from a java server and java client (using an Orb
for remote calls) to a java server with generic client (using SOAP for
remote calls). Ideally, we would like to make the transition gradual by
converting ORB Java API to SOAP Java API. Then, at some point, publish
some sort of doc. so other non-java types of clients can XML for the remote
procedure calls.
Currently, XML-RPC has a nice implementation for RPCs without requiring an
external servlet/webserve engine, but it, obviously, does not use the SOAP
standard for XML. For those interested, it is available at
www.xml-rpc.com/.
Amy L Therrien
ESS Software Development Engineer
IBM Storage Systems Group
therrien@us.ibm.com
Text Page: 1132755@mobilecomm.net