Win a copy of Cross-Platform Desktop Applications: Using Node, Electron, and NW.js this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Architecturally correct and the best way to access EJB from a JSP client(urgent!!)  RSS feed

 
Sameer Gpt
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi there
Can you please tell me that which is the architecturally correct and the best way to access EJB from a JSP client??? If possible explain it in detail
many thanxx
Sameer
 
Karthik Guru
Ranch Hand
Posts: 1209
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have used Struts so i can tell you that.
Browser
| ^
| | (Action servlet decides the next JSP)
V |
Action Servlet (Master Servlet) (Decide which action to execute based on request)
| ^
| |
V |
Action Class
| ^
| | (Populates request with data)
V |
(process the ActionForm that has come in for request parameters)
| ^
| |
V |
Business Delegate ( U can have several UI Layers here)
| ^
| |
V |

Stateless Session Bean (Server Layer starts here)
| ^
| |(Value objects that has data)
V |
Command objects (look up command and then execute)
| ^
| |
V |
Entity beans
 
Frank Carver
Sheriff
Posts: 6920
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm a bit puzzled by this. I don't think there is a single best way of doing anything like this. An architecture is only correct or incorrect in the context of a particular solution to a particular problem.
Can you tell us more about the problem you are trying to solve, or the goals of the system you are trying to design ?
 
Tim Holloway
Bartender
Posts: 18662
71
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In software, about the only word that gives me more heartburn that "The" is "Best". The Perl people have it right (motto: "There's more than one way to do it"). "Efficient" comes in as a close third.
Anyone who's done any serious study in algorithms should know that there are times when a Shell Sort can beat the stuffing out of a "QuickSort". And times when it can't even come close.
Similarly, while I can't fault such a nice complex roadmap using Struts - especially since I have Struts/EJB magazine article due to be published come November, that doesn't mean that I'd use it where the complexity and overhead were more of a liability than an asset.
I also don't happen to believe that all the design patterns that were ever needed were created when the Universe first came into existence.
 
Nadine McKenzie
Ranch Hand
Posts: 53
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Core J2EE Design Patterns book has excellent suggestions on what would be "architecturally correct". For example, on the "front-end" a service to worker works very nicely. You might choose a business delegate to tie the "front-end" to the EJB layer.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!