You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by Clay Luther <cl...@cisco.com> on 2001/04/06 22:44:12 UTC
Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
I was wondering if anyone had or knows of an example of using Apache-SOAP to
write SOAP-aware servlets without using the RpcRouterServlet architecture,
but still allows me to leverage the SOAP toolkit (rather than, say, parsing
the SOAP envelopes by hand).
Thanks.
---
Clay
Cisco Systems, Inc.
claycle@cisco.com
(972) 813-5004
J'ai un regret: je ne regrette rien.
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
It seems to me that you're defining your RPC protocol over SOAP
messaging which is different form SOAP-RPC.
You can do that with Apache SOAP .. you have to use the message
API to get access to the SOAP envelope directly and implement
whatever you want from there. The message sample shows an (silly)
example.
Sanjiva.
----- Original Message -----
From: "Clay Luther" <cl...@cisco.com>
To: <so...@xml.apache.org>
Sent: Friday, April 13, 2001 4:21 PM
Subject: Re: Examples of Writing SOAP Servlets That ARE NOT using
RPCRouterServlet
> > Wouter
>
> > Hmm, so you want to let Apache-SOAP handle the XML parsing, the
> interpretation
> > of the SOAP envelope, its header and body, but you want the body to just
> > contain XML.
> >
> > I think what you're looking for is a way to pass an XML element as a
> request
> > or response. Apache-SOAP supports passing DOM elements as SOAP bodies.
> Take
> > a look at the address book sample; it uses literal XML in precisely that
> manner.
>
>
> I wouldn't be so sure that I'd want to follow the addressbook example,
since
> it is still based off of RPCRouterServlet, and RPCRouterServlet is my
> problem. Look, here's what my SOAP messages look like:
>
> <SOAP-ENV:Envelope>
> <SOAP-ENV:Body>
> <axlapi:axl type="axlapi:request">
> <axlapi:request type="axlapi:getPhoneByDN">
> <axlapi:directoryNumber>35004</axlapi:directoryNumber>
> </axlapi:request>
> </axlapi:axl>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
> and I send back a response that looks like:
>
> <SOAP-ENV:Envelope>
> <SOAP-ENV:Body>
> <axlapi:axl type="axlapi:response">
> <axlapi:response type="getPhoneByDNResponse">
> <axl:phone>
> <axl:directoryNumber>35004</axl:directoryNumber>
> <axl:currentUser>
> <axl:firstame>Tom</axl:firstname>
> <axl:lastname>Jones</axl:lastname>
> </axl:currentUser>
> </axl:phone>
> </axlapi:response>
> </axlapi:axl>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
>
> At first, I thought I could use the RPCRouterServlet mechanism to help me
> with this. But I cannot because I cannot figure a way, when building the
> Call object in the client, to add the additional attribute(s) (xsi:type,
in
> this case) to the Call's methodname. We use schema, via types, to build
all
> the requests and responses first. So the actual method being called
> ("getPhoneByDN") is defined as a schema type (<complexType
> name="getPhoneByDN">), which is based off an abstract request type.
>
> So, I'm back to my original request. I want to use Apache-SOAP, but I
want
> to use it the way I want to use it, not the way RPCRouterServlet wants me
to
> use it. I want to say: "make me an Envelope, make me a Body, here's the
> payload, send it" on the client side, and "just give me the payload, no
> questions asked, quickly now" on the server side. And I don't want to use
> DOM because SPEED is of the essence.
>
> I think what were arriving at is that Apache-SOAP won't work for me and
> we'll have to roll our own thing.
>
> ---
> Clay
> Cisco Systems, Inc.
> claycle@cisco.com
> (972) 813-5004
>
> J'ai un regret: je ne regrette rien.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
It seems to me that you're defining your RPC protocol over SOAP
messaging which is different form SOAP-RPC.
You can do that with Apache SOAP .. you have to use the message
API to get access to the SOAP envelope directly and implement
whatever you want from there. The message sample shows an (silly)
example.
Sanjiva.
----- Original Message -----
From: "Clay Luther" <cl...@cisco.com>
To: <so...@xml.apache.org>
Sent: Friday, April 13, 2001 4:21 PM
Subject: Re: Examples of Writing SOAP Servlets That ARE NOT using
RPCRouterServlet
> > Wouter
>
> > Hmm, so you want to let Apache-SOAP handle the XML parsing, the
> interpretation
> > of the SOAP envelope, its header and body, but you want the body to just
> > contain XML.
> >
> > I think what you're looking for is a way to pass an XML element as a
> request
> > or response. Apache-SOAP supports passing DOM elements as SOAP bodies.
> Take
> > a look at the address book sample; it uses literal XML in precisely that
> manner.
>
>
> I wouldn't be so sure that I'd want to follow the addressbook example,
since
> it is still based off of RPCRouterServlet, and RPCRouterServlet is my
> problem. Look, here's what my SOAP messages look like:
>
> <SOAP-ENV:Envelope>
> <SOAP-ENV:Body>
> <axlapi:axl type="axlapi:request">
> <axlapi:request type="axlapi:getPhoneByDN">
> <axlapi:directoryNumber>35004</axlapi:directoryNumber>
> </axlapi:request>
> </axlapi:axl>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
> and I send back a response that looks like:
>
> <SOAP-ENV:Envelope>
> <SOAP-ENV:Body>
> <axlapi:axl type="axlapi:response">
> <axlapi:response type="getPhoneByDNResponse">
> <axl:phone>
> <axl:directoryNumber>35004</axl:directoryNumber>
> <axl:currentUser>
> <axl:firstame>Tom</axl:firstname>
> <axl:lastname>Jones</axl:lastname>
> </axl:currentUser>
> </axl:phone>
> </axlapi:response>
> </axlapi:axl>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
>
> At first, I thought I could use the RPCRouterServlet mechanism to help me
> with this. But I cannot because I cannot figure a way, when building the
> Call object in the client, to add the additional attribute(s) (xsi:type,
in
> this case) to the Call's methodname. We use schema, via types, to build
all
> the requests and responses first. So the actual method being called
> ("getPhoneByDN") is defined as a schema type (<complexType
> name="getPhoneByDN">), which is based off an abstract request type.
>
> So, I'm back to my original request. I want to use Apache-SOAP, but I
want
> to use it the way I want to use it, not the way RPCRouterServlet wants me
to
> use it. I want to say: "make me an Envelope, make me a Body, here's the
> payload, send it" on the client side, and "just give me the payload, no
> questions asked, quickly now" on the server side. And I don't want to use
> DOM because SPEED is of the essence.
>
> I think what were arriving at is that Apache-SOAP won't work for me and
> we'll have to roll our own thing.
>
> ---
> Clay
> Cisco Systems, Inc.
> claycle@cisco.com
> (972) 813-5004
>
> J'ai un regret: je ne regrette rien.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Clay Luther <cl...@cisco.com>.
> Wouter
> Hmm, so you want to let Apache-SOAP handle the XML parsing, the
interpretation
> of the SOAP envelope, its header and body, but you want the body to just
> contain XML.
>
> I think what you're looking for is a way to pass an XML element as a
request
> or response. Apache-SOAP supports passing DOM elements as SOAP bodies.
Take
> a look at the address book sample; it uses literal XML in precisely that
manner.
I wouldn't be so sure that I'd want to follow the addressbook example, since
it is still based off of RPCRouterServlet, and RPCRouterServlet is my
problem. Look, here's what my SOAP messages look like:
<SOAP-ENV:Envelope>
<SOAP-ENV:Body>
<axlapi:axl type="axlapi:request">
<axlapi:request type="axlapi:getPhoneByDN">
<axlapi:directoryNumber>35004</axlapi:directoryNumber>
</axlapi:request>
</axlapi:axl>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
and I send back a response that looks like:
<SOAP-ENV:Envelope>
<SOAP-ENV:Body>
<axlapi:axl type="axlapi:response">
<axlapi:response type="getPhoneByDNResponse">
<axl:phone>
<axl:directoryNumber>35004</axl:directoryNumber>
<axl:currentUser>
<axl:firstame>Tom</axl:firstname>
<axl:lastname>Jones</axl:lastname>
</axl:currentUser>
</axl:phone>
</axlapi:response>
</axlapi:axl>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
At first, I thought I could use the RPCRouterServlet mechanism to help me
with this. But I cannot because I cannot figure a way, when building the
Call object in the client, to add the additional attribute(s) (xsi:type, in
this case) to the Call's methodname. We use schema, via types, to build all
the requests and responses first. So the actual method being called
("getPhoneByDN") is defined as a schema type (<complexType
name="getPhoneByDN">), which is based off an abstract request type.
So, I'm back to my original request. I want to use Apache-SOAP, but I want
to use it the way I want to use it, not the way RPCRouterServlet wants me to
use it. I want to say: "make me an Envelope, make me a Body, here's the
payload, send it" on the client side, and "just give me the payload, no
questions asked, quickly now" on the server side. And I don't want to use
DOM because SPEED is of the essence.
I think what were arriving at is that Apache-SOAP won't work for me and
we'll have to roll our own thing.
---
Clay
Cisco Systems, Inc.
claycle@cisco.com
(972) 813-5004
J'ai un regret: je ne regrette rien.
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Clay Luther <cl...@cisco.com>.
> Wouter
> Hmm, so you want to let Apache-SOAP handle the XML parsing, the
interpretation
> of the SOAP envelope, its header and body, but you want the body to just
> contain XML.
>
> I think what you're looking for is a way to pass an XML element as a
request
> or response. Apache-SOAP supports passing DOM elements as SOAP bodies.
Take
> a look at the address book sample; it uses literal XML in precisely that
manner.
I wouldn't be so sure that I'd want to follow the addressbook example, since
it is still based off of RPCRouterServlet, and RPCRouterServlet is my
problem. Look, here's what my SOAP messages look like:
<SOAP-ENV:Envelope>
<SOAP-ENV:Body>
<axlapi:axl type="axlapi:request">
<axlapi:request type="axlapi:getPhoneByDN">
<axlapi:directoryNumber>35004</axlapi:directoryNumber>
</axlapi:request>
</axlapi:axl>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
and I send back a response that looks like:
<SOAP-ENV:Envelope>
<SOAP-ENV:Body>
<axlapi:axl type="axlapi:response">
<axlapi:response type="getPhoneByDNResponse">
<axl:phone>
<axl:directoryNumber>35004</axl:directoryNumber>
<axl:currentUser>
<axl:firstame>Tom</axl:firstname>
<axl:lastname>Jones</axl:lastname>
</axl:currentUser>
</axl:phone>
</axlapi:response>
</axlapi:axl>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
At first, I thought I could use the RPCRouterServlet mechanism to help me
with this. But I cannot because I cannot figure a way, when building the
Call object in the client, to add the additional attribute(s) (xsi:type, in
this case) to the Call's methodname. We use schema, via types, to build all
the requests and responses first. So the actual method being called
("getPhoneByDN") is defined as a schema type (<complexType
name="getPhoneByDN">), which is based off an abstract request type.
So, I'm back to my original request. I want to use Apache-SOAP, but I want
to use it the way I want to use it, not the way RPCRouterServlet wants me to
use it. I want to say: "make me an Envelope, make me a Body, here's the
payload, send it" on the client side, and "just give me the payload, no
questions asked, quickly now" on the server side. And I don't want to use
DOM because SPEED is of the essence.
I think what were arriving at is that Apache-SOAP won't work for me and
we'll have to roll our own thing.
---
Clay
Cisco Systems, Inc.
claycle@cisco.com
(972) 813-5004
J'ai un regret: je ne regrette rien.
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Wouter Cloetens <wo...@mind.be>.
On Wed, Apr 11, 2001 at 10:59:55AM -0500, Clay Luther wrote:
> > Using either/both of them will get Apache-SOAP to invoke the XML parser.
> > I understand that that's exactly what you wanted to avoid? Hence, you don't
> > want to use these methods at all. You want to copy their code into your code,
> > and strip off the final call to unMarshall().
>
> Well, *sort* of. I want Apache-SOAP to handle the SOAP stuff and let me
> handle the non-SOAP stuff (ie, the content of the SOAP message's body).
> Thus, I want to go as far as Envelope.getBody() and
> Body.getBodyEntries().elementAt(0), since this will be my XML-based API
> message.
>
> I don't want to have to parse the SOAP envelope.
Hmm, so you want to let Apache-SOAP handle the XML parsing, the interpretation
of the SOAP envelope, its header and body, but you want the body to just
contain XML.
I think what you're looking for is a way to pass an XML element as a request
or response. Apache-SOAP supports passing DOM elements as SOAP bodies. Take
a look at the address book sample; it uses literal XML in precisely that manner.
You shouldn't have to mess with the transport layer at all...
bfn, Wouter
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Wouter Cloetens <wo...@mind.be>.
On Wed, Apr 11, 2001 at 10:59:55AM -0500, Clay Luther wrote:
> > Using either/both of them will get Apache-SOAP to invoke the XML parser.
> > I understand that that's exactly what you wanted to avoid? Hence, you don't
> > want to use these methods at all. You want to copy their code into your code,
> > and strip off the final call to unMarshall().
>
> Well, *sort* of. I want Apache-SOAP to handle the SOAP stuff and let me
> handle the non-SOAP stuff (ie, the content of the SOAP message's body).
> Thus, I want to go as far as Envelope.getBody() and
> Body.getBodyEntries().elementAt(0), since this will be my XML-based API
> message.
>
> I don't want to have to parse the SOAP envelope.
Hmm, so you want to let Apache-SOAP handle the XML parsing, the interpretation
of the SOAP envelope, its header and body, but you want the body to just
contain XML.
I think what you're looking for is a way to pass an XML element as a request
or response. Apache-SOAP supports passing DOM elements as SOAP bodies. Take
a look at the address book sample; it uses literal XML in precisely that manner.
You shouldn't have to mess with the transport layer at all...
bfn, Wouter
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Clay Luther <cl...@cisco.com>.
> Wouter
> Using either/both of them will get Apache-SOAP to invoke the XML parser.
> I understand that that's exactly what you wanted to avoid? Hence, you
don't
> want to use these methods at all. You want to copy their code into your
code,
> and strip off the final call to unMarshall().
Well, *sort* of. I want Apache-SOAP to handle the SOAP stuff and let me
handle the non-SOAP stuff (ie, the content of the SOAP message's body).
Thus, I want to go as far as Envelope.getBody() and
Body.getBodyEntries().elementAt(0), since this will be my XML-based API
message.
I don't want to have to parse the SOAP envelope.
---
Clay
Cisco Systems, Inc.
claycle@cisco.com
(972) 813-5004
J'ai un regret: je ne regrette rien.
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Clay Luther <cl...@cisco.com>.
> Wouter
> Using either/both of them will get Apache-SOAP to invoke the XML parser.
> I understand that that's exactly what you wanted to avoid? Hence, you
don't
> want to use these methods at all. You want to copy their code into your
code,
> and strip off the final call to unMarshall().
Well, *sort* of. I want Apache-SOAP to handle the SOAP stuff and let me
handle the non-SOAP stuff (ie, the content of the SOAP message's body).
Thus, I want to go as far as Envelope.getBody() and
Body.getBodyEntries().elementAt(0), since this will be my XML-based API
message.
I don't want to have to parse the SOAP envelope.
---
Clay
Cisco Systems, Inc.
claycle@cisco.com
(972) 813-5004
J'ai un regret: je ne regrette rien.
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Wouter Cloetens <wo...@mind.be>.
On Tue, Apr 10, 2001 at 12:43:08PM -0500, Clay Luther wrote:
> > Wouter
>
>
> We actually started to talk apples and oranges here. Let's get back on
> track:
>
>
> > > Unfortunately, ServerUtils.readEnvelopeFromInputStream() has default
> > > access.
> > > I posted about this Friday, but nobody seems to have seen it.
> >
> > I saw it. How's that going to keep you from copying and pasting its source
> > code? ;-)
>
> I meant to say "ServerHTTPUtils.readEnvelopeFromRequest() has default
> access." This is bad, because, as you say...
>
>
> > The reason behind its access modifiers is that you're supposed to subclass > it
> > for every type of transport protocol. Or something. I don't know what
> whoever
>
> Well, I'm using HTTP as the transport protocol, so I would like to use
> ServerHTTPUtils just like MessageRouterServlet does. But I *can't* (inside
> my own package) because this critical routine is defined default, not
> public. That's just bad.
Ah. Well. The transport-independent ServerUtils.readEnvelopeFromInputStream()
is public. The HTTP-specific ServerHTTPUtils.readEnvelopeFromRequest() has
package visibility, because it's only for use by the server-side HTTP handling
code (= servlets) in the same package.
Using either/both of them will get Apache-SOAP to invoke the XML parser.
I understand that that's exactly what you wanted to avoid? Hence, you don't
want to use these methods at all. You want to copy their code into your code,
and strip off the final call to unMarshall().
> So, to get around it, I created my own org.apache.soap.server.http package,
> and added ServerHTTPUtils2, which simply presents readEnvelopeFromRequest()
> as public static and passes the call through to ServerHTTPUtils. It works,
> it doesn't make me copy code that might change underneath me (poor
> programming practice), and it appears to work nicely now.
>
> I just wish the Apache-SOAP programmers were a *little* more diligent with
> their javadoc comments...that would help, too.
Hey, those methods have a fair amount of info in them. Though I'll agree
that the source code documentation could've been better, I believe that
what's really missing is a hitch-hiker's guide (well, ok, an "architecture
document" with "design diagrammes") to how it all fits together.
> > (might be me) did that was thinking at the time he wrote it... You don't
> need
> > it unless if you're changing your mind about letting the existing
> Apache-SOAP
> > do the XML parsing bit, in which case you can just stick with the way the
> > servlet invokes it.
>
>
> As slow as Apache-SOAP RpcRouterServlet already is? Gads...it takes long
> enough now just to echo the XML response back to me. I hesitate to allow
> Apache-SOAP to parse any more of my XML than I need it to ;-) ;-) ;-).
>
> ---
> Clay
> Cisco Systems, Inc.
> claycle@cisco.com
> (972) 813-5004
>
> J'ai un regret: je ne regrette rien.
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Wouter Cloetens <wo...@mind.be>.
On Tue, Apr 10, 2001 at 12:43:08PM -0500, Clay Luther wrote:
> > Wouter
>
>
> We actually started to talk apples and oranges here. Let's get back on
> track:
>
>
> > > Unfortunately, ServerUtils.readEnvelopeFromInputStream() has default
> > > access.
> > > I posted about this Friday, but nobody seems to have seen it.
> >
> > I saw it. How's that going to keep you from copying and pasting its source
> > code? ;-)
>
> I meant to say "ServerHTTPUtils.readEnvelopeFromRequest() has default
> access." This is bad, because, as you say...
>
>
> > The reason behind its access modifiers is that you're supposed to subclass > it
> > for every type of transport protocol. Or something. I don't know what
> whoever
>
> Well, I'm using HTTP as the transport protocol, so I would like to use
> ServerHTTPUtils just like MessageRouterServlet does. But I *can't* (inside
> my own package) because this critical routine is defined default, not
> public. That's just bad.
Ah. Well. The transport-independent ServerUtils.readEnvelopeFromInputStream()
is public. The HTTP-specific ServerHTTPUtils.readEnvelopeFromRequest() has
package visibility, because it's only for use by the server-side HTTP handling
code (= servlets) in the same package.
Using either/both of them will get Apache-SOAP to invoke the XML parser.
I understand that that's exactly what you wanted to avoid? Hence, you don't
want to use these methods at all. You want to copy their code into your code,
and strip off the final call to unMarshall().
> So, to get around it, I created my own org.apache.soap.server.http package,
> and added ServerHTTPUtils2, which simply presents readEnvelopeFromRequest()
> as public static and passes the call through to ServerHTTPUtils. It works,
> it doesn't make me copy code that might change underneath me (poor
> programming practice), and it appears to work nicely now.
>
> I just wish the Apache-SOAP programmers were a *little* more diligent with
> their javadoc comments...that would help, too.
Hey, those methods have a fair amount of info in them. Though I'll agree
that the source code documentation could've been better, I believe that
what's really missing is a hitch-hiker's guide (well, ok, an "architecture
document" with "design diagrammes") to how it all fits together.
> > (might be me) did that was thinking at the time he wrote it... You don't
> need
> > it unless if you're changing your mind about letting the existing
> Apache-SOAP
> > do the XML parsing bit, in which case you can just stick with the way the
> > servlet invokes it.
>
>
> As slow as Apache-SOAP RpcRouterServlet already is? Gads...it takes long
> enough now just to echo the XML response back to me. I hesitate to allow
> Apache-SOAP to parse any more of my XML than I need it to ;-) ;-) ;-).
>
> ---
> Clay
> Cisco Systems, Inc.
> claycle@cisco.com
> (972) 813-5004
>
> J'ai un regret: je ne regrette rien.
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Clay Luther <cl...@cisco.com>.
> Wouter
We actually started to talk apples and oranges here. Let's get back on
track:
> > Unfortunately, ServerUtils.readEnvelopeFromInputStream() has default
access.
> > I posted about this Friday, but nobody seems to have seen it.
>
> I saw it. How's that going to keep you from copying and pasting its source
> code? ;-)
I meant to say "ServerHTTPUtils.readEnvelopeFromRequest() has default
access." This is bad, because, as you say...
> The reason behind its access modifiers is that you're supposed to subclass
it
> for every type of transport protocol. Or something. I don't know what
whoever
Well, I'm using HTTP as the transport protocol, so I would like to use
ServerHTTPUtils just like MessageRouterServlet does. But I *can't* (inside
my own package) because this critical routine is defined default, not
public. That's just bad.
So, to get around it, I created my own org.apache.soap.server.http package,
and added ServerHTTPUtils2, which simply presents readEnvelopeFromRequest()
as public static and passes the call through to ServerHTTPUtils. It works,
it doesn't make me copy code that might change underneath me (poor
programming practice), and it appears to work nicely now.
I just wish the Apache-SOAP programmers were a *little* more diligent with
their javadoc comments...that would help, too.
> (might be me) did that was thinking at the time he wrote it... You don't
need
> it unless if you're changing your mind about letting the existing
Apache-SOAP
> do the XML parsing bit, in which case you can just stick with the way the
> servlet invokes it.
As slow as Apache-SOAP RpcRouterServlet already is? Gads...it takes long
enough now just to echo the XML response back to me. I hesitate to allow
Apache-SOAP to parse any more of my XML than I need it to ;-) ;-) ;-).
---
Clay
Cisco Systems, Inc.
claycle@cisco.com
(972) 813-5004
J'ai un regret: je ne regrette rien.
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Clay Luther <cl...@cisco.com>.
> Wouter
We actually started to talk apples and oranges here. Let's get back on
track:
> > Unfortunately, ServerUtils.readEnvelopeFromInputStream() has default
access.
> > I posted about this Friday, but nobody seems to have seen it.
>
> I saw it. How's that going to keep you from copying and pasting its source
> code? ;-)
I meant to say "ServerHTTPUtils.readEnvelopeFromRequest() has default
access." This is bad, because, as you say...
> The reason behind its access modifiers is that you're supposed to subclass
it
> for every type of transport protocol. Or something. I don't know what
whoever
Well, I'm using HTTP as the transport protocol, so I would like to use
ServerHTTPUtils just like MessageRouterServlet does. But I *can't* (inside
my own package) because this critical routine is defined default, not
public. That's just bad.
So, to get around it, I created my own org.apache.soap.server.http package,
and added ServerHTTPUtils2, which simply presents readEnvelopeFromRequest()
as public static and passes the call through to ServerHTTPUtils. It works,
it doesn't make me copy code that might change underneath me (poor
programming practice), and it appears to work nicely now.
I just wish the Apache-SOAP programmers were a *little* more diligent with
their javadoc comments...that would help, too.
> (might be me) did that was thinking at the time he wrote it... You don't
need
> it unless if you're changing your mind about letting the existing
Apache-SOAP
> do the XML parsing bit, in which case you can just stick with the way the
> servlet invokes it.
As slow as Apache-SOAP RpcRouterServlet already is? Gads...it takes long
enough now just to echo the XML response back to me. I hesitate to allow
Apache-SOAP to parse any more of my XML than I need it to ;-) ;-) ;-).
---
Clay
Cisco Systems, Inc.
claycle@cisco.com
(972) 813-5004
J'ai un regret: je ne regrette rien.
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Wouter Cloetens <wo...@mind.be>.
On Mon, Apr 09, 2001 at 11:37:43AM -0500, Clay Luther wrote:
> > What you can do is make a copy of MessageRouterServlet and cut out the
> > functionality you don't need. The XML parser is invoked in the last line of
> > ServerUtils.readEnvelopeFromInputStream(). Copy that method without the
> > last line in your servlet, and you'll be at the point where you have a
> > request SOAPContext object, from which you can extract the root part to
> > get to the request body.
>
> Unfortunately, ServerUtils.readEnvelopeFromInputStream() has default access.
> I posted about this Friday, but nobody seems to have seen it.
I saw it. How's that going to keep you from copying and pasting its source
code? ;-)
The reason behind its access modifiers is that you're supposed to subclass it
for every type of transport protocol. Or something. I don't know what whoever
(might be me) did that was thinking at the time he wrote it... You don't need
it unless if you're changing your mind about letting the existing Apache-SOAP
do the XML parsing bit, in which case you can just stick with the way the
servlet invokes it.
bfn, Wouter
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Wouter Cloetens <wo...@mind.be>.
On Mon, Apr 09, 2001 at 11:37:43AM -0500, Clay Luther wrote:
> > What you can do is make a copy of MessageRouterServlet and cut out the
> > functionality you don't need. The XML parser is invoked in the last line of
> > ServerUtils.readEnvelopeFromInputStream(). Copy that method without the
> > last line in your servlet, and you'll be at the point where you have a
> > request SOAPContext object, from which you can extract the root part to
> > get to the request body.
>
> Unfortunately, ServerUtils.readEnvelopeFromInputStream() has default access.
> I posted about this Friday, but nobody seems to have seen it.
I saw it. How's that going to keep you from copying and pasting its source
code? ;-)
The reason behind its access modifiers is that you're supposed to subclass it
for every type of transport protocol. Or something. I don't know what whoever
(might be me) did that was thinking at the time he wrote it... You don't need
it unless if you're changing your mind about letting the existing Apache-SOAP
do the XML parsing bit, in which case you can just stick with the way the
servlet invokes it.
bfn, Wouter
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Clay Luther <cl...@cisco.com>.
> What you can do is make a copy of MessageRouterServlet and cut out the
> functionality you don't need. The XML parser is invoked in the last line
of
> ServerUtils.readEnvelopeFromInputStream(). Copy that method without the
> last line in your servlet, and you'll be at the point where you have a
> request SOAPContext object, from which you can extract the root part to
> get to the request body.
Unfortunately, ServerUtils.readEnvelopeFromInputStream() has default access.
I posted about this Friday, but nobody seems to have seen it.
---
Clay
Cisco Systems, Inc.
claycle@cisco.com
(972) 813-5004
J'ai un regret: je ne regrette rien.
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Clay Luther <cl...@cisco.com>.
> What you can do is make a copy of MessageRouterServlet and cut out the
> functionality you don't need. The XML parser is invoked in the last line
of
> ServerUtils.readEnvelopeFromInputStream(). Copy that method without the
> last line in your servlet, and you'll be at the point where you have a
> request SOAPContext object, from which you can extract the root part to
> get to the request body.
Unfortunately, ServerUtils.readEnvelopeFromInputStream() has default access.
I posted about this Friday, but nobody seems to have seen it.
---
Clay
Cisco Systems, Inc.
claycle@cisco.com
(972) 813-5004
J'ai un regret: je ne regrette rien.
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Wouter Cloetens <wo...@mind.be>.
Hmm, so you don't want the Apache-SOAP code to parse the XML. If you'll let
it do that, the Messaging servlet is the right approach.
What you're left with, then, is only the transport layer. You can still use
the SOAPContext object to represent a request and a response in an
HTTP-independent, MIME multipart-aware fashion, and TransportMessage to
handle the translation from that to bytes on the wire, aware of character
set encodings.
What you can do is make a copy of MessageRouterServlet and cut out the
functionality you don't need. The XML parser is invoked in the last line of
ServerUtils.readEnvelopeFromInputStream(). Copy that method without the
last line in your servlet, and you'll be at the point where you have a
request SOAPContext object, from which you can extract the root part to
get to the request body.
For the response, you can leave everything behind the
"provider.invoke( reqCtx, resCtx );" line in MessageRouterServlet. Just
have a valid response SOAPContext object (easily constructed, see the
messaging samples) ready.
bfn, Wouter
On Fri, Apr 06, 2001 at 04:19:10PM -0500, Clay Luther wrote:
> Hmmm...well, a cursory glance at the code it seems very similar to
> RpcRouterServlet; ie., it relies on the Apache-SOAP infrastructure (like
> ServiceProvider). I was looking for something a little more...streamlined.
>
> Bascially, we have an API already defined in XML. We want to transmit the
> API messages inside SOAP messages. The API does not conform the the RPC
> mechanism used by RpcRouterServlet.
>
> I'm looking for a way to:
>
> 1) Quickly validate that the incoming request is a "well-formed" SOAP
> message.
> 2) Extract the Envelope's Body as an (XML) Document and hand it to my API
> SAX parser, which returns a (XML) Document as its result.
> 3) Quickly construct response Envelopes that contain the parser's returned
> (XML) Documents.
>
> We've implemented this in C++ using MS SOAP. We now need to implement it in
> Apache-SOAP and right now I feel very straight-jacketed by the current
> architecture all Apache-SOAP examples and articles seemed to be coded
> towards.
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Wouter Cloetens <wo...@mind.be>.
Hmm, so you don't want the Apache-SOAP code to parse the XML. If you'll let
it do that, the Messaging servlet is the right approach.
What you're left with, then, is only the transport layer. You can still use
the SOAPContext object to represent a request and a response in an
HTTP-independent, MIME multipart-aware fashion, and TransportMessage to
handle the translation from that to bytes on the wire, aware of character
set encodings.
What you can do is make a copy of MessageRouterServlet and cut out the
functionality you don't need. The XML parser is invoked in the last line of
ServerUtils.readEnvelopeFromInputStream(). Copy that method without the
last line in your servlet, and you'll be at the point where you have a
request SOAPContext object, from which you can extract the root part to
get to the request body.
For the response, you can leave everything behind the
"provider.invoke( reqCtx, resCtx );" line in MessageRouterServlet. Just
have a valid response SOAPContext object (easily constructed, see the
messaging samples) ready.
bfn, Wouter
On Fri, Apr 06, 2001 at 04:19:10PM -0500, Clay Luther wrote:
> Hmmm...well, a cursory glance at the code it seems very similar to
> RpcRouterServlet; ie., it relies on the Apache-SOAP infrastructure (like
> ServiceProvider). I was looking for something a little more...streamlined.
>
> Bascially, we have an API already defined in XML. We want to transmit the
> API messages inside SOAP messages. The API does not conform the the RPC
> mechanism used by RpcRouterServlet.
>
> I'm looking for a way to:
>
> 1) Quickly validate that the incoming request is a "well-formed" SOAP
> message.
> 2) Extract the Envelope's Body as an (XML) Document and hand it to my API
> SAX parser, which returns a (XML) Document as its result.
> 3) Quickly construct response Envelopes that contain the parser's returned
> (XML) Documents.
>
> We've implemented this in C++ using MS SOAP. We now need to implement it in
> Apache-SOAP and right now I feel very straight-jacketed by the current
> architecture all Apache-SOAP examples and articles seemed to be coded
> towards.
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
A Apache-SOAP Bug? (was Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet)
Posted by Clay Luther <cl...@cisco.com>.
BTW, if you meant copy and rewrite it, this is made rather difficult because
org.apache.soap.server.http.ServerHTTPUtils.readEnvelopeFromRequest() is
defined with default access. Shouldn't it be public static?
---
Clay
Cisco Systems, Inc.
claycle@cisco.com
(972) 813-5004
J'ai un regret: je ne regrette rien.
----- Original Message -----
From: "Clay Luther" <cl...@cisco.com>
To: <so...@xml.apache.org>
Sent: Friday, April 06, 2001 6:06 PM
Subject: Re: Examples of Writing SOAP Servlets That ARE NOT using
RPCRouterServlet
> Are you saying rewrite/copy MessageRouterServlet, or are you saying use
> MessageRouterServlet written as is?
>
> ---
> Clay
> Cisco Systems, Inc.
> claycle@cisco.com
> (972) 813-5004
>
> J'ai un regret: je ne regrette rien.
>
>
> ----- Original Message -----
> From: "Wei Qian" <We...@oracle.com>
> To: <so...@xml.apache.org>
> Sent: Friday, April 06, 2001 4:57 PM
> Subject: RE: Examples of Writing SOAP Servlets That ARE NOT using
> RPCRouterServlet
>
>
> > Hi:
> >
> > A couple of days ago, i posted a message on how to extract
> > XML content from a SOAP Envelope. Basically, you need to
> > put it inside of MessageRouterServlet, so that it can
> > forward the XML request to your own logic instead of
> > call SOAP Proivder's API. After getting the XML response
> > from you application, put it back by
> >
> > resCtx.setRootPart( "<Your XML response/>",
> > Constants.HEADERVAL_CONTENT_TYPE_UTF8);
> >
> > I have done so with pure text XML request and response.
> > If you need to pass objects, then you can borrow
> > SOAP's serializer and deserializer, or you have to
> > write your own de/serializer.
> >
> > Hope it helps,
> >
> > Cheers,
> >
> > -Wei
> >
> > -----Original Message-----
> > From: Clay Luther [mailto:claycle@cisco.com]
> > Sent: Friday, April 06, 2001 5:19 PM
> > To: soap-user@xml.apache.org
> > Subject: Re: Examples of Writing SOAP Servlets That ARE NOT using
> > RPCRouterServlet
> >
> >
> > Hmmm...well, a cursory glance at the code it seems very similar to
> > RpcRouterServlet; ie., it relies on the Apache-SOAP infrastructure (like
> > ServiceProvider). I was looking for something a little
> more...streamlined.
> >
> > Bascially, we have an API already defined in XML. We want to transmit
the
> > API messages inside SOAP messages. The API does not conform the the RPC
> > mechanism used by RpcRouterServlet.
> >
> > I'm looking for a way to:
> >
> > 1) Quickly validate that the incoming request is a "well-formed" SOAP
> > message.
> > 2) Extract the Envelope's Body as an (XML) Document and hand it to my
API
> > SAX parser, which returns a (XML) Document as its result.
> > 3) Quickly construct response Envelopes that contain the parser's
returned
> > (XML) Documents.
> >
> > We've implemented this in C++ using MS SOAP. We now need to implement
it
> in
> > Apache-SOAP and right now I feel very straight-jacketed by the current
> > architecture all Apache-SOAP examples and articles seemed to be coded
> > towards.
> >
> > ---
> > Clay
> > Cisco Systems, Inc.
> > claycle@cisco.com
> > (972) 813-5004
> >
> > J'ai un regret: je ne regrette rien.
> >
> >
> > ----- Original Message -----
> > From: "Wei Qian" <We...@oracle.com>
> > To: <so...@xml.apache.org>
> > Sent: Friday, April 06, 2001 4:07 PM
> > Subject: RE: Examples of Writing SOAP Servlets That ARE NOT using
> > RPCRouterServlet
> >
> >
> > > Hi:
> > >
> > > If you like, you can use MessageRouterServlet instead.
> > >
> > > Cheers,
> > >
> > > -Wei
> > >
> > > -----Original Message-----
> > > From: Clay Luther [mailto:claycle@cisco.com]
> > > Sent: Friday, April 06, 2001 4:44 PM
> > > To: Soap-User
> > > Subject: Examples of Writing SOAP Servlets That ARE NOT using
> > > RPCRouterServlet
> > >
> > >
> > > I was wondering if anyone had or knows of an example of using
> Apache-SOAP
> > to
> > > write SOAP-aware servlets without using the RpcRouterServlet
> architecture,
> > > but still allows me to leverage the SOAP toolkit (rather than, say,
> > parsing
> > > the SOAP envelopes by hand).
> > >
> > > Thanks.
> > >
> > > ---
> > > Clay
> > > Cisco Systems, Inc.
> > > claycle@cisco.com
> > > (972) 813-5004
> > >
> > > J'ai un regret: je ne regrette rien.
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > > For additional commands, email: soap-user-help@xml.apache.org
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > > For additional commands, email: soap-user-help@xml.apache.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > For additional commands, email: soap-user-help@xml.apache.org
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > For additional commands, email: soap-user-help@xml.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
A Apache-SOAP Bug? (was Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet)
Posted by Clay Luther <cl...@cisco.com>.
BTW, if you meant copy and rewrite it, this is made rather difficult because
org.apache.soap.server.http.ServerHTTPUtils.readEnvelopeFromRequest() is
defined with default access. Shouldn't it be public static?
---
Clay
Cisco Systems, Inc.
claycle@cisco.com
(972) 813-5004
J'ai un regret: je ne regrette rien.
----- Original Message -----
From: "Clay Luther" <cl...@cisco.com>
To: <so...@xml.apache.org>
Sent: Friday, April 06, 2001 6:06 PM
Subject: Re: Examples of Writing SOAP Servlets That ARE NOT using
RPCRouterServlet
> Are you saying rewrite/copy MessageRouterServlet, or are you saying use
> MessageRouterServlet written as is?
>
> ---
> Clay
> Cisco Systems, Inc.
> claycle@cisco.com
> (972) 813-5004
>
> J'ai un regret: je ne regrette rien.
>
>
> ----- Original Message -----
> From: "Wei Qian" <We...@oracle.com>
> To: <so...@xml.apache.org>
> Sent: Friday, April 06, 2001 4:57 PM
> Subject: RE: Examples of Writing SOAP Servlets That ARE NOT using
> RPCRouterServlet
>
>
> > Hi:
> >
> > A couple of days ago, i posted a message on how to extract
> > XML content from a SOAP Envelope. Basically, you need to
> > put it inside of MessageRouterServlet, so that it can
> > forward the XML request to your own logic instead of
> > call SOAP Proivder's API. After getting the XML response
> > from you application, put it back by
> >
> > resCtx.setRootPart( "<Your XML response/>",
> > Constants.HEADERVAL_CONTENT_TYPE_UTF8);
> >
> > I have done so with pure text XML request and response.
> > If you need to pass objects, then you can borrow
> > SOAP's serializer and deserializer, or you have to
> > write your own de/serializer.
> >
> > Hope it helps,
> >
> > Cheers,
> >
> > -Wei
> >
> > -----Original Message-----
> > From: Clay Luther [mailto:claycle@cisco.com]
> > Sent: Friday, April 06, 2001 5:19 PM
> > To: soap-user@xml.apache.org
> > Subject: Re: Examples of Writing SOAP Servlets That ARE NOT using
> > RPCRouterServlet
> >
> >
> > Hmmm...well, a cursory glance at the code it seems very similar to
> > RpcRouterServlet; ie., it relies on the Apache-SOAP infrastructure (like
> > ServiceProvider). I was looking for something a little
> more...streamlined.
> >
> > Bascially, we have an API already defined in XML. We want to transmit
the
> > API messages inside SOAP messages. The API does not conform the the RPC
> > mechanism used by RpcRouterServlet.
> >
> > I'm looking for a way to:
> >
> > 1) Quickly validate that the incoming request is a "well-formed" SOAP
> > message.
> > 2) Extract the Envelope's Body as an (XML) Document and hand it to my
API
> > SAX parser, which returns a (XML) Document as its result.
> > 3) Quickly construct response Envelopes that contain the parser's
returned
> > (XML) Documents.
> >
> > We've implemented this in C++ using MS SOAP. We now need to implement
it
> in
> > Apache-SOAP and right now I feel very straight-jacketed by the current
> > architecture all Apache-SOAP examples and articles seemed to be coded
> > towards.
> >
> > ---
> > Clay
> > Cisco Systems, Inc.
> > claycle@cisco.com
> > (972) 813-5004
> >
> > J'ai un regret: je ne regrette rien.
> >
> >
> > ----- Original Message -----
> > From: "Wei Qian" <We...@oracle.com>
> > To: <so...@xml.apache.org>
> > Sent: Friday, April 06, 2001 4:07 PM
> > Subject: RE: Examples of Writing SOAP Servlets That ARE NOT using
> > RPCRouterServlet
> >
> >
> > > Hi:
> > >
> > > If you like, you can use MessageRouterServlet instead.
> > >
> > > Cheers,
> > >
> > > -Wei
> > >
> > > -----Original Message-----
> > > From: Clay Luther [mailto:claycle@cisco.com]
> > > Sent: Friday, April 06, 2001 4:44 PM
> > > To: Soap-User
> > > Subject: Examples of Writing SOAP Servlets That ARE NOT using
> > > RPCRouterServlet
> > >
> > >
> > > I was wondering if anyone had or knows of an example of using
> Apache-SOAP
> > to
> > > write SOAP-aware servlets without using the RpcRouterServlet
> architecture,
> > > but still allows me to leverage the SOAP toolkit (rather than, say,
> > parsing
> > > the SOAP envelopes by hand).
> > >
> > > Thanks.
> > >
> > > ---
> > > Clay
> > > Cisco Systems, Inc.
> > > claycle@cisco.com
> > > (972) 813-5004
> > >
> > > J'ai un regret: je ne regrette rien.
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > > For additional commands, email: soap-user-help@xml.apache.org
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > > For additional commands, email: soap-user-help@xml.apache.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > For additional commands, email: soap-user-help@xml.apache.org
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > For additional commands, email: soap-user-help@xml.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Clay Luther <cl...@cisco.com>.
Are you saying rewrite/copy MessageRouterServlet, or are you saying use
MessageRouterServlet written as is?
---
Clay
Cisco Systems, Inc.
claycle@cisco.com
(972) 813-5004
J'ai un regret: je ne regrette rien.
----- Original Message -----
From: "Wei Qian" <We...@oracle.com>
To: <so...@xml.apache.org>
Sent: Friday, April 06, 2001 4:57 PM
Subject: RE: Examples of Writing SOAP Servlets That ARE NOT using
RPCRouterServlet
> Hi:
>
> A couple of days ago, i posted a message on how to extract
> XML content from a SOAP Envelope. Basically, you need to
> put it inside of MessageRouterServlet, so that it can
> forward the XML request to your own logic instead of
> call SOAP Proivder's API. After getting the XML response
> from you application, put it back by
>
> resCtx.setRootPart( "<Your XML response/>",
> Constants.HEADERVAL_CONTENT_TYPE_UTF8);
>
> I have done so with pure text XML request and response.
> If you need to pass objects, then you can borrow
> SOAP's serializer and deserializer, or you have to
> write your own de/serializer.
>
> Hope it helps,
>
> Cheers,
>
> -Wei
>
> -----Original Message-----
> From: Clay Luther [mailto:claycle@cisco.com]
> Sent: Friday, April 06, 2001 5:19 PM
> To: soap-user@xml.apache.org
> Subject: Re: Examples of Writing SOAP Servlets That ARE NOT using
> RPCRouterServlet
>
>
> Hmmm...well, a cursory glance at the code it seems very similar to
> RpcRouterServlet; ie., it relies on the Apache-SOAP infrastructure (like
> ServiceProvider). I was looking for something a little
more...streamlined.
>
> Bascially, we have an API already defined in XML. We want to transmit the
> API messages inside SOAP messages. The API does not conform the the RPC
> mechanism used by RpcRouterServlet.
>
> I'm looking for a way to:
>
> 1) Quickly validate that the incoming request is a "well-formed" SOAP
> message.
> 2) Extract the Envelope's Body as an (XML) Document and hand it to my API
> SAX parser, which returns a (XML) Document as its result.
> 3) Quickly construct response Envelopes that contain the parser's returned
> (XML) Documents.
>
> We've implemented this in C++ using MS SOAP. We now need to implement it
in
> Apache-SOAP and right now I feel very straight-jacketed by the current
> architecture all Apache-SOAP examples and articles seemed to be coded
> towards.
>
> ---
> Clay
> Cisco Systems, Inc.
> claycle@cisco.com
> (972) 813-5004
>
> J'ai un regret: je ne regrette rien.
>
>
> ----- Original Message -----
> From: "Wei Qian" <We...@oracle.com>
> To: <so...@xml.apache.org>
> Sent: Friday, April 06, 2001 4:07 PM
> Subject: RE: Examples of Writing SOAP Servlets That ARE NOT using
> RPCRouterServlet
>
>
> > Hi:
> >
> > If you like, you can use MessageRouterServlet instead.
> >
> > Cheers,
> >
> > -Wei
> >
> > -----Original Message-----
> > From: Clay Luther [mailto:claycle@cisco.com]
> > Sent: Friday, April 06, 2001 4:44 PM
> > To: Soap-User
> > Subject: Examples of Writing SOAP Servlets That ARE NOT using
> > RPCRouterServlet
> >
> >
> > I was wondering if anyone had or knows of an example of using
Apache-SOAP
> to
> > write SOAP-aware servlets without using the RpcRouterServlet
architecture,
> > but still allows me to leverage the SOAP toolkit (rather than, say,
> parsing
> > the SOAP envelopes by hand).
> >
> > Thanks.
> >
> > ---
> > Clay
> > Cisco Systems, Inc.
> > claycle@cisco.com
> > (972) 813-5004
> >
> > J'ai un regret: je ne regrette rien.
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > For additional commands, email: soap-user-help@xml.apache.org
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > For additional commands, email: soap-user-help@xml.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Clay Luther <cl...@cisco.com>.
Are you saying rewrite/copy MessageRouterServlet, or are you saying use
MessageRouterServlet written as is?
---
Clay
Cisco Systems, Inc.
claycle@cisco.com
(972) 813-5004
J'ai un regret: je ne regrette rien.
----- Original Message -----
From: "Wei Qian" <We...@oracle.com>
To: <so...@xml.apache.org>
Sent: Friday, April 06, 2001 4:57 PM
Subject: RE: Examples of Writing SOAP Servlets That ARE NOT using
RPCRouterServlet
> Hi:
>
> A couple of days ago, i posted a message on how to extract
> XML content from a SOAP Envelope. Basically, you need to
> put it inside of MessageRouterServlet, so that it can
> forward the XML request to your own logic instead of
> call SOAP Proivder's API. After getting the XML response
> from you application, put it back by
>
> resCtx.setRootPart( "<Your XML response/>",
> Constants.HEADERVAL_CONTENT_TYPE_UTF8);
>
> I have done so with pure text XML request and response.
> If you need to pass objects, then you can borrow
> SOAP's serializer and deserializer, or you have to
> write your own de/serializer.
>
> Hope it helps,
>
> Cheers,
>
> -Wei
>
> -----Original Message-----
> From: Clay Luther [mailto:claycle@cisco.com]
> Sent: Friday, April 06, 2001 5:19 PM
> To: soap-user@xml.apache.org
> Subject: Re: Examples of Writing SOAP Servlets That ARE NOT using
> RPCRouterServlet
>
>
> Hmmm...well, a cursory glance at the code it seems very similar to
> RpcRouterServlet; ie., it relies on the Apache-SOAP infrastructure (like
> ServiceProvider). I was looking for something a little
more...streamlined.
>
> Bascially, we have an API already defined in XML. We want to transmit the
> API messages inside SOAP messages. The API does not conform the the RPC
> mechanism used by RpcRouterServlet.
>
> I'm looking for a way to:
>
> 1) Quickly validate that the incoming request is a "well-formed" SOAP
> message.
> 2) Extract the Envelope's Body as an (XML) Document and hand it to my API
> SAX parser, which returns a (XML) Document as its result.
> 3) Quickly construct response Envelopes that contain the parser's returned
> (XML) Documents.
>
> We've implemented this in C++ using MS SOAP. We now need to implement it
in
> Apache-SOAP and right now I feel very straight-jacketed by the current
> architecture all Apache-SOAP examples and articles seemed to be coded
> towards.
>
> ---
> Clay
> Cisco Systems, Inc.
> claycle@cisco.com
> (972) 813-5004
>
> J'ai un regret: je ne regrette rien.
>
>
> ----- Original Message -----
> From: "Wei Qian" <We...@oracle.com>
> To: <so...@xml.apache.org>
> Sent: Friday, April 06, 2001 4:07 PM
> Subject: RE: Examples of Writing SOAP Servlets That ARE NOT using
> RPCRouterServlet
>
>
> > Hi:
> >
> > If you like, you can use MessageRouterServlet instead.
> >
> > Cheers,
> >
> > -Wei
> >
> > -----Original Message-----
> > From: Clay Luther [mailto:claycle@cisco.com]
> > Sent: Friday, April 06, 2001 4:44 PM
> > To: Soap-User
> > Subject: Examples of Writing SOAP Servlets That ARE NOT using
> > RPCRouterServlet
> >
> >
> > I was wondering if anyone had or knows of an example of using
Apache-SOAP
> to
> > write SOAP-aware servlets without using the RpcRouterServlet
architecture,
> > but still allows me to leverage the SOAP toolkit (rather than, say,
> parsing
> > the SOAP envelopes by hand).
> >
> > Thanks.
> >
> > ---
> > Clay
> > Cisco Systems, Inc.
> > claycle@cisco.com
> > (972) 813-5004
> >
> > J'ai un regret: je ne regrette rien.
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > For additional commands, email: soap-user-help@xml.apache.org
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > For additional commands, email: soap-user-help@xml.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
RE: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Wei Qian <We...@oracle.com>.
Hi:
A couple of days ago, i posted a message on how to extract
XML content from a SOAP Envelope. Basically, you need to
put it inside of MessageRouterServlet, so that it can
forward the XML request to your own logic instead of
call SOAP Proivder's API. After getting the XML response
from you application, put it back by
resCtx.setRootPart( "<Your XML response/>",
Constants.HEADERVAL_CONTENT_TYPE_UTF8);
I have done so with pure text XML request and response.
If you need to pass objects, then you can borrow
SOAP's serializer and deserializer, or you have to
write your own de/serializer.
Hope it helps,
Cheers,
-Wei
-----Original Message-----
From: Clay Luther [mailto:claycle@cisco.com]
Sent: Friday, April 06, 2001 5:19 PM
To: soap-user@xml.apache.org
Subject: Re: Examples of Writing SOAP Servlets That ARE NOT using
RPCRouterServlet
Hmmm...well, a cursory glance at the code it seems very similar to
RpcRouterServlet; ie., it relies on the Apache-SOAP infrastructure (like
ServiceProvider). I was looking for something a little more...streamlined.
Bascially, we have an API already defined in XML. We want to transmit the
API messages inside SOAP messages. The API does not conform the the RPC
mechanism used by RpcRouterServlet.
I'm looking for a way to:
1) Quickly validate that the incoming request is a "well-formed" SOAP
message.
2) Extract the Envelope's Body as an (XML) Document and hand it to my API
SAX parser, which returns a (XML) Document as its result.
3) Quickly construct response Envelopes that contain the parser's returned
(XML) Documents.
We've implemented this in C++ using MS SOAP. We now need to implement it in
Apache-SOAP and right now I feel very straight-jacketed by the current
architecture all Apache-SOAP examples and articles seemed to be coded
towards.
---
Clay
Cisco Systems, Inc.
claycle@cisco.com
(972) 813-5004
J'ai un regret: je ne regrette rien.
----- Original Message -----
From: "Wei Qian" <We...@oracle.com>
To: <so...@xml.apache.org>
Sent: Friday, April 06, 2001 4:07 PM
Subject: RE: Examples of Writing SOAP Servlets That ARE NOT using
RPCRouterServlet
> Hi:
>
> If you like, you can use MessageRouterServlet instead.
>
> Cheers,
>
> -Wei
>
> -----Original Message-----
> From: Clay Luther [mailto:claycle@cisco.com]
> Sent: Friday, April 06, 2001 4:44 PM
> To: Soap-User
> Subject: Examples of Writing SOAP Servlets That ARE NOT using
> RPCRouterServlet
>
>
> I was wondering if anyone had or knows of an example of using Apache-SOAP
to
> write SOAP-aware servlets without using the RpcRouterServlet architecture,
> but still allows me to leverage the SOAP toolkit (rather than, say,
parsing
> the SOAP envelopes by hand).
>
> Thanks.
>
> ---
> Clay
> Cisco Systems, Inc.
> claycle@cisco.com
> (972) 813-5004
>
> J'ai un regret: je ne regrette rien.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
RE: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Wei Qian <We...@oracle.com>.
Hi:
A couple of days ago, i posted a message on how to extract
XML content from a SOAP Envelope. Basically, you need to
put it inside of MessageRouterServlet, so that it can
forward the XML request to your own logic instead of
call SOAP Proivder's API. After getting the XML response
from you application, put it back by
resCtx.setRootPart( "<Your XML response/>",
Constants.HEADERVAL_CONTENT_TYPE_UTF8);
I have done so with pure text XML request and response.
If you need to pass objects, then you can borrow
SOAP's serializer and deserializer, or you have to
write your own de/serializer.
Hope it helps,
Cheers,
-Wei
-----Original Message-----
From: Clay Luther [mailto:claycle@cisco.com]
Sent: Friday, April 06, 2001 5:19 PM
To: soap-user@xml.apache.org
Subject: Re: Examples of Writing SOAP Servlets That ARE NOT using
RPCRouterServlet
Hmmm...well, a cursory glance at the code it seems very similar to
RpcRouterServlet; ie., it relies on the Apache-SOAP infrastructure (like
ServiceProvider). I was looking for something a little more...streamlined.
Bascially, we have an API already defined in XML. We want to transmit the
API messages inside SOAP messages. The API does not conform the the RPC
mechanism used by RpcRouterServlet.
I'm looking for a way to:
1) Quickly validate that the incoming request is a "well-formed" SOAP
message.
2) Extract the Envelope's Body as an (XML) Document and hand it to my API
SAX parser, which returns a (XML) Document as its result.
3) Quickly construct response Envelopes that contain the parser's returned
(XML) Documents.
We've implemented this in C++ using MS SOAP. We now need to implement it in
Apache-SOAP and right now I feel very straight-jacketed by the current
architecture all Apache-SOAP examples and articles seemed to be coded
towards.
---
Clay
Cisco Systems, Inc.
claycle@cisco.com
(972) 813-5004
J'ai un regret: je ne regrette rien.
----- Original Message -----
From: "Wei Qian" <We...@oracle.com>
To: <so...@xml.apache.org>
Sent: Friday, April 06, 2001 4:07 PM
Subject: RE: Examples of Writing SOAP Servlets That ARE NOT using
RPCRouterServlet
> Hi:
>
> If you like, you can use MessageRouterServlet instead.
>
> Cheers,
>
> -Wei
>
> -----Original Message-----
> From: Clay Luther [mailto:claycle@cisco.com]
> Sent: Friday, April 06, 2001 4:44 PM
> To: Soap-User
> Subject: Examples of Writing SOAP Servlets That ARE NOT using
> RPCRouterServlet
>
>
> I was wondering if anyone had or knows of an example of using Apache-SOAP
to
> write SOAP-aware servlets without using the RpcRouterServlet architecture,
> but still allows me to leverage the SOAP toolkit (rather than, say,
parsing
> the SOAP envelopes by hand).
>
> Thanks.
>
> ---
> Clay
> Cisco Systems, Inc.
> claycle@cisco.com
> (972) 813-5004
>
> J'ai un regret: je ne regrette rien.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Clay Luther <cl...@cisco.com>.
Hmmm...well, a cursory glance at the code it seems very similar to
RpcRouterServlet; ie., it relies on the Apache-SOAP infrastructure (like
ServiceProvider). I was looking for something a little more...streamlined.
Bascially, we have an API already defined in XML. We want to transmit the
API messages inside SOAP messages. The API does not conform the the RPC
mechanism used by RpcRouterServlet.
I'm looking for a way to:
1) Quickly validate that the incoming request is a "well-formed" SOAP
message.
2) Extract the Envelope's Body as an (XML) Document and hand it to my API
SAX parser, which returns a (XML) Document as its result.
3) Quickly construct response Envelopes that contain the parser's returned
(XML) Documents.
We've implemented this in C++ using MS SOAP. We now need to implement it in
Apache-SOAP and right now I feel very straight-jacketed by the current
architecture all Apache-SOAP examples and articles seemed to be coded
towards.
---
Clay
Cisco Systems, Inc.
claycle@cisco.com
(972) 813-5004
J'ai un regret: je ne regrette rien.
----- Original Message -----
From: "Wei Qian" <We...@oracle.com>
To: <so...@xml.apache.org>
Sent: Friday, April 06, 2001 4:07 PM
Subject: RE: Examples of Writing SOAP Servlets That ARE NOT using
RPCRouterServlet
> Hi:
>
> If you like, you can use MessageRouterServlet instead.
>
> Cheers,
>
> -Wei
>
> -----Original Message-----
> From: Clay Luther [mailto:claycle@cisco.com]
> Sent: Friday, April 06, 2001 4:44 PM
> To: Soap-User
> Subject: Examples of Writing SOAP Servlets That ARE NOT using
> RPCRouterServlet
>
>
> I was wondering if anyone had or knows of an example of using Apache-SOAP
to
> write SOAP-aware servlets without using the RpcRouterServlet architecture,
> but still allows me to leverage the SOAP toolkit (rather than, say,
parsing
> the SOAP envelopes by hand).
>
> Thanks.
>
> ---
> Clay
> Cisco Systems, Inc.
> claycle@cisco.com
> (972) 813-5004
>
> J'ai un regret: je ne regrette rien.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Clay Luther <cl...@cisco.com>.
Hmmm...well, a cursory glance at the code it seems very similar to
RpcRouterServlet; ie., it relies on the Apache-SOAP infrastructure (like
ServiceProvider). I was looking for something a little more...streamlined.
Bascially, we have an API already defined in XML. We want to transmit the
API messages inside SOAP messages. The API does not conform the the RPC
mechanism used by RpcRouterServlet.
I'm looking for a way to:
1) Quickly validate that the incoming request is a "well-formed" SOAP
message.
2) Extract the Envelope's Body as an (XML) Document and hand it to my API
SAX parser, which returns a (XML) Document as its result.
3) Quickly construct response Envelopes that contain the parser's returned
(XML) Documents.
We've implemented this in C++ using MS SOAP. We now need to implement it in
Apache-SOAP and right now I feel very straight-jacketed by the current
architecture all Apache-SOAP examples and articles seemed to be coded
towards.
---
Clay
Cisco Systems, Inc.
claycle@cisco.com
(972) 813-5004
J'ai un regret: je ne regrette rien.
----- Original Message -----
From: "Wei Qian" <We...@oracle.com>
To: <so...@xml.apache.org>
Sent: Friday, April 06, 2001 4:07 PM
Subject: RE: Examples of Writing SOAP Servlets That ARE NOT using
RPCRouterServlet
> Hi:
>
> If you like, you can use MessageRouterServlet instead.
>
> Cheers,
>
> -Wei
>
> -----Original Message-----
> From: Clay Luther [mailto:claycle@cisco.com]
> Sent: Friday, April 06, 2001 4:44 PM
> To: Soap-User
> Subject: Examples of Writing SOAP Servlets That ARE NOT using
> RPCRouterServlet
>
>
> I was wondering if anyone had or knows of an example of using Apache-SOAP
to
> write SOAP-aware servlets without using the RpcRouterServlet architecture,
> but still allows me to leverage the SOAP toolkit (rather than, say,
parsing
> the SOAP envelopes by hand).
>
> Thanks.
>
> ---
> Clay
> Cisco Systems, Inc.
> claycle@cisco.com
> (972) 813-5004
>
> J'ai un regret: je ne regrette rien.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
RE: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Wei Qian <We...@oracle.com>.
Hi:
If you like, you can use MessageRouterServlet instead.
Cheers,
-Wei
-----Original Message-----
From: Clay Luther [mailto:claycle@cisco.com]
Sent: Friday, April 06, 2001 4:44 PM
To: Soap-User
Subject: Examples of Writing SOAP Servlets That ARE NOT using
RPCRouterServlet
I was wondering if anyone had or knows of an example of using Apache-SOAP to
write SOAP-aware servlets without using the RpcRouterServlet architecture,
but still allows me to leverage the SOAP toolkit (rather than, say, parsing
the SOAP envelopes by hand).
Thanks.
---
Clay
Cisco Systems, Inc.
claycle@cisco.com
(972) 813-5004
J'ai un regret: je ne regrette rien.
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
RE: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet
Posted by Wei Qian <We...@oracle.com>.
Hi:
If you like, you can use MessageRouterServlet instead.
Cheers,
-Wei
-----Original Message-----
From: Clay Luther [mailto:claycle@cisco.com]
Sent: Friday, April 06, 2001 4:44 PM
To: Soap-User
Subject: Examples of Writing SOAP Servlets That ARE NOT using
RPCRouterServlet
I was wondering if anyone had or knows of an example of using Apache-SOAP to
write SOAP-aware servlets without using the RpcRouterServlet architecture,
but still allows me to leverage the SOAP toolkit (rather than, say, parsing
the SOAP envelopes by hand).
Thanks.
---
Clay
Cisco Systems, Inc.
claycle@cisco.com
(972) 813-5004
J'ai un regret: je ne regrette rien.
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org