Can't explain why you're not seeing the 2nd part of it (the
soap call), but looking at the code in the JSP it set the
target URL to the same URL as the JSP except pointing
to a jws file instead.  Which means its going back over
the net.   It sounds like you changed your client to go
thru tcpmon - try changing the server instead.  By that I
mean go into tomcat's (or whatever server your using)
config\server.xml file and change the port # to something
else (like 8181).  Then bring up tcpmon to route all 8080
requests to 8181 - you should then catch _all_ requests.
-Dug


"Thalis A. Kalfigopoulos" <[EMAIL PROTECTED]> on 04/06/2002 06:57:18 PM

Please respond to [EMAIL PROTECTED]

To:    [EMAIL PROTECTED]
cc:
Subject:    Re: BWS book ch3/ex2 problem: No SOAP, just POST



On Sat, 6 Apr 2002, Doug Davis wrote:

> >From the browser to the jsp yes its just a post, but inside the jsp is
an
> axis client that will do the real soap call.
> -Dug

That's strange, because in the book around page 130-31 they suggest the use
of TCPMon to check excactly that the data exchanged is SOAP messages! They
even have a screenshot showing that. Am I misinterpreting it?
What could the reason for the disagreement between the two outputs?

thanks again,
thalis

>
>
> "Thalis A. Kalfigopoulos" <[EMAIL PROTECTED]> on 04/06/2002 05:28:29 PM
>
> Please respond to [EMAIL PROTECTED]
>
> To:    [EMAIL PROTECTED]
> cc:
> Subject:    BWS book ch3/ex2 problem: No SOAP, just POST
>
>
>
> Hello, I've been trying to manage things with the "Builing Web
Services..."
> book.
> The problem is with ch3/ex2 where you are supposed to place an Inventory
> Check request by POSTing a SOAP message. The example seems to work ok,
but
> when I monitor the traffic with TCPMon it appears to be just a simple
POST
> i.e. the data is sent as sku=947-TI&quantity=1 and not as a SOAP message.
> And of course the request is also not SOAP.
>
> I'm using axis beta1 & tomcat4.0.
>
>
> Any help appreciated.
>
> TIA,
> thalis
>
> p.s. someone else was having problems with the same chapter-example but
not
> like to this
>
>
>
>



Reply via email to