aspose file tools*
The moose likes EJB and other Java EE Technologies and the fly likes Seam vs EJB3 question on a specific usecase. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Soft Skills this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Seam vs EJB3 question on a specific usecase." Watch "Seam vs EJB3 question on a specific usecase." New topic
Author

Seam vs EJB3 question on a specific usecase.

Dinesh K J
Greenhorn

Joined: Mar 19, 2008
Posts: 3
I have an application which will involve a JSF front end and will send requests to a MQ (Most likely JBoss messaging). And a business layer which will read the messages and apply business logic and store it in Database.

The UI layer will be on a separate Tomcat and Business layer on JBoss. The business layer needs to be scalable, i.e. by adding extra servers we need to handle extra load, the order in which messages are processed is not important.

Few questions here

1. Seam framework or Plain EJB3 for the above case? Where will I code my Business logic in the case of Seam ?
2. Is it a good practice to send Messages to MQ directly from Tomcat (ie from the webapp) ?


Thanks in Advance for your replies.
Dinesh.


-----
SCJP 5.0
SCWCD 5.0
Jayr Motta
Ranch Hand

Joined: Jul 30, 2010
Posts: 110

Dinesh,

1. Seam framework or Plain EJB3 for the above case? Where will I code my Business logic in the case of Seam ?


I don't really know Seam, however I know EJB3 and I'm pretty sure that you'll be able to cope with the same load as with any other implementation / framework. In most cases the bottleneck aren't in the business layer if you design the software well, in any technology, it usually happens on the database, once both work with relational database and there is no such thing as partitioning of relational database (at the most you'll get a mirror / backup .. but's not the same as partitioned databases).

2. Is it a good practice to send Messages to MQ directly from Tomcat (ie from the webapp) ?


I don't think it's wrong to send messages from your controller layer, but there are some implications on it. An example is if you want to send the message just if all other operations in the method your have been executed without errors, you'll have to check it or control transactions manually.

I think the major benefit by doing this kind of operation in the business layers is the amount of implicit services you earn. Declarative security, declarative transactions, less maintainance points, etc.

Hope it helps!


Feel free to ask me anything!
www.BlackBeltFactory.com/ui#!/ref=jmotta, SCJP 6, OCWCD JEE5, OCE EJB JEE6
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Seam vs EJB3 question on a specific usecase.