Seam or not to seam

Posted in java by pedro | Friday, February 16th, 2007 at 1:24 pm

Today is a titan worker day. Karwer and I have killed nearly all tasks in 1.9.2.

For long time I waited for Seam exploration. I read Jacek fights with seam and application servers. He provides simple seam 5 minutes tutorial startup.

1. Get JEMS Installer 1.2.0.GA.
2. Get JBoss Seam 1.1.6.GA.
3. Install JBoss AS 4.0.5.GA with EJB 3.0

java -jar ./jems-installer-1.2.0.GA.jar -installGroup ejb3 installpath=

4. Unzip seam.
5. Run seam setup
6. create project seam


7. Run JBoss AS and you’re done.

After that you have:

* project structure with ant build.xml
* EJB 3.0
* TestNG with JBoss Embeddable EJB3
* JSF template
* Database (HSQL) integration
* You have simple login form (which works)

Directory structure, I’m disappointed, because it’s no maven like. You have netbeans project, if you use eclipse or idea you have got a problem. It’s ant, so you have 32M lib directory.

I think than seam wants to show that he can generate more than RoR (by the way, django way ;) ).

So seam guys suggested use netbeans, no problem. Downloaded, installed and … everything is fine. Netbeans is better and better. Maybe it’s time to look closer on it. We’ll see. I going back to seam.

Technorati Tags: ,

Leave a Reply

about me

My name is Sebastian Pietrowski. I've finished Warsaw University as Master degree. I started my journey with Java 1.1 with Thread and JDBC programing in 1998 as I worked for merlin.pl. In 1999 I've passed Java Programer Certificate for Java 1.2, and was solution architect of merlin.pl infrastructure when we was moving from pl/sql to J2EE. It was great performance optimization with 10 times more req/sec than in requirements and 85 times faster as original solution.

Currently I work as Expert Software Development Java at F.Hoffmann-La Roche. The company was founded in 1896 and today, Roche employs over 80.000 people. After work I'm involved in activities related to Scala/Lift, Ruby/Rails/Merb, Python/Django. This is because I try to be pragmatic also I'm focused on application performance and tuning with success in my daily work.

My Yoda's motto: Do, or do not. There is no try.