Skip to main content

JEAP 6 - 建立Remote Stateless Session Bean

新的 EE 6 與 EJB 3 讓建立 ejb 變得超簡單的!
因為剛好有人問Remote EJB 的問題,就順便介紹怎麼建立囉!

============================================
工具 : JBoss Developer Studio
平台 : JBoss Enterprise Application Platform 6
Java EE 版本: Java EE 6
============================================

1. 請確定你的本機已經安裝JBoss EAP 6 (unzip 後,執行add-user.sh or add-user.bat 加入使用者)
2. JBoss Developer Studio已經正確安裝,並且也設定好的Server. 以下為參考畫面



接下來就可以開始建立我們的第一個 EJB3 專案咧~

1. 在左邊的Project Explorer 上,按下滑鼠右鍵,選擇新建一個ejb的專案

2. 打入Project 的名字 (這個case 我打的是 MyEJBProject),如果你還沒有建立放置ejb 的EAR 檔,選擇 "Add project to an EAR" , 在裡面打上你想要取的EAR 名稱,或是你已經有了EAR 檔,那就選你要的EAR 名稱就好!打好後按下Next

3. 直接按下Next

4. 因為我還不想寫呼叫這個ejb 的client程式,所以先把 "Create an EJB Client to hold the client interface and classes." 的勾勾拿掉。按下Finish


這樣就可以看到我們的Project 完成拉!



5. 建立第一個Remote Session Bean,在ejb的專案中案滑鼠右鍵,選擇New, 然後Others
跳出視窗後,選擇 SessionBean(EJB3.x).

6. 替這個session bean 取名字,這次的session bean 是stateless, 所以選擇stateless. 然後幫這個bean 建立一個對外的remote interface.

7. 按下Finish 完成,之後,會看到自動產生的兩個Java 檔案。

8. 在 Remote interface上面加上我這次要加入的method 名稱。
(你會發現,自動產生的java 程式碼裡面,@Remote 的 annotation已經幫你家好了咧!)

9. 在真正的Bean 裡面寫上我們真正會執行的程式碼。

10. 發佈上Server部署,如果你成功的話,會看到以下的程式碼,表示你成功拉!


11. 寫個Client 程式測試剛剛的Session Bean. 先建立一個Java 的專案,

12. 幫這個Java 專案取個名字


13. 所有EJB 的Client 都必須要使用 JBoss 的jboss-client.jar,不然就call不到哩~所以先到專案上,按下滑鼠右鍵,選擇properties.
                                

14. 在build path 上面,選擇加入 jboss-client.jar 這個外部的jar檔,通常,這個jar檔都會放在JBoss EAP6安裝路徑/bin/client底下.

 


15. 加入剛剛建立的EJB 專案的聯結
 



16.這樣就可以開始寫Client拉~一樣,先建立一個Class

17. 程式碼如下,
package redhat.client;

import java.util.Hashtable;

import javax.naming.Context;
import javax.naming.InitialContext;

import redhat.remotebeans.MyCallerRemote;

public class RemoteStatelessClient {
 public static void main(String ar[]) throws Exception{
        Context context=null;
        try{
         final Hashtable jndiProperties = new Hashtable();
            jndiProperties.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming");
            jndiProperties.put(Context.PROVIDER_URL, "remote://localhost:4447");
            jndiProperties.put( "jboss.naming.client.ejb.context", true );
            jndiProperties.put( Context.SECURITY_PRINCIPAL, "admin" );
            jndiProperties.put( Context.SECURITY_CREDENTIALS, "christina79" );
            jndiProperties.put(Context.INITIAL_CONTEXT_FACTORY, org.jboss.naming.remote.client.InitialContextFactory.class.getName());
            context = new InitialContext(jndiProperties);
            
        }catch (Exception e) {
              e.printStackTrace();
        }


        MyCallerRemote remote=(MyCallerRemote)context.lookup("ejb:MyEJBProjectEAR/MyEJBProject/MyCallerBean!redhat.remotebeans.MyCallerRemote");
        System.out.println(remote.callMyName("Christina"));
     }
 
}

18. 然後按滑鼠右鍵執行為Java Application, 如果成功,你就會看到以下的結果拉!



Comments

Popular posts from this blog

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

jboss-devstudio-9.0.0.GA-installer-eap.jar
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 …

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 …