JBoss vs Spring

[Rod Johnson]

I think it was from someone asking, "Should I use JBoss, or should I use Spring?", and someone else responding, "Spring".

I think the original question asked about some specific features, and Ben was responding based on that. Spring is designed to work in any application server (or outside an application server); using Spring does not mean ignoring what the server may have to offer. It just provides greater choice in a lot of cases.

It comes down to distinguishing between EJB and J2EE--which I, at least, have always been careful to do.

[Martin Kersten]

It comes down to distinguishing between EJB and J2EE--which I, at least, have always been careful to do.

I guess you wrote a whole book about it, arn't you?

[stateofmind]

Rod Johnson: It comes down to distinguishing between EJB and J2EE--which I, at least, have always been careful to do.

Is this the same Rod Johnson of "J2EE without EJB" :?: From what I've read it's a great book. But I'm a little lost right now, I need a better into to J2EE before I can grasp it all.

Do you know of any web references that give you a overview of J2EE and maybe some examlpes?

Josh

[robh]

Yes it is. Spring came about from the framework discussed in the book. If you have never read it I definitely recommend that you do. You should probably read both Expert One-on-One J2EE books by Rod in the order in which they were printed.

Rob

[ani]

Hi All,
I am new to spring.
I would like to know more about how can I integrate Spring with JBoss?

thanks
Ani

[Rod Johnson]

Spring integrates well with JBoss or any J2EE application server through the J2EE APIs. Many users use JBoss and Spring happily together. Spring's functionality does not conflict with that offered by the underlying platform, whether it's an application server or (in simpler cases) a web container such as Tomcat.

[ani]

Hi Rod,
Thanks for your reply.

Let me explain what we are planning to do.
We are developing a J2EE application with following requirement.

1. Workflow based .. so that developer can easily define its workflow in plain xml
2.Schedular.. Lots background jobs are required on server.
3.SEDA based architecture...
4.ESB
5.Distributed .. So that we can have services running on differnet machine
6.Persistence

Here I need suggetion should we go with EJB (or + ) Spring.

Can I get any document on integration of Spring with JBOSS.

thanks
ani.......

[jbetancourt]

Since you need ESB, why not just go with an ESB?

Mule, ServiceMix, etc. I'm not sure if JBoss has completed its ESB slant. (Yes, I'm aware of ESB being more or less then an actual 'product'). ServiceMix has a lot of support for Spring. Mule is already SEDA based.