You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@xml.apache.org by Cory Isaacson <ci...@capita2.com> on 2000/08/20 22:30:28 UTC
Servlets and SOAP
Is there any way to have a Servlet be a provider for a SOAP call?
Cory
Re: Servlets and SOAP
Posted by Cory Isaacson <ci...@capita2.com>.
Rich,
I agree, its a must. If a provider object can be a servlet, the problem goes away, and if not, you're correct - it needs the context and session objects.
Thanks,
Cory
----- Original Message -----
From: Rich Johns
To: soap-user@xml.apache.org
Sent: Monday, August 21, 2000 10:05 AM
Subject: Re: Servlets and SOAP
What you want is the provider to get context. If the provider is a java class (as is the case in the
current architecture) then the context must be passed to the provider somehow ( a sticky issue).
OTH, if the provider were a servlet, then the issue of passing context to provider classes becomes
a moot point.
The next problem you have for the provider that needs context, is to get that same context back
to the provider on the successive soap calls that form a conceptual client session. You have to
get the response headers generated by the web server/servlet engine for a given soap call out of the
Call strucutre and submitted as response headers to the subsequent calls.
See earlier posts from me that describe a protoype that I have for doing this for the NON-servlet
provider class case. A generalized solution that allows a provider to be a
servlet might be a more palatable change to the architecture than passing context to java class providers.
I could work with either, but I'd like to see some form of this functionality as part of the standard distribution.
Cory Isaacson wrote:
Steve, I do mean a server, so instead of using a provider class, invoke a servlet. I can certainly see how I could modify the RPCServlet code to do this, I just wondered if there were plans to make it a standard feature. My reasoning is that I need to buffer certain things, and need access to the servlet context/session objects to do part of the job. If I modify the RPCServlet, then I assume that my site won't respond to other standard SOAP calls (which may not matter in this case) but it would be neat if you could invoke a class or a servlet as part of the architecture, and the invoked servlet got passed the request object through servlet chaining. Just an idea, but I bet not hard to include in the SOAP product itself if others agree. Cory
----- Original Message -----
From: Steven J. McDowall
To: soap-user@xml.apache.org
Sent: Sunday, August 20, 2000 5:07 PM
Subject: RE: Servlets and SOAP
"Provider" ?? That is an ambigious request.. :-)Do you mean client? Of course, just use "invoke" like anyway else..Do you mean server (which I think you do) the answer is of course again, although a bitof work..Most of the logic is the same (exactly) as in the RPCServlet code itself.. That really is a "Soap Server" of a sort.. Just take the part where it decodes the soap message and ferretsout the data it wants with DOM calls to get the elements you want..Perhaps not totally elegant, but it should work..
-----Original Message-----
From: Cory Isaacson [mailto:cisaacson@capita2.com]
Sent: Sunday, August 20, 2000 3:30 PM
To: soap-user@xml.apache.org
Subject: Servlets and SOAP
Is there any way to have a Servlet be a provider for a SOAP call? Cory
Re: Servlets and SOAP
Posted by Cory Isaacson <ci...@capita2.com>.
Rich,
I agree, its a must. If a provider object can be a servlet, the problem goes away, and if not, you're correct - it needs the context and session objects.
Thanks,
Cory
----- Original Message -----
From: Rich Johns
To: soap-user@xml.apache.org
Sent: Monday, August 21, 2000 10:05 AM
Subject: Re: Servlets and SOAP
What you want is the provider to get context. If the provider is a java class (as is the case in the
current architecture) then the context must be passed to the provider somehow ( a sticky issue).
OTH, if the provider were a servlet, then the issue of passing context to provider classes becomes
a moot point.
The next problem you have for the provider that needs context, is to get that same context back
to the provider on the successive soap calls that form a conceptual client session. You have to
get the response headers generated by the web server/servlet engine for a given soap call out of the
Call strucutre and submitted as response headers to the subsequent calls.
See earlier posts from me that describe a protoype that I have for doing this for the NON-servlet
provider class case. A generalized solution that allows a provider to be a
servlet might be a more palatable change to the architecture than passing context to java class providers.
I could work with either, but I'd like to see some form of this functionality as part of the standard distribution.
Cory Isaacson wrote:
Steve, I do mean a server, so instead of using a provider class, invoke a servlet. I can certainly see how I could modify the RPCServlet code to do this, I just wondered if there were plans to make it a standard feature. My reasoning is that I need to buffer certain things, and need access to the servlet context/session objects to do part of the job. If I modify the RPCServlet, then I assume that my site won't respond to other standard SOAP calls (which may not matter in this case) but it would be neat if you could invoke a class or a servlet as part of the architecture, and the invoked servlet got passed the request object through servlet chaining. Just an idea, but I bet not hard to include in the SOAP product itself if others agree. Cory
----- Original Message -----
From: Steven J. McDowall
To: soap-user@xml.apache.org
Sent: Sunday, August 20, 2000 5:07 PM
Subject: RE: Servlets and SOAP
"Provider" ?? That is an ambigious request.. :-)Do you mean client? Of course, just use "invoke" like anyway else..Do you mean server (which I think you do) the answer is of course again, although a bitof work..Most of the logic is the same (exactly) as in the RPCServlet code itself.. That really is a "Soap Server" of a sort.. Just take the part where it decodes the soap message and ferretsout the data it wants with DOM calls to get the elements you want..Perhaps not totally elegant, but it should work..
-----Original Message-----
From: Cory Isaacson [mailto:cisaacson@capita2.com]
Sent: Sunday, August 20, 2000 3:30 PM
To: soap-user@xml.apache.org
Subject: Servlets and SOAP
Is there any way to have a Servlet be a provider for a SOAP call? Cory
Re: Servlets and SOAP
Posted by Rich Johns <rj...@vignette.com>.
What you want is the provider to get context. If the provider is a java class (as is the case in the
current architecture) then the context must be passed to the provider somehow ( a sticky issue).
OTH, if the provider were a servlet, then the issue of passing context to provider classes becomes
a moot point.
The next problem you have for the provider that needs context, is to get that same context back
to the provider on the successive soap calls that form a conceptual client session. You have to
get the response headers generated by the web server/servlet engine for a given soap call out of the
Call strucutre and submitted as response headers to the subsequent calls.
See earlier posts from me that describe a protoype that I have for doing this for the NON-servlet
provider class case. A generalized solution that allows a provider to be a
servlet might be a more palatable change to the architecture than passing context to java class
providers.
I could work with either, but I'd like to see some form of this functionality as part of the
standard distribution.
Cory Isaacson wrote:
> Steve, I do mean a server, so instead of using a provider class, invoke a servlet. I can certainly
> see how I could modify the RPCServlet code to do this, I just wondered if there were plans to make
> it a standard feature. My reasoning is that I need to buffer certain things, and need access to
> the servlet context/session objects to do part of the job. If I modify the RPCServlet, then I
> assume that my site won't respond to other standard SOAP calls (which may not matter in this case)
> but it would be neat if you could invoke a class or a servlet as part of the architecture, and the
> invoked servlet got passed the request object through servlet chaining. Just an idea, but I bet
> not hard to include in the SOAP product itself if others agree. Cory
>
> ----- Original Message -----
> From: Steven J. McDowall
> To: soap-user@xml.apache.org
> Sent: Sunday, August 20, 2000 5:07 PM
> Subject: RE: Servlets and SOAP
> "Provider" ?? That is an ambigious request.. :-)Do you mean client? Of course, just
> use "invoke" like anyway else..Do you mean server (which I think you do) the answer is
> of course again, although a bitof work..Most of the logic is the same (exactly) as in
> the RPCServlet code itself.. That really is a "Soap Server" of a sort.. Just take the
> part where it decodes the soap message and ferretsout the data it wants with DOM calls
> to get the elements you want..Perhaps not totally elegant, but it should work..
>
> -----Original Message-----
> From: Cory Isaacson [mailto:cisaacson@capita2.com]
> Sent: Sunday, August 20, 2000 3:30 PM
> To: soap-user@xml.apache.org
> Subject: Servlets and SOAP
>
> Is there any way to have a Servlet be a provider for a SOAP call? Cory
>
Re: Servlets and SOAP
Posted by Rich Johns <rj...@vignette.com>.
What you want is the provider to get context. If the provider is a java class (as is the case in the
current architecture) then the context must be passed to the provider somehow ( a sticky issue).
OTH, if the provider were a servlet, then the issue of passing context to provider classes becomes
a moot point.
The next problem you have for the provider that needs context, is to get that same context back
to the provider on the successive soap calls that form a conceptual client session. You have to
get the response headers generated by the web server/servlet engine for a given soap call out of the
Call strucutre and submitted as response headers to the subsequent calls.
See earlier posts from me that describe a protoype that I have for doing this for the NON-servlet
provider class case. A generalized solution that allows a provider to be a
servlet might be a more palatable change to the architecture than passing context to java class
providers.
I could work with either, but I'd like to see some form of this functionality as part of the
standard distribution.
Cory Isaacson wrote:
> Steve, I do mean a server, so instead of using a provider class, invoke a servlet. I can certainly
> see how I could modify the RPCServlet code to do this, I just wondered if there were plans to make
> it a standard feature. My reasoning is that I need to buffer certain things, and need access to
> the servlet context/session objects to do part of the job. If I modify the RPCServlet, then I
> assume that my site won't respond to other standard SOAP calls (which may not matter in this case)
> but it would be neat if you could invoke a class or a servlet as part of the architecture, and the
> invoked servlet got passed the request object through servlet chaining. Just an idea, but I bet
> not hard to include in the SOAP product itself if others agree. Cory
>
> ----- Original Message -----
> From: Steven J. McDowall
> To: soap-user@xml.apache.org
> Sent: Sunday, August 20, 2000 5:07 PM
> Subject: RE: Servlets and SOAP
> "Provider" ?? That is an ambigious request.. :-)Do you mean client? Of course, just
> use "invoke" like anyway else..Do you mean server (which I think you do) the answer is
> of course again, although a bitof work..Most of the logic is the same (exactly) as in
> the RPCServlet code itself.. That really is a "Soap Server" of a sort.. Just take the
> part where it decodes the soap message and ferretsout the data it wants with DOM calls
> to get the elements you want..Perhaps not totally elegant, but it should work..
>
> -----Original Message-----
> From: Cory Isaacson [mailto:cisaacson@capita2.com]
> Sent: Sunday, August 20, 2000 3:30 PM
> To: soap-user@xml.apache.org
> Subject: Servlets and SOAP
>
> Is there any way to have a Servlet be a provider for a SOAP call? Cory
>
Re: Servlets and SOAP
Posted by Cory Isaacson <ci...@capita2.com>.
OK, I'll roll my own for now. I'm worked out how I can add the functionality I need, by calling a specific servlet or a special version which passes along the session/context data.
Cory
----- Original Message -----
From: Steven J. McDowall
To: soap-user@xml.apache.org
Sent: Monday, August 21, 2000 9:18 AM
Subject: RE: Servlets and SOAP
Cory, there was some talk of this, but I don't think anything came of it yet..
In any case, you would not want to remove rpcrouter as an alias for org.apache.soap.RPCRouterSevlet
as a registered sevlet name, but instead simply ADD new servlets for the new SOAP Servlets you create
IMHO.. Thus, you won't lose the functionality if you still want/desire the "old" rpc style.. It just depends
on which URL you invoke on the server side..
If you look in the archives (that's a joke btw :-() I think someone posted a version of the rpc servlet which
uses "engines", one of which is the rpc engine as we know it. THe idea was that you could easily register
other "engines" (services) on top of the main structure.. I then Jean-Loius someone did the work..not
sure what happened though..
-Steve
-----Original Message-----
From: Cory Isaacson [mailto:cisaacson@capita2.com]
Sent: Sunday, August 20, 2000 4:37 PM
To: soap-user@xml.apache.org; sjmcdowall@visi.com
Subject: Re: Servlets and SOAP
Steve,
I do mean a server, so instead of using a provider class, invoke a servlet. I can certainly see how I could modify the RPCServlet code to do this, I just wondered if there were plans to make it a standard feature.
My reasoning is that I need to buffer certain things, and need access to the servlet context/session objects to do part of the job. If I modify the RPCServlet, then I assume that my site won't respond to other standard SOAP calls (which may not matter in this case) but it would be neat if you could invoke a class or a servlet as part of the architecture, and the invoked servlet got passed the request object through servlet chaining.
Just an idea, but I bet not hard to include in the SOAP product itself if others agree.
Cory
----- Original Message -----
From: Steven J. McDowall
To: soap-user@xml.apache.org
Sent: Sunday, August 20, 2000 5:07 PM
Subject: RE: Servlets and SOAP
"Provider" ?? That is an ambigious request.. :-)
Do you mean client? Of course, just use "invoke" like anyway else..
Do you mean server (which I think you do) the answer is of course again, although a bit
of work..
Most of the logic is the same (exactly) as in the RPCServlet code itself.. That really is a
"Soap Server" of a sort.. Just take the part where it decodes the soap message and ferrets
out the data it wants with DOM calls to get the elements you want..
Perhaps not totally elegant, but it should work..
-----Original Message-----
From: Cory Isaacson [mailto:cisaacson@capita2.com]
Sent: Sunday, August 20, 2000 3:30 PM
To: soap-user@xml.apache.org
Subject: Servlets and SOAP
Is there any way to have a Servlet be a provider for a SOAP call?
Cory
Re: Servlets and SOAP
Posted by Cory Isaacson <ci...@capita2.com>.
OK, I'll roll my own for now. I'm worked out how I can add the functionality I need, by calling a specific servlet or a special version which passes along the session/context data.
Cory
----- Original Message -----
From: Steven J. McDowall
To: soap-user@xml.apache.org
Sent: Monday, August 21, 2000 9:18 AM
Subject: RE: Servlets and SOAP
Cory, there was some talk of this, but I don't think anything came of it yet..
In any case, you would not want to remove rpcrouter as an alias for org.apache.soap.RPCRouterSevlet
as a registered sevlet name, but instead simply ADD new servlets for the new SOAP Servlets you create
IMHO.. Thus, you won't lose the functionality if you still want/desire the "old" rpc style.. It just depends
on which URL you invoke on the server side..
If you look in the archives (that's a joke btw :-() I think someone posted a version of the rpc servlet which
uses "engines", one of which is the rpc engine as we know it. THe idea was that you could easily register
other "engines" (services) on top of the main structure.. I then Jean-Loius someone did the work..not
sure what happened though..
-Steve
-----Original Message-----
From: Cory Isaacson [mailto:cisaacson@capita2.com]
Sent: Sunday, August 20, 2000 4:37 PM
To: soap-user@xml.apache.org; sjmcdowall@visi.com
Subject: Re: Servlets and SOAP
Steve,
I do mean a server, so instead of using a provider class, invoke a servlet. I can certainly see how I could modify the RPCServlet code to do this, I just wondered if there were plans to make it a standard feature.
My reasoning is that I need to buffer certain things, and need access to the servlet context/session objects to do part of the job. If I modify the RPCServlet, then I assume that my site won't respond to other standard SOAP calls (which may not matter in this case) but it would be neat if you could invoke a class or a servlet as part of the architecture, and the invoked servlet got passed the request object through servlet chaining.
Just an idea, but I bet not hard to include in the SOAP product itself if others agree.
Cory
----- Original Message -----
From: Steven J. McDowall
To: soap-user@xml.apache.org
Sent: Sunday, August 20, 2000 5:07 PM
Subject: RE: Servlets and SOAP
"Provider" ?? That is an ambigious request.. :-)
Do you mean client? Of course, just use "invoke" like anyway else..
Do you mean server (which I think you do) the answer is of course again, although a bit
of work..
Most of the logic is the same (exactly) as in the RPCServlet code itself.. That really is a
"Soap Server" of a sort.. Just take the part where it decodes the soap message and ferrets
out the data it wants with DOM calls to get the elements you want..
Perhaps not totally elegant, but it should work..
-----Original Message-----
From: Cory Isaacson [mailto:cisaacson@capita2.com]
Sent: Sunday, August 20, 2000 3:30 PM
To: soap-user@xml.apache.org
Subject: Servlets and SOAP
Is there any way to have a Servlet be a provider for a SOAP call?
Cory
RE: Servlets and SOAP
Posted by "Steven J. McDowall" <sj...@visi.com>.
Cory, there was some talk of this, but I don't think anything came of it
yet..
In any case, you would not want to remove rpcrouter as an alias for
org.apache.soap.RPCRouterSevlet
as a registered sevlet name, but instead simply ADD new servlets for the new
SOAP Servlets you create
IMHO.. Thus, you won't lose the functionality if you still want/desire the
"old" rpc style.. It just depends
on which URL you invoke on the server side..
If you look in the archives (that's a joke btw :-() I think someone posted a
version of the rpc servlet which
uses "engines", one of which is the rpc engine as we know it. THe idea was
that you could easily register
other "engines" (services) on top of the main structure.. I then Jean-Loius
someone did the work..not
sure what happened though..
-Steve
-----Original Message-----
From: Cory Isaacson [mailto:cisaacson@capita2.com]
Sent: Sunday, August 20, 2000 4:37 PM
To: soap-user@xml.apache.org; sjmcdowall@visi.com
Subject: Re: Servlets and SOAP
Steve,
I do mean a server, so instead of using a provider class, invoke a
servlet. I can certainly see how I could modify the RPCServlet code to do
this, I just wondered if there were plans to make it a standard feature.
My reasoning is that I need to buffer certain things, and need access to
the servlet context/session objects to do part of the job. If I modify the
RPCServlet, then I assume that my site won't respond to other standard SOAP
calls (which may not matter in this case) but it would be neat if you could
invoke a class or a servlet as part of the architecture, and the invoked
servlet got passed the request object through servlet chaining.
Just an idea, but I bet not hard to include in the SOAP product itself if
others agree.
Cory
----- Original Message -----
From: Steven J. McDowall
To: soap-user@xml.apache.org
Sent: Sunday, August 20, 2000 5:07 PM
Subject: RE: Servlets and SOAP
"Provider" ?? That is an ambigious request.. :-)
Do you mean client? Of course, just use "invoke" like anyway else..
Do you mean server (which I think you do) the answer is of course again,
although a bit
of work..
Most of the logic is the same (exactly) as in the RPCServlet code
itself.. That really is a
"Soap Server" of a sort.. Just take the part where it decodes the soap
message and ferrets
out the data it wants with DOM calls to get the elements you want..
Perhaps not totally elegant, but it should work..
-----Original Message-----
From: Cory Isaacson [mailto:cisaacson@capita2.com]
Sent: Sunday, August 20, 2000 3:30 PM
To: soap-user@xml.apache.org
Subject: Servlets and SOAP
Is there any way to have a Servlet be a provider for a SOAP call?
Cory
RE: Servlets and SOAP
Posted by "Steven J. McDowall" <sj...@visi.com>.
Cory, there was some talk of this, but I don't think anything came of it
yet..
In any case, you would not want to remove rpcrouter as an alias for
org.apache.soap.RPCRouterSevlet
as a registered sevlet name, but instead simply ADD new servlets for the new
SOAP Servlets you create
IMHO.. Thus, you won't lose the functionality if you still want/desire the
"old" rpc style.. It just depends
on which URL you invoke on the server side..
If you look in the archives (that's a joke btw :-() I think someone posted a
version of the rpc servlet which
uses "engines", one of which is the rpc engine as we know it. THe idea was
that you could easily register
other "engines" (services) on top of the main structure.. I then Jean-Loius
someone did the work..not
sure what happened though..
-Steve
-----Original Message-----
From: Cory Isaacson [mailto:cisaacson@capita2.com]
Sent: Sunday, August 20, 2000 4:37 PM
To: soap-user@xml.apache.org; sjmcdowall@visi.com
Subject: Re: Servlets and SOAP
Steve,
I do mean a server, so instead of using a provider class, invoke a
servlet. I can certainly see how I could modify the RPCServlet code to do
this, I just wondered if there were plans to make it a standard feature.
My reasoning is that I need to buffer certain things, and need access to
the servlet context/session objects to do part of the job. If I modify the
RPCServlet, then I assume that my site won't respond to other standard SOAP
calls (which may not matter in this case) but it would be neat if you could
invoke a class or a servlet as part of the architecture, and the invoked
servlet got passed the request object through servlet chaining.
Just an idea, but I bet not hard to include in the SOAP product itself if
others agree.
Cory
----- Original Message -----
From: Steven J. McDowall
To: soap-user@xml.apache.org
Sent: Sunday, August 20, 2000 5:07 PM
Subject: RE: Servlets and SOAP
"Provider" ?? That is an ambigious request.. :-)
Do you mean client? Of course, just use "invoke" like anyway else..
Do you mean server (which I think you do) the answer is of course again,
although a bit
of work..
Most of the logic is the same (exactly) as in the RPCServlet code
itself.. That really is a
"Soap Server" of a sort.. Just take the part where it decodes the soap
message and ferrets
out the data it wants with DOM calls to get the elements you want..
Perhaps not totally elegant, but it should work..
-----Original Message-----
From: Cory Isaacson [mailto:cisaacson@capita2.com]
Sent: Sunday, August 20, 2000 3:30 PM
To: soap-user@xml.apache.org
Subject: Servlets and SOAP
Is there any way to have a Servlet be a provider for a SOAP call?
Cory
Re: Servlets and SOAP
Posted by Cory Isaacson <ci...@capita2.com>.
Steve,
I do mean a server, so instead of using a provider class, invoke a servlet. I can certainly see how I could modify the RPCServlet code to do this, I just wondered if there were plans to make it a standard feature.
My reasoning is that I need to buffer certain things, and need access to the servlet context/session objects to do part of the job. If I modify the RPCServlet, then I assume that my site won't respond to other standard SOAP calls (which may not matter in this case) but it would be neat if you could invoke a class or a servlet as part of the architecture, and the invoked servlet got passed the request object through servlet chaining.
Just an idea, but I bet not hard to include in the SOAP product itself if others agree.
Cory
----- Original Message -----
From: Steven J. McDowall
To: soap-user@xml.apache.org
Sent: Sunday, August 20, 2000 5:07 PM
Subject: RE: Servlets and SOAP
"Provider" ?? That is an ambigious request.. :-)
Do you mean client? Of course, just use "invoke" like anyway else..
Do you mean server (which I think you do) the answer is of course again, although a bit
of work..
Most of the logic is the same (exactly) as in the RPCServlet code itself.. That really is a
"Soap Server" of a sort.. Just take the part where it decodes the soap message and ferrets
out the data it wants with DOM calls to get the elements you want..
Perhaps not totally elegant, but it should work..
-----Original Message-----
From: Cory Isaacson [mailto:cisaacson@capita2.com]
Sent: Sunday, August 20, 2000 3:30 PM
To: soap-user@xml.apache.org
Subject: Servlets and SOAP
Is there any way to have a Servlet be a provider for a SOAP call?
Cory
Re: Servlets and SOAP
Posted by Cory Isaacson <ci...@capita2.com>.
Steve,
I do mean a server, so instead of using a provider class, invoke a servlet. I can certainly see how I could modify the RPCServlet code to do this, I just wondered if there were plans to make it a standard feature.
My reasoning is that I need to buffer certain things, and need access to the servlet context/session objects to do part of the job. If I modify the RPCServlet, then I assume that my site won't respond to other standard SOAP calls (which may not matter in this case) but it would be neat if you could invoke a class or a servlet as part of the architecture, and the invoked servlet got passed the request object through servlet chaining.
Just an idea, but I bet not hard to include in the SOAP product itself if others agree.
Cory
----- Original Message -----
From: Steven J. McDowall
To: soap-user@xml.apache.org
Sent: Sunday, August 20, 2000 5:07 PM
Subject: RE: Servlets and SOAP
"Provider" ?? That is an ambigious request.. :-)
Do you mean client? Of course, just use "invoke" like anyway else..
Do you mean server (which I think you do) the answer is of course again, although a bit
of work..
Most of the logic is the same (exactly) as in the RPCServlet code itself.. That really is a
"Soap Server" of a sort.. Just take the part where it decodes the soap message and ferrets
out the data it wants with DOM calls to get the elements you want..
Perhaps not totally elegant, but it should work..
-----Original Message-----
From: Cory Isaacson [mailto:cisaacson@capita2.com]
Sent: Sunday, August 20, 2000 3:30 PM
To: soap-user@xml.apache.org
Subject: Servlets and SOAP
Is there any way to have a Servlet be a provider for a SOAP call?
Cory
RE: Servlets and SOAP
Posted by "Steven J. McDowall" <sj...@visi.com>.
"Provider" ?? That is an ambigious request.. :-)
Do you mean client? Of course, just use "invoke" like anyway else..
Do you mean server (which I think you do) the answer is of course again,
although a bit
of work..
Most of the logic is the same (exactly) as in the RPCServlet code itself..
That really is a
"Soap Server" of a sort.. Just take the part where it decodes the soap
message and ferrets
out the data it wants with DOM calls to get the elements you want..
Perhaps not totally elegant, but it should work..
-----Original Message-----
From: Cory Isaacson [mailto:cisaacson@capita2.com]
Sent: Sunday, August 20, 2000 3:30 PM
To: soap-user@xml.apache.org
Subject: Servlets and SOAP
Is there any way to have a Servlet be a provider for a SOAP call?
Cory
RE: Servlets and SOAP
Posted by "Steven J. McDowall" <sj...@visi.com>.
"Provider" ?? That is an ambigious request.. :-)
Do you mean client? Of course, just use "invoke" like anyway else..
Do you mean server (which I think you do) the answer is of course again,
although a bit
of work..
Most of the logic is the same (exactly) as in the RPCServlet code itself..
That really is a
"Soap Server" of a sort.. Just take the part where it decodes the soap
message and ferrets
out the data it wants with DOM calls to get the elements you want..
Perhaps not totally elegant, but it should work..
-----Original Message-----
From: Cory Isaacson [mailto:cisaacson@capita2.com]
Sent: Sunday, August 20, 2000 3:30 PM
To: soap-user@xml.apache.org
Subject: Servlets and SOAP
Is there any way to have a Servlet be a provider for a SOAP call?
Cory