Configuring JBoss shared libs

One popular question in JBoss forums is the correct placement of shared libraries with Enterprise Application deployed on JBoss. In this short tutorial we will show the available options.
A typical Enterprise application is made up of a Front-end Layer, a Persistence Layer and some common Classes referenced by both layers.

 

Placing the common Classes in an EAR archive allows the EJB and Web Classloader to resolve correctly the utility Classes referenced, however you have to instruct JBoss about these Classes. You have basically three options for referencing utility Classes:

 

Option 1: Declare the shared libs in application.xml

 

jboss common shared libs

This is the most portable solution, since the application.xml descriptor allows your application to declare external Java modules by adding the <Java> module.
Here's an example:

<application>  
   
  <module>  
    <web>  
      <web-uri>TestWeb.war</web-uri>  
      <context-root>testWeb</context-root>  
    </web>  
  </module>  
    
  <module>  
    <ejb>TestEJB.jar</ejb>  
  </module>  
     
  <module>  
    <java>Utility.jar</java>  
  </module>  
      
</application>  

 

Option 2: Place the libraries in the "lib" folder
jboss shared libs common
By placing libraries or configuration files in the "lib" folder (at the root of your EAR), you will be able to resolve your class/files without the need to add any configuration.
Though this is the fastest solution, it might not be supported in all application servers. For example Bea Weblogic uses the APP-INF/lib to load common libraries

 

Option 3: Add a jboss-app.xml configuration file
jboss common shared libs
If you want even more customization for your application, you can use a JBoss specific deployment descriptor, namedjboss-app.xml which is to be placed in the META-INF folder of your EAR.
Here's a sample of it:

<?xml version='1.0' encoding='UTF-8'?>  
<!DOCTYPE jboss-app PUBLIC "-//JBoss//DTD J2EE Application 5.0//EN"  
"http://www.jboss.org/j2ee/dtd/jboss-app_5_0.dtd" >  
<jboss-app>   
<library-directory>APP-INF/lib</library-directory>  
</jboss-app>
 

The advantage of this solution is that you can choose any location for your libraries. The cons is that it is not portable across another application server.

资源下载链接为: https://pan.quark.cn/s/22ca96b7bd39 在当今的软件开发领域,自动化构建与发布是提升开发效率和项目质量的关键环节。Jenkins Pipeline作为一种强大的自动化工具,能够有效助力Java项目的快速构建、测试及部署。本文将详细介绍如何利用Jenkins Pipeline实现Java项目的自动化构建与发布。 Jenkins Pipeline简介 Jenkins Pipeline是运行在Jenkins上的一套工作流框架,它将原本分散在单个或多个节点上独立运行的任务串联起来,实现复杂流程的编排与可视化。它是Jenkins 2.X的核心特性之一,推动了Jenkins从持续集成(CI)向持续交付(CD)及DevOps的转变。 创建Pipeline项目 要使用Jenkins Pipeline自动化构建发布Java项目,首先需要创建Pipeline项目。具体步骤如下: 登录Jenkins,点击“新建项”,选择“Pipeline”。 输入项目名称和描述,点击“确定”。 在Pipeline脚本中定义项目字典、发版脚本和预发布脚本。 编写Pipeline脚本 Pipeline脚本是Jenkins Pipeline的核心,用于定义自动化构建和发布的流程。以下是一个简单的Pipeline脚本示例: 在上述脚本中,定义了四个阶段:Checkout、Build、Push package和Deploy/Rollback。每个阶段都可以根据实际需求进行配置和调整。 通过Jenkins Pipeline自动化构建发布Java项目,可以显著提升开发效率和项目质量。借助Pipeline,我们能够轻松实现自动化构建、测试和部署,从而提高项目的整体质量和可靠性。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值