Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <22446776.post@talk.nabble.com>
Date: Tue, 10 Mar 2009 17:43:38 -0700 (PDT)
From: Christoph <christoph.amshoff@fjh.com>
To: users@maven.apache.org
Subject: Re: Best practice: web service project structure
In-Reply-To: <49B6CEE0.4090509@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <22431433.post@talk.nabble.com> <49B6CEE0.4090509@gmail.com>


Thanks Rusty, but this is actually not answering my question...

I know how to do multi-module projects in principle, I'm just wondering if
that is the right approach to structure a single web service to get separate
JARs for the different "views" on it (client view, impl view). 

A WS should be considered one logical "project" but still I think it is
useful to get one JAR used by WS callers, another JAR used by WS
implementation and maybe a third JAR containing common classes used by both.
Does this make sense? If so, how to best achieve that?

Christoph.


Rusty Wright-2 wrote:
> 
> http://www.sonatype.com/books/maven-book/reference/
> 
> Have a look at the multi-module projects.
> 
> 
> Christoph wrote:
>> Hi,
>> 
>> we're want to setup a couple of web service projects that have to provide
>> several artifacts:
>> * ws-client.jar: contains everything required to call the WS
>> * ws-impl.jar: provides the implementation of a WS
>> * ws-core.jar: contains base classes used by both of the others
>> 
>> This way a WS client is not forced to have dependencies required for WS
>> implementation. Quite common, I think.
>> 
>> Now... the question is, how to best set this up with Maven. I didn't find
>> very much in documentation and mailing lists about how to structure the
>> projects. IMO there are two options:
>> 
>> 1) Have a single Maven project that generates multiple artifacts (JAR
>> files). They could all have the same base name but a distinct classifier,
>> for instance. Assembly plugin could be useful, right? Of course, all JARs
>> must be deployed in the end.
>> 
>> 2) Use a multi-module project with dedicated subprojects for the 2
>> artifacts, so there is one artifact per Maven project. However, this
>> might
>> be some overhead because some projects will only contain few files.
>> 
>> What do you think, which way is the preferred one? How are YOU doing WS
>> projects?
>> 
>> Thanks for any opinion,
>> Christoph
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Best-practice%3A-web-service-project-structure-tp22431433p22446776.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org