Hi,
from what I understand so far, axis and its tools support me quite
good in a situation where I only have an interface which I want
to implement as WebService:
- Java2WSDL creates an WSDL file from it
- WSDL2Java picks up this file and creates client stubs _and_
necessary java beans (complexTypes representations), and if
I want, I also get some server skeletons and the (un)deploy.wsdd
files to deploy the WebService.
Unfortunately, this is not exactly the situation I am in. I already
have a running WebService "demo", where I created server and client
side, which is running on a different SOAP implementation today,
and I want to migrate it to use axis instead.
What I already have is
- an interface which contains all java.rmi-specific stuff,
- a java bean which I want to "transfer" using a WebService,
which also has a method "foo()" that I want to call on the
client,
- the server side implementation, of course and
- the client code.
So what I want to do is the following:
"Hey Axis, here is an interface and it's implementation. Please
deploy this as a WebService and give me the WSDL for it.
Thanks! Now I want to create client stubs, but, hey, here I
already have the interface and 'Bean' implementation, please use
this and do not create new Java sources. I only want the stubs
which I use in my client then."
Until now, I could not figure out if there is a simlpe way
how to do this. (A workaround would be to let axis create the
files first and then replace the created files with my own,
of course, but I do not like this too much).
Is there any "best practice" for my situation?
Any help appreciated,
Jonas
--
Jonas Rathert
PLATINION GmbH
A Company of the Boston Consulting Group
Im Mediapark 5, 50670 Cologne/Germany
Tel. +49 221. 58 95 83 04
Fax +49 221. 589 20 51
mailto:[EMAIL PROTECTED]
http://www.platinion.de/
