Finalmente a alternativa que faltava chegou a nossos ambientes. O glassfish, servidor de aplicações da sun inspirado no famoso pacote SunOne tomou a frente dos produtos open source e salvou a vida de nós desenvolvedores.

Com recursos interessantes, alto poder de processamento e grande facilidade de configuração, instalação e uso, promete ser o melhor dos produtos deste genero este ano.

Confira em.: http://java.sun.com/javaee/community/glassfish/

Disponível para quase todas as plataformas incluindo MAC.

"mengapa?"

tentunya saya punya alasan tersendiri :D

tapi alasan saya belum tentu bagus untuk anda, dan alasan anda belum tentu bagus juga untuk saya :D

walaupun saya sudah migrasi dari Struts1 ke Struts2 trus akhirnya ke JSF sudah lama, tapi pura-puranya saya baru migrasi sekarang :D , hehehe.

JSF

saya pindah dari struts1-->struts2 dan akhirnya ke JSF karena ketika pertama kali saya belajar JSF disitu saya melihat ada kesamaan antara konsep JSF dan Swing. yaitu berbasis komponen. sehingga hal ini membuat pembuatan halaman web sangat mudah karena berbasiskan komponen, artinya kita membuat halaman web seperti mendesain form dalam aplikasi desktop :D

dan selain itu JSF juga mendukung Dependency Injection yang mencakup scope untuk aplikasi website seperti request, session dan application :D , sehingga ini bisa digunakan sebagai pengganti DI-nya milik Spring :D

EJB

namun untuk total migrasi dari Spring ke EJB secara total mungkin baru sekarang ini, walaupun pertamanya saya belajar EJB lalu Spring dan sekarang saya balik lagi ke EJB :D

sebenarnya banyak orang enggan menggunakan EJB karena dulu ketika EJB masih versi 2.x, EJB dikatakan sebagai nighmare (mimpi buruk) bagi pengembang, entah saya juga kurang tahu karena saya mempelajari EJB sejak versi 3, dan menurut cerita penggunaan EJB 2.x sangat komplex dan memakan resource yang boros. :D

dan untungnya, pihak pengembang tidak putus asa dengan kegagalan EJB 2.x, sehingga sekarang saya bisa menikmati kemudahan dan kehebatan EJB 3.0 (yang katanya sebentar lagi mau keluar EJB 3.1) :D

Sebenarnya, kemampuan EJB tidak terlalu dapat dibanggakan dengan Spring Framework yang udah begitu banyak, namun disini saya menitik beratkan EJB dan Spring sebagai busines layer, bukan yang lainnya.

satu hal yang menjadi daya tarik EJB adalah kemampuan Injectionnya yang hanya dengan menggunakan annotation @EJB, tanpa melakukan konfigurasi seperti di Spring. hal ini memudahkan kita untuk memanggil komponen EJB secara langsung tanpa harus menginjeknya lewat metode setter atau lewat konstruktor seperti yang dilakukan Spring.

Namun harus di perhatikan jika EJB hanya dapat berjalan pada server yang mendukung JEE, sehingga jika kita menggunakan server seperti Tomcat dan GlassFish v.3, maka EJB tak akan berjalan karena server-server tersebut hanya digunakan untuk WebServer, so untuk menjalankan EJB kita perlu menggunakan server seperti JBoss ato GlassFish v.2

JPA

jpa sebenarnya merupakan spesifikasi yang tergabung dalam EJB yang dinamakan EJB-Entity. namun JPA tidak selalu harus berjalan bersama EJB, karena JPA juga dapat berjalan dalam aplikasi desktop ato web sama seperti Hibernate ato TopLink.

Sebenarnya JPA bukanlah sebuah framework untuk persistence, tapi merupakan spesifikasi seperti JDBC, sehingga untuk menjalankan JPA kita memerlukan implementasinya seperti menggunakan TopLink, Hibernate, EclipseLink, OpenJPA, KODO dan yang lainnya.

sehingga JPA bisa dikatakan sebagai JDBC tingkat tinggi :D (ngarang), karena emang penggunaannya sangat mudah dari pada JDBC dan hampir mirip seperti Hibernate.

hanya saja karena JPA merupakan spesifikasi yang bisa diimplementasi oleh berbagai framework, sehingga bisa dibilang JPA kurang komplete jika dibandingkan dengan Hibernate, terutama dalam hal Query.

namun alasan kenapa saya memilih JPA karena hal pertama adalah JPA merupakan kesatuan EJB, sehingga penggunaannya sangat mudah dengan EJB, dan selain itu dengan bantuan EJB proses transaksi untuk JPA jadi mudah karena kita tak perlu memikirkan "TRANSACTION" untuk proses-proses persistence yang kita lakukan karena semuanya di handle langsung oleh EJB.

Dan yang paling bermanfaat adalah JPA dapat diinjek hanya dengan menggunakan annotation @PersistenceContext atau @PersistenceUnit, sehingga penggunaannya semakin mudah, dan hal ini tanpa bantuan EJB ato Spring, sehingga andai kita tak menggunakan EJB, kita tetap bisa melakukan injeksi ke JPA

Facelets + SEAM

Facelets dan SEAM merupakan framework yang patut digunakan jika kita menggunakan JSF+EJB+JPA, karena :

dengan facelets kita dapat dengan mudah menkoneksikan antara JSP dan JSF yang kadang ditemukan berbagai kendala seperti dalam "ExpressionLanguage" misalnya. dan selain itu dengan facelets, pembuatan halaman web dapat berbasiskan template, sehingga mempermudah pembuatan halaman web ketika kita memerlukan halaman yang banyak namun memiliki kesamaan layout.

