File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Hibernate/Spring/ Struts vs. EJB 3.0 on JBOSS

 
Arthur Orange
Ranch Hand
Posts: 30
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am excited about the prospect of using EJB 3.0 on JBOSS.

I have some questions however.
1) Is it possible to use Spring/Struts and Hibernate on JBoss?
2) Is it possible to use EJB3.0 and elements of Spring on JBoss?

My goal is to be able to use the most configurable variations of these (I tried hibernate 3.0 and its PAINFUL to configure it to run with the simplest of dbs) Are any of the aforementioned technologies mutually exclusive?

I know Struts and Spring and Hibernate are viable together (but EJB 2.0 and Spring are not).

Is it worth the effort to try to install JBoss/ learn it and use it if I am NOT going to be touching EJB 3.0? Since I could make struts/spring/hibernate interoperate on a leaner app server like tomcat.

A
 
norman richards
Author
Ranch Hand
Posts: 367
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hibernate and Spring both work great on JBoss. Hibernate is an actual JBoss project, so you can count on it always working well.

I highly recommend looking at EJB3 instead of Spring. Spring is interesting, but EJB3 is so much easier to use.

Certainly you should consider JBoss no matter what you are working on. No matter what you are doing, you need to run inside of a container of some sorts. JBoss is the best container to run in, whether you are doing WEB or EJB or whatever.
 
Kishore Dandu
Ranch Hand
Posts: 1934
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by norman richards:

Certainly you should consider JBoss no matter what you are working on. No matter what you are doing, you need to run inside of a container of some sorts. JBoss is the best container to run in, whether you are doing WEB or EJB or whatever.


Do u folks have concrete numbers about this statement. I agree of its merits on a smaller scale websites. But I haven't seen it used in full fledged high number websites yet. If any one has observations to the contrary please chip in.
 
Kishore Dandu
Ranch Hand
Posts: 1934
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by norman richards:
JBoss is the best container to run in, whether you are doing WEB or EJB or whatever.


I would consider this as evangelism than hard truths. If you like some technology don't extrapolate it. Please just give its relative merits. That will be a cleaner way of promoting it.
 
Sam Griffith
Author
Greenhorn
Posts: 16
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think instead of getting into a discussion of spec numbers, etc, what is really more relavant, is who is using JBoss to do real world things and what are they using it for. Please go to the link that follows to read about some customers using JBoss to do exciting things.

http://www.jboss.org/customers/index
 
Kishore Dandu
Ranch Hand
Posts: 1934
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Sam Griffith:
I think instead of getting into a discussion of spec numbers, etc, what is really more relavant, is who is using JBoss to do real world things and what are they using it for. Please go to the link that follows to read about some customers using JBoss to do exciting things.

http://www.jboss.org/customers/index


It depends on what application inside the organization is using JBoss. It is possible that continental.com is hosted on a crop of weblogic servers and their intranet site(with reasonable hits per day) is hosted on JBoss.
 
Michael Yuan
author
Ranch Hand
Posts: 1427
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In my opinion, Spring is a bit complex (giant XML files) and under-powered (no real app service integration), compared with EJB 3.0. But most importantly, EJB 3.0 absorbed some of the best ideas in Spring (DI and POJO) and standardized them. You can check out a controversial article I published on OnJava on this subject.

POJO Application Frameworks: Spring Vs. EJB 3.0

Disclaimer: I work for JBoss. But the view presented in the article is purely personal.
 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic