Here is the scenario which I'm talking about:
Exposing legacy application as a Web Service:
A legacy application is to be exposed as SOAP based Web Service. I would
_not_ like to embed a bulky servlet container. If all that I care is that I
should be able to recieve a soap message, so that I can invoke my legacy
application. And then respond back with a SOAP message containing the
response. Based on my research and experience, I've noticed that for couple
of reasons it is not feasible to create a proxy class and deploy it onto
apache soap (over servlet container):
** The legacy application API (if it had java based hooks!) to invoke from
proxy class is too complicated. Note that proxy class is remotely deployed
on servlet container and the application itself is a different process.
** Because of the limitations of the legacy application API, if the code to
recieve SOAP message and respond back with SOAP message has to reside
within the legacy application. In that case definitely embeding a servlet
container will be overkill. In some cases it may not even be feasible.
I think if for these scenarios, what we really need is a simple light
weight class which implements Web Service protocol for HTTP as a trasnport.
This class could listen for HTTP POST requests, invoke a handler on the
reciept of request. This handler can take care of parsing the request
message. And also it can compose and respond back with the response
message. Handler may either use Apache SOAP API to parse the request
itself. Also it may use Apache SOAP API to compose a response. This handler
can as well set HTTP headers on response messages.
Just a suggestion...
What surprises me most is that in this internet era, nobody thought of
developing a light weight listener class for listening for HTTP requests.
Java has client side support for posting data to an URL...but then at
server side you better be doing it yourself. I guess notion was you always
need a bulky web server handling this for you, though that is not
necessarily true.
And if the above suggestion makes sense, then this can be done for HTTPS as
well.
Thanks
-Ashutosh
|---------+---------------------------->
| | Pavel Ausianik |
| | <Pavel_Ausianik@e|
| | pam.com> |
| | |
| | 11/08/2002 07:49 |
| | AM |
| | Please respond to|
| | soap-dev |
| | |
|---------+---------------------------->
>---------------------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
|
| cc:
|
| Subject: RE: ApcheSOAP without Apache
|
|
|
|
|
>---------------------------------------------------------------------------------------------------------------------------------------------|
I guess existing Apache SOAP server solution is really servlet based. I
think also, somebody who wants to parse HTTP header hardly will want to
impement servlet API (because it is rather big for small service).
At the same time , if impelementing some custom API to support HTTP, it
will
be probably not standard, so the SOAP solution for this will be custom as
well. I mean anyway add SOAP intergration is less complex than write own
HTTP server,
I would suggest start searching over web for free open source simple http
implementation. I would also recommend to stay with servlet engine. If
current version are too complex, adn require a lot of memery - try to find
older version, without EJB and JSP support, or disable all unnecessary
services on current implementation.
Pavel
> -----Original Message-----
> From: Scott Nichol [mailto:snicholnews@;scottnichol.com]
> Sent: Friday, November 08, 2002 6:50 AM
> To: [EMAIL PROTECTED]
> Subject: Re: ApcheSOAP without Apache
>
>
> You may find it difficult to have Apache SOAP parse the
> request, execute
> the service method, the write the response, because some of the server
> code to do this depends on the code running in a servlet
> container. It
> would be *great* to factor out these dependencies: any volunteers?
>
> Scott Nichol
>
> ----- Original Message -----
> From: "Ashutosh Arora" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, November 07, 2002 5:34 PM
> Subject: Re: ApcheSOAP without Apache
>
>
> >
> > I'm also interested in something similar. I basically want
> to be able
> to
> > recieve HTTP requests, extract the HTTP headers, HTTP body. And then
> using
> > Apache SOAP parse the SOAP message. And then finally compose a
> response
> > using Apache SOAP and respond back to the client. Is there any open
> source,
> > which I could use for receving HTTP requests?
> >
> > Thanks
> > -Ashutosh
> >
> >
> >
> >
> > Scott Nichol
> > <snicholnews@scott To:
> [EMAIL PROTECTED]
> > nichol.com> cc:
> > Subject: Re:
> ApcheSOAP without Apache
> > 11/07/2002 02:32
> > PM
> > Please respond to
> > soap-dev
> >
> >
> >
> >
> >
> > I did something similar to what you describe back when SOAP 0.9 was
> > current. Basically, you probably want code to read HTTP headers and
> > then the HTTP body. You take the body and parse into an
> XML DOM, then
> > traverse the DOM to pick out the important parts of the SOAP call,
> then
> > write HTTP headers and XML body for the response. This is
> the core of
> > handling SOAP requests. Probably well more than 50% of the Apache
> SOAP
> > source is devoted to attaching more advanced features onto
> this and/or
> > supporting as many features of SOAP 1.1 as possible.
> >
> > Scott Nichol
> >
> > ----- Original Message -----
> > From: "Jean-Luc Cooke" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, November 07, 2002 11:14 AM
> > Subject: ApcheSOAP without Apache
> >
> >
> > > All, good work on this OSS project. Very keen.
> > >
> > > I'm going to ask something out-landish here and I'm very
> interested
> in
> > your
> > > response.
> > >
> > > I'd like to create a small java application which accepts
> HTTP-SOAP
> > requests
> > > and
> > > processes them. In other words: I want to create a light-weight
> > HTTP-SOAP
> > > service using only Java.
> > >
> > > The object with the main(String[]) method would have a
> ServerSocket
> > and spawn
> > > child worker threads as requests come in. Not hard. But
> how would
> I
> > parse
> > > the SOAP request myself since there's no Apache/Tomcat/Jakarta?
> > >
> > > Many thanks, looking forward to your reply.
> > >
> > > JLC
> > >
> > > --
> > > To unsubscribe, e-mail:
> <mailto:soap-dev-unsubscribe@;xml.apache.org>
> > > For additional commands, e-mail:
> <mailto:soap-dev-help@;xml.apache.org>
> > >
> > >
> >
> >
> > --
> > To unsubscribe, e-mail:
> <mailto:soap-dev-unsubscribe@;xml.apache.org>
> > For additional commands, e-mail:
> <mailto:soap-dev-help@;xml.apache.org>
> >
> >
> >
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
> <mailto:soap-dev-unsubscribe@;xml.apache.org>
> > For additional commands, e-mail:
> <mailto:soap-dev-help@;xml.apache.org>
> >
> >
>
>
> --
> To unsubscribe, e-mail: <mailto:soap-dev-unsubscribe@;xml.apache.org>
> For additional commands, e-mail: <mailto:soap-dev-help@;xml.apache.org>
>
--
To unsubscribe, e-mail: <mailto:soap-dev-unsubscribe@;xml.apache.org>
For additional commands, e-mail: <mailto:soap-dev-help@;xml.apache.org>
--
To unsubscribe, e-mail: <mailto:soap-dev-unsubscribe@;xml.apache.org>
For additional commands, e-mail: <mailto:soap-dev-help@;xml.apache.org>