dengan SEAM, kita dapat dengan mudah mengintregasikan antara JSF dan EJB, dan selain itu SEAM mendukung facelets dan SEAM juga memiliki kemampuan yang banyak seperti kemampuan untuk menampilkan Chart, kemampuan membangun RSS, integrasi untuk Email, dan lainnya. Dan semua itu berbasiskan JSF dan EJB, sehingga SEAM akan membuat pengguna JSF dan EJB lebih termanjakan, hahahaha :D

tapi tidak selamanya pendapat saya sesuai dengan keinginan anda bukan?

itu tergantung selera :D

see you!!!

http://java.sun.com/products/ejb/

https://facelets.dev.java.net/

http://www.seamframework.org/

http://www.hibernate.org/

http://www.springframework.org/

http://struts.apache.org/

http://struts.apache.org/2.x/

Simply:
1. Download MySQL 5.1 Community Edition and GlassFish v2 Update Release 2 (UR2).
2. Develop a cool web application using the combination.
3. Create a project of your application at java.net.
4. Write a review of these products and post it in your blog.
5. Submit your java.net project's URL and your review's URL.
6. Do it before October 22, 2008.

How to Enter

To participate, do the following:
1. Develop an innovative web application that uses MySQL 5.1 Community Edition database and GlassFish v2 UR2 application server. You can develop in any of the following languages: Java, PHP, Python, or Ruby. You must submit complete source code of the application, user documentation, developer/administrator documentation including application installation instructions, and appropriate executables. You must make all these deliverables available as a project at java.net. Provide your project's URL in the Submission Form below.

2. Write reviews of MySQL 5.1 Community Edition database and GlassFish v2 UR2 application server based on your experiences as you developed the web application. You must post the review in a blog or on a web page, and you must provide the corresponding URL in the Submission Form below.

The developed application and the reviews must be new material that you have written and not copied from something that you or others have already developed or published.

Finally, complete the submission form, and if you have any questions, submit a contact request.

Deadline
Contest starts: September 2, 2008
Submission deadline: October 22, 2008
Judging period: October 23 - November 20, 2008

Winners announced: November 21, 2008

For more information please look at here

The ip for the server, 172.25.133.69 which alias to http://nas.amc.xxx.gov and Default Web Module is "Root" app.

Dilemma: We wanted to set up a virtual server for a new URL, http://idms.amc.xxx.gov and register the Default Web Module to " iDMSCommingsoon" app.

How the world can we do that?  We are not running any Appache on top of Glassfish,  is Glassfish smart enough to figure it out which application to respond based on URL, etc.  The answer is YES. It is so easy to set that up by using Glassfish admin tool.

Solutions:  Here are few choices I had, were recommended by Sun's Technician:
"I'm sure you know this, but it bears mention now. A combo of IP+Port number can have only one process/program binding to it... thus if you have 1 IP address, any port there, can be "used/bound to" only once. This is true for all Web or App Servers or any Server for that matter.

The SJAS/Glassfish, works around this limitation by using the concept of Listeners and Virtual Servers.
A Listener can be instructed to listen/respond to different domains (web domains, not App Server domains) such as www.aaa.com and www.bbb.com
You can then have and configure your Virtual Servers to use those listeners.

Couple of scenarios you could approach.
-If you have available more IP addresses, you can create another listener, assign it to use Port 80 and create your Virtual Servers to use it.
Or
-If you have only one IP available, you can modify existing listener to also respond to new site (idms.faa.gov) and configure the new Virtual Server to use
the same listener.

Either way, DNS will need to be modified accordingly, whether you point 1 domain (HTTP domain, not App Server domain) to that IP or have 2 or more domains pointing to that IP (absolutely possible).

More about it can be seen here:
http://docs.sun.com/app/docs/doc/819-3671/ablsw?a=view"

This is how we have tackled this issue initially:
1. We have aliased http://idms.amc.xxx.gov to the same ip 172.25.133.69 as the other URL has been using for years.
2. We have changed few things on setting as follows.

You may notice that idms Virtual Server is using the same Listeners for other server, so they are sharing listeners.

3. Here is the same old way to deploy a .war but only thing I have changed is server name.

What a surprise, it worked!
Here is my lame drawing to show the big picture.

Concern: I have a concern about performance.   Since both URLs are using same ip and listeners, what are chances for the bottleneck when both URLs starting get many hits simultaneously.

Netbeans is AMAZING at creating web services, the tools are incredibly rich.

But this error dogged me. I had one or two web services that worked and others that didn't. To set up my service I had set up some inner classes

public static class dtaData {
private String Name;
private String date;
private String sid;
}

then created a web services that returned a LIST of those objects:-

    @WebMethod(operationName = "Data")
    public List Data() {
        List result=new ArrayList();
       for (int i=0;i<20;++i) {
        dtaData DataObject=new dtaData ();
       DataObject.sid=""+i;
       result.add(Result);
     }

        
        return result;
    }
  

And it falls over with this error when you test the webserver. HOWEVER The problem is caused because there is no web service DIRECTLY returning the dtaData class. The solution is to create a web service that returns null but has dtaData as the returning Object.

e.g.

    @WebMethod(operationName = "testData")
    public dtaData testData() {
           return null;

    }
   

These errors are given when the problem occurs:-

On the glassfish server

