On Wednesday 19 January 2005 20:19, Peter Molettiere wrote:
> On Jan 19, 2005, at 7:52 AM, Michael Schuerig wrote:
> > For integration testing of client and server code and configuration
> > I'd like to cut the Axis handler stack in the place where messages
> > are converted to and from XML.
>
> I'm not sure if this is what you want or not... but it's a structure
> I use for unit testing axis stuff. You don't need to set up a
> server/tomcat/webapp to do serialization/deserialization.
I don't just want to test de/serializers. For that I already have a way,
though I forget the details when I don't look at it for five minutes.
What I'm looking for could tentatively be "StringTransport" where I get
two methods in some appropriate place:
For client-side testing I want to implement a method
String handleInvocation(String request)
that gets called for each invocation with the SOAP request and returns
some SOAP response.
For server-side testing I'd like to call a method
String invokeService(String request)
that I pass the SOAP request and which returns the SOAP response
produced by the invoked operation.
The point really is that I'd like to use the actual "live" configuration
as much as possible with only a tiny detour to a custom handler that
provides the interfaces shown above.
After thinking about this a bit more, I have the idea that this can be
done with a custom transport. I have no clear idea how this might work,
but there's an example of a FileTransport in the samples. I'm
wondering, though, if I can avoid to implement a StringTransport and
simply use some means that are already there in Axis.
Michael
--
Michael Schuerig Those people who smile a lot
mailto:[EMAIL PROTECTED] Watch the eyes
http://www.schuerig.de/michael/ --Ani DiFranco, Outta Me, Onto You
