Skip to main content

JEAP 5 - Shared Library設定

通常在JBoss 裡面,如果有遇到不同的Application 需要共用一些JAR的檔案,我們都會請他放在 JBOSS_INSTALL_PATH/server/$PROFILE/lib 下。

這種Loading 的方式,會將EAR 與 這些library 分別Load 近來。

因此,load 之後,兩個 EAR 都會對應到同一個 Load 進來的Library的instance.

使用者希望可以把這些jar檔放在一個位置,以後只要更新一個地方,其他對應的EAR 只要look up 這些更新得檔案就好了。

通常,一般的Class 這樣子就好了。因為大部份的API 在同一個Server instance 下是可以共用的。這樣也比較省memory。

可是這位客戶,它的Library裡面因為會需要hold 住每個EAR instance 給它的值,所以是無法提供共用的。

因此,他希望每個Library 都存在每個獨立EAR isolation 的裡面,不要互相影響。

照現行的deploy的做法是沒辦法做到 isolation 的。

唯一的方法就是在JBoss deploy 的時候去定義,讓他在load EAR 的時候也去look up 設定的library 位置。

所以,必須要客制化一個deployer 讓它可以在EAR Level 的時候lookup 檔案,做到這一層的isolation.

在網路上找到一個Sample Code, 它的做法是extend JBoss 原有的UrlIntegrationDeployer,這支程式會把程式掃到的URL File load 進去。 所以要改的工,變得簡單了。

1. 先建立一個JMX Bean, 指定需要額外讀取的檔案。
2. 找一個可以實作isIntegrationDeployment的method. (PathUrlIntegrationDeployer)

接下來只要將檔案放到JBOSS_INSTALL_PATH/server/$PROFILE/deployer 下,修改裡面loading 的位置就好囉!


另外,還有EAR isolation 的修改。
如果想要每個EAR 的 domain 獨立的話,JBOSS_INSTALL_PATH/server/$PROFILE/deployers/ear-deployer-jboss-beans.xml  裡面,isolated 改成 true

<bean name="EARClassLoaderDeployer" class="org.jboss.deployment.EarClassLoaderDeployer">
      <!-- A flag indicating if ear deployments should have their own scoped
         class loader to isolate their classes from other deployments.
      <property name="isolated">true</property>


Popular posts from this blog

Red Hat JBoss Fuse - Getting Started with Fuse Integration Service 2.0 Tech preview

I just realized that I did not do a getting started for Fuse Integration Service 2.0 Tech preview before I did the pipeline demo, thanks for those of you who reminded me! :)

To get started with FIS 2.0, for people who has just getting to know the technology, here is how I interpret it. Basically, it's divide into two aspect,

1. Integration development, FIS uses Apache Camel as the core technology that creates, orchestrate, compose microservices into a super lightweight thin integration layer, and become the API provider and service orchestrator through exposing RESTful or messaging service endpoints. And you can choose to either package and run it with Spring-Boot or Karaf.

2. Application Deployment and Management, FIS takes advantages of OpenShift platform, and allows you to separately deploy the micro-integration service among distributed environment, at the same time takes care of the failover, high availability, load balancing and service lookup problem for you.

So, now we know …

Red Hat JBoss Fuse/A-MQ - Fuse and A-MQ Version 6.3 GA is released!

Fuse and A-MQ 6.3 GA has just went out. Maybe, you would think this is just only a minor version release why should I care? Hold your thoughts on that! Because they have done a lot of improvements and also added many new features into this release.

Besides various bug fixes and making sure Fuse Fabric is much more stable. There are two major change in this version update:

New Tooling in JBoss Developer Studio (JBDS) 9.1 GA. Newer Apache Camel version – Camel v2.17. I was really impressed by the work put in to make developing Camel application much simpler. First is the installation of tooling itself. Now it has a all-in-one installer so you don't need to worry about which plugins you need to check. See the videos below to see the new "Getting Started" of Fuse 6.3.

And If you notice from the above video, the presentation of camel route in JBDS has also updated. It fixed some of the miss representation of logic and making it easier to read.

Old Camel Route
New Camel Route
On …

Fuse Integration Service - Setup JBDS and create first quickstart application

Before we go and start creating our first application, I want to show you how to setup your JBoss Developer Studio, create a small application from the quickstart example and then running it on Fuse Integration Service.

I am using JBoss Developer Studio version 9, you can find it here.
After download the

double-click it, and start installing with default values.

After successful installation, we will need install the plugins for Fuse, on JBoss Central view, select software update, select enable early access.

And select JBoss Fuse Development for the plugin,

Click on install, and we are all set to go!

First thing first, we want to create a Fuse project to deploy on the base of Fuse Integration Service, which is OpenShift. If you have not installed it, please go back to my previous post for instructions. So on your JBDS, right click and start creating the project. Select new, maven project, if you have installed the plugin correctly, you should …