Caused by: javax.xml.ws.WebServiceException: javax.xml.bind.MarshalException
 - with linked exception:
[javax.xml.bind.JAXBException: class PHJ.Agenda$ICDB_Agenda_data nor any of its super class is known to this context.]
        at com.sun.xml.ws.message.jaxb.JAXBMessage.writePayloadTo(JAXBMessage.java:322)
        at com.sun.xml.ws.message.AbstractMessageImpl.writeTo(AbstractMessageImpl.java:142)
        at com.sun.xml.ws.encoding.StreamSOAPCodec.encode(StreamSOAPCodec.java:108)
        at com.sun.xml.ws.encoding.SOAPBindingCodec.encode(SOAPBindingCodec.java:258)
        at com.sun.xml.ws.transport.http.HttpAdapter.encodePacket(HttpAdapter.java:320)
        at com.sun.xml.ws.transport.http.HttpAdapter.access$100(HttpAdapter.java:93)
        at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:454)

On the web service test return:

Exceptions details : java.lang.reflect.InvocationTargetException

Ok, lets start with WebSynergy, the very cool thing out there by the colloberation of Sun, Liferay!

Now, our dream development package includes liferay portal + Glassfish server with lots of capabilities i.e. SAW, openESB + Netbeans IDE (I still prefer Eclipse!)+ PortalPack + Groovy DSL/Grails support + Spring + hibernate + MySQL

Ok, if you want to use all these into your company's project, wouldn't it be smart to think of a GEnIUS Build tool to automate getting these sources into one updated package for you to use in development or for production!!

I think that would be incrediably cool to have such tool inhouse while you are developing, I think this calls for a new jcp proposal!

what do you think?

Organized By: Sun Microsystems

Key Dates:
Deadline for Submissions: October 22, 2008

For Whom:
Participant must be enrolled as a student pursuing a degree in an educational institute

Sun Microsystems has yet again announced the Student Review Contest. This time one has to use MySQL and GlassFish and develop a web application and then write a review on MySQL and GlassFish.

Download MySQL 5.1 Community Edition and GlassFish v2 UR2 application server. Check them out for yourself by developing a web application. After you have a chance to use both the products, write reviews to tell the world what you think. A panel of judges will review all submissions and select the winners.

The contest will have two groups: one for students who are not Sun Campus Ambassadors, and another comprising Sun Campus Ambassadors. For each group, there will be a grand prize of $500 in Visa debit card, and five second prizes of $250 each in Visa debit card.

How to participate:
1. Develop an web application using MySQL and GlassFIsh and then host it on java.net
2. Write a review on MySQL and GlassFish in your blog.

Use the Entry Submission link and submit the entries.

More details can be found here and in the Student reviews Blog.

Subscribe to Geek RSS Feed here.
Subscribe to Let Me Know RSS Feed here.

Server 1 - The "Controller" (machine 1, 192.168.100.10)

1. Install the SUN Application server make sure you select

- Do not require username/password
- Create a windows service (otherwise it wont stay running)
- Do not start the server from the INSTALLATION PROGRAM, use control panel, administration tools, services and start the service from there.

2. Login to the GUI http://localhost:4848

3. Select ADD CLUSTER SUPPORT - you will have to restart the server. Do NOT do this through the windows instead restart the service - Start, Control Panel, Admin Tools, Services, find SUN APPLICATION SERVER and RESTART

4. Login to the GUI http://localhost:4848 - Click on CREATE NEW CLUSTER

