What i have right now is a ejb-project, war-project and an ear-project. In the ejb-project i use appc to compile the generated artifact so when i do an install the 'compiled artifact' gets installed in the repository. The war-project uses the compiled ejb artifact. Same for the ear-project, it generates the ear (with compiled ejb and the war), generates Webservices using servicegen, runs appc and then gets installed in the repository. So, i have a fully compiled and webservice ready ear in the repository.
If one is to use seperate projects for servicegen and appc, then what should be the 'packaging' of that project? Also doing so will generate services using the ear in the local project build folders, so how to install the ear again in the repository? This is important for a multi-module project where an 'mvn install' will build all the modules populate the repositiry. I guess the appc should be in an ear or ejb project and the sericegen in the ear project. But my original question still remains - appc in package phase still executes the build twice :( Thanks. Jeff Bailey wrote: > > 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-tf2604105s177.html#a7312860 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
