axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Johan Walters <johan.walt...@gmail.com>
Subject Re: Eclipse build path problem (conflict between client stubs and server code)
Date Tue, 18 Oct 2005 15:49:45 GMT
I'm affraid it doesn't help. Thanks for thinking with me though.

Johan

2005/10/18, Grossberger, Guenter <Guenter.Grossberger@softwareag.com>:
> Hi!
>
> You may do the following (although I didn't try it out):
> Open Project/Properties/Java BuildPath, select "Allow output folders for source folders"
and specify different folders for your source folders.
>
>
> Best regards,
>
> --
> DI Günter Grossberger
> Consultant             Tel: +43 1 329 50 161
> Software AG Österreich Fax: +43 1 329 50 171
> Guglgasse 7-9          GSM: +43 676 833 29 261
> 1030 Wien              http://www.softwareag.com/austria
>
>
> > -----Original Message-----
> > From: Johan Walters [mailto:johan.walters@gmail.com]
> > Sent: Monday, October 17, 2005 11:55 AM
> > To: axis-user@ws.apache.org
> > Subject: Eclipse build path problem (conflict between client
> > stubs and server code)
> >
> > Hi all,
> >
> > I'm using Eclipse to edit and build my project. In this project I have
> > both client and server code. I've integrated axis to my servlet
> > project. The idea is that the whole lot is deployed to tomcat, where
> > users will be able to download the client program.
> >
> > Using java2wsdl and wsdl2java to generate client code, goes fine. The
> > output java files are placed in a separate source tree in my project.
> > The stub-classes there have the same packagename as the service code
> > has. In ant, I simply compile both source trees seperately. All works
> > fine, building and running both the server and client works.
> >
> > The problem is, Eclipse's build path (to compile ahead and provide
> > in-line assistance) sees only one project, and also sees that stub
> > classnames already have been declared in the other source tree and
> > references in the client code are interpreted to the wrong package.
> >
> > I suppose I'm not the only one facing this probem. The solutions I can
> > think of is either removing the client source tree from the build
> > path, or changing the namespace in wsdl2java so that the stub classes
> > will be in a package with a different name.
> >
> > I'm not sure whether the latter solution has any disadvantages, but
> > it's ugly at least. Can't Eclipse just treat two source folders
> > seperately? I do not want two make two separate projects out of it;
> > the client code has to be deployed to the server as well (for
> > distribution), and I certainly do not want to use two CVS
> > repositories.
> >
> > Any Ideas?
> >
> > Johan Walters
> >
>

Mime
View raw message