Re: seperate server and client code

From: Dale Green <dale.green_at_Sun.COM>
Date: Thu, 14 Mar 2002 09:57:11 -0800

Hi Isabelle,

In the EA2 version of the Java(tm) Web Services Tutorial,
my HelloWorld example will take the approach suggested
by Su. In summary, my build.xml file does this:

1. compiles HelloImpl & HelloIF,
   classes -> build/shared

2. runs xrpcc -server,
   classes -> build/server

3. packages contents of build/shared & build/server
   into a WAR file

4. runs xrpcc -client,
   classes -> build/client

5. packages the contents of build/shared & build/client
   into a JAR file

- Dale

>Date: Thu, 14 Mar 2002 06:20:02 -0700
>From: Su Zhang <su_ba_ru_at_HOTMAIL.COM>
>Subject: Re: [JAX-RPC] seperate server and client code
>Hi Isabelle,
>The xrpcc tool's "-server" option generates server-side files only. And its
"-client" option generates client-side classes only.
>Hope it helps.
>On Thu, 14 Mar 2002 09:48:58 +0100, Isabelle Gheysens
<i.gheysens_at_ENERGYICT.COM> wrote:
>>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
>>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?