Link Details

Link 1144167 thumbnail
User 1208553 avatar

By tipiwi
Published: Apr 23 2014 / 07:49

eXo Platform 4.0 has a Tomcat 7 version and a JBoss EAP 6.1 version. In the JBoss version, eXo is packaged as a unique (exploded) EAR containing all the JARs and all the WARs. To install your portlets, the default procedure is to install your WARs and your JARs inside the eXo EAR. This can be done manually (copy the WARs into platform.ear, copy the JARs into platform.ear/lib, then update the application.xml) or with the extension manager. This method has the benefit of being really easy, especially with the extension manager, but it also has some drawbacks: - eXo artifacts and custom portlets artifacts are not well separated - portlets cannot be hot deployed - it can lead to class-path issues if your portlet needs a different version of a JAR already present in eXo Hopefully, there are solutions to avoid all these drawbacks. With JBoss AS 7 (JBoss EAP 6), a new class-path system has been introduced: JBoss Modules.
  • 18
  • 0
  • 1008
  • 777

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Apache Hadoop
Written by: Piotr Krewski
Featured Refcardz: Top Refcardz:
  1. Play
  2. Akka
  3. Design Patterns
  4. OO JS
  5. Cont. Delivery
  1. Play
  2. Java Performance
  3. Akka
  4. REST
  5. Java