A Apache-SOAP Bug? (was Re: Examples of Writing SOAP Servlets That ARE NOT using RPCRouterServlet)

[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