Enter the name and click OK now the cluster has been created (in this case i'll use cluster1)

5. Create the first NODE. (this has to be done at the dos prompt)

Start, RUN, CMD, OK

cd \Sun\appserver\bin<ENTER>

asadmin<ENTER>

You will get a asadmin> prompt.

on each machine in the cluster you have to create and start a node agent

create-node-agent --host localhost --port 4848 nodeagent1

create an instance for this node agent

create-instance --host localhost --port 4848 --nodeagent nodeagent1 --cluster cluster1 instance1

now start the node agent

start-node-agent --syncinstances=true nodeagent1
(just hit enter on the master password)

at this point you have created and set up the first cluster machine which will control the cluster - so all your cluster admin will be done from this machine.

Exit asadmin

exit

then exit the command box

exit

Setting up Cluster Server clients (machine 2, 192.168.100.11)

1. Install the SUN Application server make sure you select

- Do not require username/password
- Create a windows service (otherwise it wont stay running)
- Do not start the server from the INSTALLATION PROGRAM, use control panel, administration tools, services and start the service from there.

2. Login to the GUI http://localhost:4848

3. Select ADD CLUSTER SUPPORT - you will have to restart the server. Do NOT do this through the windows instead restart the service - Start, Control Panel, Admin Tools, Services, find SUN APPLICATION SERVER and RESTART

4. Create a node agent, start, run cmd ok

Start, RUN, CMD, OK

cd \Sun\appserver\bin<ENTER>

asadmin<ENTER>

You will get a asadmin> prompt.

on each machine in the cluster you have to create and start a node agent

create-node-agent --host 192.168.100.10 --port 4848 nodeagent2

create an instance for this node agent

create-instance --host 192.168.100.10 --port 4848 --nodeagent nodeagent2 --cluster cluster1 instance2

now start the node agent

start-node-agent --syncinstances=true nodeagent2
(just hit enter on the master password)

at this point you have created and set up a cluster "client"

Exit asadmin

exit

then exit the command box

exit

Now you have your two cluster machines working.

Deploying a Netbeans Project to the Cluster

1. Make sure it's running locally
2. Change the database settings in netbeans to point to the LIVE database if it is different and make sure it runs still
3. Deploy the app to the main server in the cluster
4. Login to the GUI and go through the JDBC connectors and enable them for the cluster
5. Test the application in SINGLE USER mode (normally port 8080) and make sure it all works.
6. Go into APPLICATIONS, MANAGE TARGETS for your app and deploy it to the cluster

I will be putting up a tutorial on load balancing as well shortly.

PS: the issue is also discussed in this thread on the GlassFish forum here.

It is a Java EE 5 implementation, like JBoss.

It is the reference implementation of Java EE 5.

While those two sentences look very similar, there are huge differences between them.

前回のブログの問題はおいといて、NetBean IDEを使って、MyarchのWSDLから、Web Serviceのコードを作成することにする。問題なくうまく作成された。ヴェリファイもうまくいく。Glassfishサーバーにディプロイしようとすると、エラーが起こる。NetBean IDEのディプロイBuildでは、成功というが、Glassfishサーバーの、Output には、Exceptionエラーが見える。この問題を解くには、自分の技能は、足りないので、メトロのベーシックサンプルにもどってMyarchの例を動かしてみよう。どうなるか？もうひとつ気になることは、ヴェリファイの時、Web　Serviceは、JAX-RPCを使用というではないか。WSDL では、Document/Literalスタイルを使っているのに。

Congratulations! Sun Microsystems is pleased to inform you that you have been selected as a
potential winner in the GlassFish Community Innovation Award Program. If your entry is verified,
as explained below, and you are confirmed to be an eligible entrant, you will be entitled to receive
a cash prize in the amount of $313.00 less applicable withholdings.

I know! "potential winner" Gee + Fancy!

It's still pretty cool, to get payed for something I was going to anyways

The bug I found in Glassfish was pretty obscure: WebSecurityManager.checkPermission NPE with custom JACC impl, and pretty boring even though it may sound exciting since it was in tehe security infrastructure, I can't think of any possible way it could be exploited even if it wasn't already patched.

Still... I'm pretty happy about it. Not only have I gotten a ton of use out of Sun's really superior application server Glassfish. Now they are even paying me to use it!

Top that JBOSS! Send me $$$!!! You too WebSphere! Where is my $$$???

How to participate?

• Download MySQL and Glassfish.
• Use the to create a Web Application ( Using any Programming Language- Java ,PHP, Ruby or Python)
• Submit complete source code of the application, user documentation, developer/administrator documentation including application installation instructions, and appropriate executables as a project at java.net
• Write reviews of MySQL 5.1 Community Edition database and GlassFish v2 UR2 application server based on your experiences as you developed the web application.

What to submit for the event?

• Submit the Link to the java.net project
• Submit the Blog link of the review written.

Use the Submission form for both of them.

The contest is held in two categories

• Categrory 1: For all Sun Campus Ambassadors
• Category 2: For all Non Sun Campus Ambassadors

Prizes:

Separate prizes for each category

• Grand prize of $500 in Visa debit card.
• Five chances to win a prize of $250 in Visa debit card.

Deadline for Submitting the Contest entries: October 22, 2008

So get started now to gift u'r self a Visa Debit Card.

Visit the Official Contest page here.

Visit the blog post on Student Veiws and Reviews here.

Use MySQL database and GlassFish application server to develop a web application and write a review for...

• A chance to win a grand prize of $500 in Visa debit card, and
• Five chances to win a prize of $250 in Visa debit card

Simply:
1. Download MySQL 5.1 Community Edition and GlassFish v2 Update Release 2 (UR2).
2. Develop a cool web application using the combination.
3. Create a project of your application at java.net.
4. Write a review of these products and post it in your blog.
5. Submit your java.net project's URL and your review's URL.
6. Do it before October 22, 2008.

The Sun Student Reviews site has all the details, so does the contest page.

And here is a nice flier for you.

Good luck and have fun!

for the last two days I've been trying to make a Silverlight client consume a Glassfish JAX-WS Web Service, but without any success till a few hours ago. I tried the procedure indicated at "Call a Java EE Web service from Silverlight Client" on the MSDN blogs (the only one I could find) but it didn't work. That blog post says that the solution is copying an xml file called clientaccesspolicy.xml in the docroot folder of the GlassFish domain where the web service resides. I found that when you add a GlassFish WS web reference to a Silverlight project, Visual Studio (I use the Professional 2008 version) creates a configuration file that gives compilation problems, unless you manually change the "customBinding" to "basicHttpBinding" and manually add the endpoint. When I ran the Silverlight client it launched a CommunicationException due to a "cross-domain configuration error". I had already copied the clientaccesspolicy.xml file on the docroot folder of my GlassFish domain as indicated on the msdn blog.

Then, after some hours, I had the idea of creating an ASPNET Web Service which acts as a wrapper for my GlassFish WS, but I found out that neither that would work and it would launch the same exception! I started to have strong suspicions that this was a Silverlight bug. I completely erased the existing project which didn't work and created a new one, adding the web references normally (not manually). In this way it finally worked!

Just out of curiosity I tried adding another web reference to the Silverlight project to my original GlassFish WS, having to change the configuration file manually as before. It not only didn't work, but it also caused the other (.NET) web service to stop working, even after I had removed it completely and had restored the configuration file to the original state. It's so ridiculous! Silverlight is good looking, but still not serious enough for interoperability.

Cheers.

As part the improved security, each component of the system (webserver, database) runs in its own virtual machine, and only has the bare minimum access to files and other services that it needs.  When setting these up, I have to ssh to each component individually.  Access is provided to the seperate components by having a different ssh port on one externally available IP address.

Typing in "ssh -p 7543 dobes@543.32.54.32" with varying port numbers, usernames, and IP addresses can be a pain.  Today I found out that you can specify aliases in your ssh configuration that set up connection options, hostnames, and IP addresses.

Simply edit ~/.ssh/config and put sections like:

Host glassfish-live

HostName 543.32.54.32

Port 7543

User dobes

Compression on

IndentityFile  ~/.ssh/id_rsa_live

Each time ssh finds "Host" it treats the settings that follow as specific to that host, and "HostName" tells it the "real" host to connect to.  These aliases are a great shortcut and I was so pleased to discover them I couldn't wait to share them.

Hope you make good use of this one ...

1. Download & install

Kedua software tersebut bisa didownload sekaligus di http://download.netbeans.org/netbeans/6.1/final/. Install netbeans dan glassfish di komputer Anda dengan mengikuti wizard.

2. Setup Project

Start Netbeans, pilih menu File -> New Project.
Pada dialog New Project, pilih categori Enterprise -> Enterprise Application, klik Next.

Masukkan nama project TestEnterpriseProject.

Pilih Server Glassfish V2, Java EE Version 5, dan pastikan Anda mengaktifkan pilihan Create EJB Module dan Create Web Application Module, kemudian klik Finish.

Maka Netbeans akan mengcreate project TestEnterpriseProject sebagai project utama, project TestEnterpriseProject-ejb sebagai sub-project untuk modul EJB, dan TestEnterpriseProject-war sebagai sub-project untuk modul web.

Struktur project seperti tampak pada gambar berikut:

3. EJB module

Ada 3 macam EJB dalam spesifikasi EJB versi 3.0 (EJB3) :

a. Session Bean
Session bean adalah EJB yang digunakan untuk mengeksekusi proses. Isi dari Session Bean ini biassanya berupa kata kerja (transfer, pay, calculate, updateData, dll). Stateless Session Bean (SLSB) adalah Session Bean yang tidak menyimpan state (keadaan) pada setiap kali eksekusi. Berbeda dengan Statefull Session Bean (SFSB) yang dapat menyimpan state. State ini dapat kita gunakan misalnya untuk menyimpan informasi user atau barang-barang yang sudah dibeli (pada kasus online shop).

b. Entity Bean
Entity Bean adalah EJB yang digunakan untuk mempermudah manipulasi database. Konsepnya adalah Object - Relational Mapping (ORM) yang berarti memetakan object dengan data di dalam database. Entity Bean sebenarnya adalah spesifikasi "bawaan" dari versi EJB sebelumnya yaitu EJB 2.1. Dalam EJB3, ada API lain yang lebih sederhana yaitu Java Persistence API (JPA). Sekarang orang lebih banyak menggunakan JPA dibandingkan Entity Bean.

c. Message Driven Bean
Message Driven Bean (MDB) adalah EJB yang digunakan untuk keperluan messaging menggunakan Java Messaging Service (JMS).

Kali ini kita akan menggunakan Stateless Session Bean. Session Bean karena kita akan melakukan pertihutang matematik, Stateless karena kita tidak perlu menyimpan informasi apapun.

Klik kanan di sub-project EJB, pilih New -> Session Bean. Masukkan properties berikut:
EJB Name: CalculatorSession
Package: suhearie.blog.enterprise.ejb
Session Type: Stateless
Create Interface: Local

Netbeans secara otomatis akan meng-create class CalculatorSessionBean sebagai bean class dan CalculatorSessionLocal sebagai interface. Untuk membuat Session Bean, kita membutuhkan sebuah interface dan sebuah class. Interface digunakan untuk menentukan method apa yang bisa dipanggil oleh client, sedangkan bean class merupakan implementasi dari method tersebut.

Business Logic Interface - Local
Interface CalculatorSessionLocal diberi annotation @Local, artinya interface ini bisa diakses oleh client yang "local" atau berada dalam JVM yang sama dengan EJB server. Client yang kita gunakan adalah web component (JSP dan Servlet) yang berjalan di application server yang sama, sehingga kita cukup menggunakan Local interface. Di interface ini, kita hanya mendefinisikan satu method saja yaitu calculate yang menerima parameter-parameter berupa OPERATION, operand1 dan operand2.

[sourcecode language='java']
package suhearie.blog.enterprise.ejb;

import javax.ejb.Local;

/**
*
* @author sarianto
*/
@Local
public interface CalculatorSessionLocal {

public enum OPERATION {ADD, SUBSTRACT, MULTIPLY, DIVIDE};

public int calculate(OPERATION operation, int oper1, int oper2);

}
[/sourcecode]

Bean Class - Business Logic Implementation
Class CalculatorSessionBean adalah implementasi dari interface CalculatorSessionLocal. Kita menandainya dengan annotation @Stateless yang berarti kita mendefinisikannya sebagai Stateless Session Bean. Pada implementasi method calculate, kita melakukan perhitungan matematika yang sebenarnya.

[sourcecode language='java']
package suhearie.blog.enterprise.ejb;

import javax.ejb.Stateless;

/**
*
* @author sarianto
*/
@Stateless
public class CalculatorSessionBean implements CalculatorSessionLocal {

public int calculate(OPERATION operation, int oper1, int oper2) {
switch(operation) {
case ADD:
return oper1+oper2;
case SUBSTRACT:
return oper1-oper2;
case MULTIPLY:
return oper1*oper2;
case DIVIDE:
return oper1/oper2;
default:
throw new UnsupportedOperationException("Not supported yet.");
}
}
}
[/sourcecode]

4. Web Module

Kita akan menggunakan web sebagai user inteerface. Komponen yang akan digunakan adalah Servlet dan JSP.

a. Servlet
Servlet adalah komponen web yang berupa java class yang mengextends javax.servlet.http.HttpServlet. Class ini biasanya digunakan untuk menangani http request, melakukan processing, kemudian memberikan hasil processing tersebut ke halaman JSP untuk ditampilkan di browser. Konsep ini disebut Model-View-Controller (MVC).

b. Java Server Page (JSP)
JSP mirip dengan PHP atau ASP yang merupakan halaman HTML yang dapat disisipi dengan kode java (scriplet). Tujuannya untuk memudahkan developer dalam merancang user interface.

File index.jsp, kita gunakan untuk membuat form html yang akan mensubmit parameter-parameter yang digunakan untuk melakukan perhitungan. Netbeans sudah menyediakan file index.jsp ini di dalam folder TestEnterpriseProject-war -> Web Pages. Edit file tersebut sehingga menjadi seperti berikut. Form html disubmit ke servlet (CalculatorServlet), yang sesaat lagi akan kita buat.

[sourcecode language='html']

Welcome to Java EE Calculator Test Project !

[/sourcecode]

Create servlet, dengan cara klik kanan di module TestEnterpriseProject-war, pilih New -> Servlet. Isikan class name CalculatorServlet, dan package suhearie.blog.enterprise.servlet. Klik next, pastikan option untuk memasukkan informasi servlet ini ke file deployment descriptor diaktifkan, kemudian klik finish.

Modifikasi servlet tersebut menjadi seperti berikut.
Di class ini kita memiliki satu class variable bertipe CalculatorSessionLocal dan memberinya annotation @EJB yang berarti application server akan meng-inject object tersebut secara otomatis ke dalam servlet kita. Konsep ini disebut dengan dependency injection. Selanjutnya, kita mengambil parameter-parameter yang dikirim melalui http request, kemudian menggunakan session bean untuk melakukan perhitungan berdasarkan parameter-parameter tersebut. Hasil perhitungan kita masukkan sebagai attribut di object request. Untuk menampilkannya, kita akan memforward request menuju ke halaman JSP CalculatorPage.jsp (kita buat sesaat lagi) menggunakan RequestDispatcher.

[sourcecode language='java']
package suhearie.blog.enterprise.servlet;

import java.io.*;

import javax.ejb.EJB;
import javax.servlet.*;
import javax.servlet.http.*;
import suhearie.blog.enterprise.ejb.CalculatorSessionLocal;

/**
*
* @author sarianto
*/
public class CalculatorServlet extends HttpServlet {

/**
* Processes requests for both HTTP GET and POST methods.
* @param request servlet request
* @param response servlet response
*/
@EJB
CalculatorSessionLocal calculatorSession;
protected void processRequest(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
String operation = request.getParameter("operation");
int oper1 = Integer.parseInt(request.getParameter("oper1"));
int oper2 = Integer.parseInt(request.getParameter("oper2"));

int result = calculatorSession.calculate(CalculatorSessionLocal.OPERATION.valueOf(operation), oper1, oper2);
request.setAttribute("result", result);
request.getRequestDispatcher("/CalculatorPage.jsp").forward(request, response);
}

//
/**
* Handles the HTTP GET method.
* @param request servlet request
* @param response servlet response
*/
protected void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
processRequest(request, response);
}

/**
* Handles the HTTP POST method.
* @param request servlet request
* @param response servlet response
*/
protected void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
processRequest(request, response);
}
}
[/sourcecode]

