Thanks alot Michael, Indeed that makes quite alot of sense especially since we have 15 grid services that we want to migrate. I had thought of creating a single parent pom but that is probably more acurate as client deps are not the same as service/stubs deps.
However since I'm writing the WSDL2Java mojo (it is not normal Axis) I was wondering if there is a way to programatically create the "stubs" subproject along with its pom file from goal in the "ws1" package pom. I'll try to explain a little more: - parent (package .POM) -- service-parent (must have a .GAR package output) -- ws1 (must have a .GAR package output) --- client (output .JAR) --- services (output .JAR) --- stubs (output.JAR) -- ws2 (must have a .GAR package output) --- client (output .JAR) --- services (output .JAR) --- stubs (output.JAR) That's the last question (I hope) but can I put a bunch of stuff under the ws1/src/main/resources directory such as WSDL / deployment descriptor etc? And have my .GAR Mojo pacakge the JAR along with the differen config files / hibernate map files and client shell scripts? Thank you again! Mathieu ----- Original Message ----- From: "Michael McCallum" <[EMAIL PROTECTED]> To: "Maven Users List" <[email protected]> Sent: Tuesday, February 19, 2008 7:47:26 PM (GMT-0500) America/New_York Subject: Re: Good Project Structure for Web Services? simple question for you.... so this structure looks 'nice'... what do you do when you have 2 webservices? 3? 4? now you have that in you head look at your poms... where is the duplication? in the configuration of the plugins in each of the so called children. if you have a parent of client and stub and service its not possible to factor that plugin configuration up... if however you had parents - distribution-management-parent aka company pom - client-parent :: distribution-management-parent - service-parent :: distribution-management-parent - stubs-parent :: distribution-management-parent ws1 - common-deps :: distribution-management-parent - client :: client-parent - service :: service-parent - stubs :: stubs-parent ws2 - common-deps :: distribution-management-parent - client :: client-parent - service :: service-parent - stubs :: stubs-parent ws(n) .... if you need common deps you can compose them in a common artifact of the client, service and stub siblings. the common deps may include the schema, wsdl etc as well (its unfortunate many plugins do not support loading resources from the classpath) if you still want a project aggregation you can will make ws1, ws2 as modules projects but that does not imply or require inheritance... On Wed, 20 Feb 2008 13:20:12 Mathieu Lemay wrote: > Hello everyone, I'm struggling at getting a good structure for webservice > packages. > > From the WSDL Java stubs will be created therefore should the structure be: > > parent > -client > -stubs > -service > > where parent also contains the schemas and WSDL files as well as any > server-config.wsdd , or other elements? Or should I find a way to have all > three artifacts (client, stubs and service jars) be created from the parent > pom (classifiers). I will also have to create a special pacakge (called > GAR) from the three JARS + WSDL + config files and special deployment > descriptors. I'm creating the plugin for creating GARs at the moment but > I'm now wondering if this plugin should create the "submodule" when > creating STUBS via the WSDL2Java. > > Help Please? > > Mathieu > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
