aspose file tools*
The moose likes JBoss/WildFly and the fly likes JBoss & Spring Frame Work Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "JBoss & Spring Frame Work" Watch "JBoss & Spring Frame Work" New topic
Author

JBoss & Spring Frame Work

DINESH MISHRA
Greenhorn

Joined: Jan 07, 2001
Posts: 6
Hi,

What is the scope of the applications build up on Spring Frame Work and JBoss?
Thanks & Regards
Dinesh Mishra
Dave Salter
Ranch Hand

Joined: Jul 20, 2005
Posts: 293

I'm not entirely sure what you mean, but....

You can develop and deploy Spring applications onto JBoss instead of Tomcat (JBoss uses Tomcat internally for JSP/Servlets).

Sometimes I prefer to use JBoss instead of Tomcat for Spring development because of a few extra features it gives me.
S Davis
Author
Ranch Hand

Joined: Feb 07, 2006
Posts: 40
There is nothing stopping you from deploying Spring in JBoss, although it's a bit like driving your Ford to your job at Toyota... (grin)

JBoss uses the J2EE specs to provide transactions (Stateless Session Beans). Spring is an alternate technology that is functionally equivalent but doesn't adhere to the J2EE spec.

See http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossSpringIntegration for details on integrating the two, or perhaps consider Geronimo as an alternate -- it provides native Spring support.

I'm a big fan of Spring -- the dependency injection is something I'm using at my day job on a command-line interface (?!)
Tom Marrs
Author
Ranch Hand

Joined: Sep 20, 2000
Posts: 67
Like Scott said, it's like driving a Ford to your job at Toyota. <grin/>

If you're using Spring properly (for Transactions, Hibernate integration, and so on), you could easily deploy your application on Tomcat. Spring does transactions, so you don't need Stateless Session Beans anymore. The Hibernate integration is fabulous.

If you need JMS messaging, you could use ActiveMQ. Jencks (a related project) allows you to add Message-Driven POJOs to your Spring environment, so you don't need MDBs anymore, either. Again, you could put this on Tomcat.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: JBoss & Spring Frame Work