File CalculatorPage.jsp, kita gunakan untuk menampilkan hasil perhitungan.

[sourcecode language='html']

Java EE Calculator Result:

Operation: <%=request.getParameter("operation")%>
Operand 1: <%=request.getParameter("oper1")%>
Operand 2: <%=request.getParameter("oper2")%>
Result: <%= request.getAttribute("result")%>
BACK


[/sourcecode]

Setelah selesai semua, pindah ke tab Services, buka tree Servers, klik kanan di Glassfish, pilih Start untuk menjalankan Glassfish application server. Setelah glassfish berjalan, kembali ke tab Projects, klik kanan di TestEnterpriseProject, pilih Undeploy and Deploy. Setelah proses undeploy dan deploy selesai, buka web browser anda dan masukkan alamat http://localhost:8080/TestEnterpriseProject-war, dan Anda akan melihat halaman seperti berikut:

Masukkan parameter, kemudian klik tombol Calculate, maka hasilnya akan ditampilkan:

Na configuração do Glassfish eu precisei criar o Realm de Segurança (e um sun-web.xml que vai no war para mapear os roles), os DataSources para conexão com o MySQL e configurar o JMS. A vantagem que ele já tem um servidor JMS integrado e quando eu utilizava o Tomcat dependia do ActiveMQ rodando em separado, mais uma razão para eu mudar para um servidor de aplicação.

