• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Project organization JSF 1.2 / EJB3 with Maven2 - How?

 
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I already did some EJB3/JSF projects and know how to deploy them as EAR on JBoss. To do this i used 3 projects in Eclipse (EAR project, JSF project and EJB3 project). Now i would like to start with maven. I am very new to this and wonder if its possible with maven to deploy ONLY the JSF or the EJB part without having to deploy the whole EAR file. Reason is that it could be that only web changes took effect, but the EJB is already finished. In my concrete case I am planning to get some web developer and I only want him to be allowed to checkout the JSF project and deploy that part into the JBOSS without having to deploy EJB and without having access to that EJB project source code. I guess a JAR of the EJB project should be enough for the JSF module / this web developer. But how is this setup in Eclipse / Maven2 using standard Spring 3?
 
author
Posts: 3285
13
Mac OS X Eclipse IDE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I think you may need to look at Cargo or Jboss plugins? Maybe the deploy plugin with options can also help here
 
Ray Blue
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
actually it was quiet easy at last (after i found maven). The jsf project must not include the sources or any reference to the EJB project inside eclipse. In the next step the ejb and jsf project both need a pom. And finally i set a dependency in jsf to ejb with only compile time scope. So the source could be compiled, but the exported war file doesnt contain any ejb jars anymore and the ejb can simply be deployed apart from jsf ;)
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic