That is actually the way we build all of our projects and it makes it easier for development, unit testing and our SCM processes. We really don't need the ear for dev and unit testing but it is our required packaging to get through audit and SCM process. WE actually check them into our source code control in a consolidated project and use the master pom of the project to control the versions so that all the artifacts within that group use the same versions of related artifacts and the resolution within the project is consistent.
I hope to have the servicegen mojo done this weekend and will push up the snapshot of both plugins once it is ready providing the snow does not call me out skiing. The servicegen mojo will construct the classpath from the depenency path of the pom.xml so you will only have to include the ejb artifact in order for servicegen to find it. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -----Original Message----- From: Jeff Bailey [mailto:[EMAIL PROTECTED] Sent: Friday, November 10, 2006 6:43 PM To: [email protected] Subject: Re: Example POM for WebLogic servicegen needed Thanks for the example. That saved me a lot of time! Re: phase for appc, I'm trying to take the approach having one project create the ejb-jar and a separate project create the web services using servicegen. Currently I run appc in the package phase. I thought it might be better to decompose things that way instead of trying to do to much in one project. In fact, I'm starting look into actually having a another project to create the ear. In a nutshell I'd have the following projects: EJB Project - contains my session beans. WebService Project - uses servicegen to create webservices for my sessions beans Web Project - contains my web app EAR Project - Packages the artifacts of the other three packages into the ear for my application. My goal is to separate out the assembly of the EAR and to keep each project relatively simple. I have a few challenges that I need to overcome: 1) servicegen needs to reference the ejb jar as a parameter. I currently have a relative path hardcoded to my ejb project, but what I'd really like to do is reference the ejb artifact. I'm sure this can be done but I need to dig into how to refernce it. Maybe declare the ejb jar as a dependency and somehow reference that in the servicegen call? 2) The WebService project uses servicegen to generate an EAR. I'm really only interested in the war file that's generated by servicegen so it can be packaged into the EAR by my EAR project. I have servicegen configured to generate an exploded ear, but I need to figure out how to make the war that servicegen generates the artifact of my WebService project so that it will be installed in the repository and can be picked up by my EAR project. Hopefully this makes sense. I'd be curious to know if others think by breakdown of maven projects is good pattern or an anti-pattern and if you have any suggestions on how to solve the remaining issues. Thanks, Jeff Dmystery wrote: > > On a different note, what execution phase are you executing the > weblogic:appc? I'm doing it in a pom which first generate sources using > XMLbeans, compiles some aspects, create ejb-jar, ejb-client-jar and then > run weblogic:appc which is in the package phase. The problem is, when appc > is started, it does the whole thing again, XMLBeans to ejb-client-jar. > Just wanna know what phase you have weblogic:appc? > > Thanks. > -- View this message in context: http://www.nabble.com/Example-POM-for-WebLogic-servicegen-needed-tf2604105s1 77.html#a7288485 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- 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]