Daí parti para integrar o Glassfish com o Eclipse, mas o plugin do Glassfish não estava funcionando. Resolvi testar o Netbeans que tem uma ótima integração com o Glassfish (é tudo da Sun :) ). Só precisei instalar os plugins do Maven (dentro dele tem uma opção de instalar plugins) e importar meus projetos foi extremamente fácil.

Agora para fazer o deploy do meu projeto Maven no Glassfish eu não consegui de um jeito bom, estou fazendo pela linha de comando mesmo usando o comando asadmin (criei um shell script pra isso). O Glassfish eu rodo por dentro do Netbeans, perto de onde tem a estrutura do projeto tem uma aba Serviços. Ali tem Servidores e dentro o Glassfish, só clicar com o botão direito e mandar rodar ou parar.

Meu ear ficou com 2 wars dentro e com todos os jars comuns aos dois wars. Cada war tem somente os jars específicos utilizados somente neles. Depois de alguns problemas com classloaders consegui fazer a minha aplicação funcionar. Tive que colocar a opção class-loader delegate="false" nos meus arquivos sun-web.xml e tomar cuidado para que cada dependência que fosse procurada ou estivesse no mesmo classloader ou no classloader pai. Para saber mais sobre a "hierarquia" de classloaders é só dar uma olhada na documentação do Glassfish.

