I have an existing web application that was written in servlet/jsp. I want to inject
EJB tech to rewrite it. The application is a database query and display type. No transaction or database update involved. Here are my questions ---
1. Since there is no transaction or database update involved, should I think using EJB is a overkilling ?
2. Somehow I feel I can use session bean for the following purposes: I have lot of calculation and logic stuff, this can be done by stateless session bean; I have some Action classes that basically do the database query and return some data structure for front end display, I can use session bean to replace these Action classes. Are these 2 ideas correct ?
3. Assuming I can use session beans to replace the Action classes, I am not sure if stateful or stateless bean is better. The application consists of several pages. user picks some criteria on 1st page and the 2nd page is displayed based on 1st page's search results, and then user picks search criteria on 2nd page, so the 3rd page is displayed based on previous page's choices... So I have a Action1.java, Action2.java, etc corresponding to Page1, Page2's search work. It seems I can convert them into stateless session beans because everytime I just do a search by giving some search criteria, that's it, I get the search results and display it. Does this make sense ?