Re: seperate server and client code

From: Simon Horrell <>
Date: Thu, 14 Mar 2002 14:01:35 +0000

Note that they will both generate [un]marshalling code needed by both client
and server. I am not sure that there is a way (using the RI) to specify one
package for client-side classes, one for server-side classes and another for
common (shared) classes if that is what you wanted.

----- Original Message -----
From: "Su Zhang" <su_ba_ru_at_HOTMAIL.COM>
Sent: Thursday, March 14, 2002 1:20 PM
Subject: Re: 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.
> Su
> On Thu, 14 Mar 2002 09:48:58 +0100, Isabelle Gheysens
<i.gheysens_at_ENERGYICT.COM> 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
> >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
> >place so that it's easy to deploy my client code to all the clients?
> >
> >Thanx!
> >
> >Isabelle