Fica aqui o relato que talvez ajude alguém, não entrei em muitos detalhes para não ficar muito extenso. Me surpreendi com a qualidade do Glassfish e do Netbeans que não via fazia muito tempo. E pensar que eu odiava servidor da Sun (iPlanet argh!!).

Originally I was running lighttpd and I was thinking this might be a bug in lighttpd, so I eventually switched to apache.  Once I was running apache I got a much more verbose error - instead of just a plan 500 or 502 status code I got a message.  I googled that error message plus glassfish and found the solution.

I thought I'd share it here so that future searchers who are using lighttpd or apache will have more places to find the answer.

To fix the issue, add:

SetEnv force-proxy-request-1.0 1

SetEnv proxy-nokeepalive 1

To your apache httpd.conf.  I don't know what the equivalent fix for lighttpd is, if there is any.

From this fix, it appears that glassfish is misbehaving in some way in relation to being behind a proxy, but I don't what way that is and I'm just glad I fixed this mysterious problem!

If any of you readers have more information about this issue, please comment!

Sei que a maior parte do tão falado SOA não passam de um hype, sendo que tudo que existe hoje neste sentido parece muito mais com uma coleção de design patterns catalogados especificamente para organizar as aplicações de modo a minimizar os impactos de integrações com sistemas Back-End, mas de qualquer maneira, as possibilidades de utilizar-se deste paradigma em Java são bastante interessantes, e é a respeito desta experiência que tivémos na última semana é que irei tentar reportar.

Como já falei, o projeto em questão receberá quase que 100% de suas informações a partir de dados provenientes de sistemas Back-End do cliente, utilizando-se maneiras e protocolos diversos. Dado o cenário, observamos a necessidade de separar os processos de integração do sistema de sua semântica, de seu objetivo. Neste sentido, as perspectivas ofertados pelo paradigma SOA parecem surgir com certa precisão para alcançar esta meta. Como em Java sempre existe a liberdade de escolha, que nos permite alcançar o mesmo objetivo utilizando-se diversos frameworks e produtos, existem diversas alternativas para implementar aplicações que utilizam o paradigma SOA. O importante nesta situação é optar por alternativas que seguem alguma API ou especificação JSR. isto lhe trará seguranças em diversos aspectos, principalmente ao vender (ou tentar vender) seu produto.

As APIs em Java que trarão o paradigma SOA à sua aplicação, fazem parte da JSR 208 - JBI (Java Business Integration). As características completas da especificação podem ser encontradas aqui, mas em essência diria que API foi construída no modelo de Web Services, integrando os consumidores e provedores de informações através de componentes plugáveis, chamados de Service Units (SU). Estes componentes plugáveis são divididos em duas categorias (se é que posso dizer assim):

• Binding Components (BC): São os componentes que representam os meios de acesso ou consumo da informação necessária, ou do seu próprio processo. Dentre os BCs existentes, teríamos por exemplo: SOAP, HTTP, FILE, Message Queue, CICS e etc, implementando portanto, como consumir ou disponibilizar determinada informação.
• Service Engines (SE):  São componentes que fazem parte do seu processo de integração e realizam tarefas específicas. Poderíamos ter por exemplo, service engines que executam tranformações de strings XML, acessam bases de dados, objetos EJB ou outros web services.

Os processos de integração que utilizam BCs e SEs em ambiente JBI são realizados de diversas formas, dentre elas processos BPEL, onde podemos harmonizar todas as condições nas quais as interações entre nossos componentes devem acontecer, em qual tempo e em qual ordem. A composição dos diversos SUs, dá origem a uma aplicação composta, chamada de Service Assembly (SA).

O interessante nisto tudo é ressaltar que o JBI define as formas (dentre muitas outras coisas) nas quais os componentes BC e SE devem ser construídos, quais interfaces devem implementar e quais arquivos xml devem ser providos.Isto facilita e muito a adição de novos Service Units, tornando a adição de novas tecnologias como CEP por exemplo, muito facilitada. Um viva aos padrões!!!

Durante a avaliação dos JBI Servers gratuitos que implementem JBI e que possuísem fonte aberto, os produtos que comparei por um tempo foram esses (não tive muito tempo, mas acho que o que pude ver foi bastante satisfatório):

