Hi, All:

 

I am currently on a fledgling project that requires the following technologies:

 

Business Object Pooling (Scalability)

Database Connection Pooling

JTA/Transaction Manager

JMS

Web Services

 

Currently, the group is trying to avoid using an app server all together and glue all these open source technologies using Spring.  My argument is that if we need all these aforementioned technologies, we should go with an Application Server (JBoss :-)) and get these services "out of the box".

 

The group is having a very hard time attempting to glue all these pieces together, including making use of JBI (ServiceMix/Jencks/ActiveMQ).  My position is that we should use Stateless Session EJBs for now (they would be much quicker to implement than all these independent technologies they are trying to glue together), with Hibernate-based DAOs on the backend, Web Services for SOA and wait until JBI matures.

 

We have a business deadline and are falling very far behind.  I think we may be "over-architecting" what appears to be a traditional reservation system.

 

My questions are:

 

1) How does JBoss foresee the use of Spring and "Lightweight Containers" in the future?  Is my thinking sound that we should stick with JBoss or will JBoss be rendered "obsolete" by Spring and JBI?

 

2) How will JBoss interact with Spring?  What is the preferred way of it being used with JBoss?

 

3) What is JBoss future plans for JBI (our particular flavor is ServiceMix)?  Should we wait until the technology matures and gains industry-wide acceptance and app servers incorporate this technology, especially with our risk-averse project requirement due to tight deadlines?

 

Thanks for your help.

 

Sincerely,

John Curley

 

 

 

This electronic message transmission contains information from the Company that may be proprietary, confidential and/or privileged.
The information is intended only for the use of the individual(s) or entity named above.  If you are not the intended recipient, be
aware that any disclosure, copying or distribution or use of the contents of this information is prohibited.  If you have received
this electronic transmission in error, please notify the sender immediately by replying to the address listed in the "From:" field.

Reply via email to