Thanks for your generous help,
One final question, If I have TCPMonitor listening to some arbitrary port
and targeting 8080, what do I do to actually get it to react in some way? Run my
client? Must I run the client exclusively to/from the listen port? How would I
do that. In other words, what are the final steps?
James Crosson
In a message dated 6/15/2004 3:54:30 AM Eastern Standard Time,
[EMAIL PROTECTED] writes:
Hi,
No need to keep the client side classes in a separate
directory. You can
keep them in the same directory. Check the Axis
userguide which explains
how to use the client side.(
http://ws.apache.org/axis/java/user-guide )
For running the client
application(creting the request for the client
application) either you
generate the stubs or you can write your
webservice client
manually.
TCPMonitor: change your sending port from the client to some
port
number(for e.g.5555) and make that port as listen port for TCP monitor
and
set the target port as the actual target port(for e.g.8080).
So soap
messages are listened at 5555 and redirected to 8080.
(Can get more
information at axis
userguide).
regards,
Jeyakumaran
>
> I have
developed a correct WSDL file, and have generated the appropriate
>
classes with WSDL2Java. I did a small amount of tinkering with the
>
classes,
> ran AdminClient and have my Web Service running on the local
TomCat
> server.
> I have added some handlers and written a
messager service.
>
> What now? How exactly do I utilize this web
service and see if it works?
> Do
> I put the client side classes
in one directory and providor sides in
> another? Do I run a specifid
program or have to make a new one? I'm even a
> bit lost on how to
utilize TCPMonitor (I know how to run it but how do I
> get
>
messages moving with SOAP?)
>
> Thanks,
> James
Crosson
> KledarasTechnologies
>
>
Lanka Software
Foundation
Promoting opensource in Srilanka
|