Apache ServiceMix - Esta é a implementação JBI da Apache Software Foundation. Apesar de parecer bastante simples ao fazer download, minha impressão a respeito do ServiceMix é que ele não serve muito bem para iniciantes. Faz-se necessário um conhecimento bastante grande a respeito de suas especificações, das estruturas de diretórios necessárias, dos arquivos xml de configuração e por aí vai... Não consegui encontrar nenhum plugin para o eclipse que realmente tenham valido a pena, ou que me poupassem ao menos metado do trabalho necessário para publicar uma aplicação "Hello World". Um problema grande (e bota grande nisso) é o fato de os tutorias publicados no site da Apache conterem diversos (e absurdos) erros, o que dificulta e muito seu aprendizado. Uma das coisas bacanas é a disponibilização de diversos builds Maven para empacotamento dos deploys.

Mule - Apesar de bastante utilizado e comentado, não implementa especificação nenhuma, portanto não pude olhar este cara muito a fundo. Segundo os artigos e tutorias que li, é bastante rápido, fáicl de gerenciar e de se usar. Como não segue nenhuma especificação, cuidado se escolhê-lo, você pode morrer abraçado a ele.

Open ESB - É de longe o mais fácil de se utilizar e um dos mais completos em termos de Binding Components disponíveis após download. Antigo See Beyond, hoje é a base da distribuição Java CAPS da SUN.  Seu uso através do editor CASA NetBeans é muito intuitivo e apresenta resultados muito de maneira muito rápida. Além do que, os tutorias disponíveis no site da comunidade NetBeans estão muito bem escritos e realmente funcionam. Possui integração facilitada com servidores GlassFish e JBOSS, o que o torna uma excelente opção tanto para aprendizado como para ambiente produtivo.

É isot, neste post procurei descrever de maneira um pouco abstrata talvez, como a plataforma Java soluciona os paradigmas SOA através de suas especificações e APIs, além de apresentar algumas opções de ESBs disponpiveis. Nos próximos POSTS, colocarei alguns exemplos interessantes de aplicações que não consegui encontrar na internet e tivemos que descobrir na marra. Também vou escrever a respeito de CEP, que parece ser algo bastante promissor daqui pra frente!

NetBeans

NetBeans 6.1 provides out-of-the box integration as it is bundled with GlassFish.

Just keep the default setting "GlassFish V2 UR2" enabled during installation process.

In this way GlassFish is automatically installed, configured and ready-to-use: simply press "Run" on any web project!

However, if you would like to declare another installation of GlassFish go to Tools → Servers → Add Server...

Select the proper version, specify the name and click "Next.

Provide the installation path of GlassFish through the "Browse" button and click "Next" to configure the password or "Finish" to complete.

That's it!

Let's create a simple web application to test it. Go to File → New Project... → Web → Web Application → Next → Specify the Project Name → Finish

The project should appear on the Projects tab. Edit the code of index.jsp and change <h2>Hello World!</h2> to <h2>Hello World from GlassFish!</h2>

Now simply right-click on the project and select "Run"!

Eclipse

If you are behind a proxy make sure you have properly configured the network settings for HTTPs also. Window → Preferences → General → Network Connections and make sure the option "Use this proxy server for SSL" is checked → Apply → OK → restart Eclipse.

Open the Servers view: Window → Show View → Other... → Server → Servers

On the Servers tab right-click → New → Server

Click on the "Download additional server adapters" link.

Click on the GlassFish Java EE Server option and press "Next".

Afte reading and accepting the CDDL licence press "Finish" and OK at the prompt message. After a while Eclipse will restart.

Now go the Servers tab right-click → New → Server and select "GlassFish".

Note: The plugin for brand new GlassFish v3 Technology Preview 2 is already available!

Select the version of GlassFish you have installed and press "Next".

Provide the installation directory of GlassFish and click "Next".

That's it!

JDeveloper

JDeveloper has a really handy feature: deploy-on-demand.

Let's assume we want to deploy a web application. In the Application Navigator right-click on the project → New... → General → Deployment Profiles

Select war and click "Next".

After specifying the name, for example "wicket", provide the hot-deploy directory of GlassFish through the "Browse" button.

That's it!

To deploy the application simply right-click on the project → Deploy → wicket → to WAR file.

Para habilitar no Glassfish (versão v2) a integração com o Apache, temos que copiar os jars commons-modeler, commons-logging e tomcat-ajp de uma instalação existente do Tomcat (importante: não pode ser a última versão do Tomcat que não funciona, eu usei a 5.5.17) para o diretório $GLASSFISH_HOME/lib. No meu caso comecei a ter problemas com o log4j e tive que tirá-lo do pacote da minha aplicação e colocá-lo no diretório lib também para o servidor inicializar sem erro. Só que minha aplicação parou de mostrar os logs do log4j, isso ainda é um problema que tenho que contornar.

Após ter copiado os jars, ainda temos que definir uma propriedade na inicialização do Glassfish que definirá a porta utilizada pelo mod_jk do Apache para se comunicar com o Glassfish:

-Dcom.sun.enterprise.web.connector.enableJK=8009

Isso pode ser feito pela interface de administração (por exemplo, http://localhost:4848) ou usando o comando:

$GLASSFISH_HOME/bin/asadmin create-jvm-options -Dcom.sun.enterprise.web.connector.enableJK=8009

Não vou explicar a parte do Apache que utilizaria o mod_jk, é só procurar no Google como faz a integração Tomcat com Apache que é igual.

Se alguém quiser mais detalhes, ver em essa página em inglês: Running GlassFish with Apache httpd