Hi Isabelle,
Here is the correct distribution for your application:
Client side:
------------
LogonDialog.class
LoginIF_Stub.class
LoginServiceImpl.class
LoginService.class
Both sides:
------------
LoginIF.class
Login_RequestStruct.class
Login_RequestStruct_SOAPSerializer.class
Login_ResponseStruct.class
Login_ResponseStruct_SOAPSerializer.class
Server side:
------------
LoginImpl.class
LoginIF_Tie.class
Hope that helps. You can also follow the approach as suggested by Su and
Dale.
Thanks for your interest in JAX-RPC.
Regards,
-Arun
Isabelle Gheysens wrote:
> Hi,
>
> I'm new to jaxrpc.
> I managed to write a client that makes jaxrpc calls to a server.
> Client and server code are all together now...
> I have one client class: LogonDialog
> I have following server classes: LogonIF, LogonImpl
>
> Also a lot of classes have been generated: Login_RequestStruct.class,
> Login_RequestStruct_SOAPSerializer.class, Login_ResponseStruct.class,
> Login_ResponseStruct_SOAPSerializer.class, LoginIF_Stub.class,
> LoginIF_Tie.class, LoginService.class, LoginService.class and
> LoginServiceImpl.class
>
> I want to seperate client and server code in seperate packages so that each
> only contains those files really needed,
> I suppose the stubs belong to the client code and the ties belong to the
> server code... but what about the other generated classes...?
> How can I automate this that class files are put automatically in the right
> place so that it's easy to deploy my client code to all the clients?
>
> Thanx!
>
> Isabelle
--
=============================================
There is only one me, I must live myself!
There is only one today, I must live itself!
=============================================
http://members.tripod.com/~apgupta/index.html
=============================================