File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes EJB and other Java EE Technologies and the fly likes Would it be foolish to only use the EJB container? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Would it be foolish to only use the EJB container?" Watch "Would it be foolish to only use the EJB container?" New topic
Author

Would it be foolish to only use the EJB container?

Steve Buck
Ranch Hand

Joined: Nov 23, 2004
Posts: 45
Would it be foolish to only use the EJB container? Say you want some centralized objects with controlled DB access (the EJB does it all..not client), security, transactions, persistence and remotability available for a rich desktop app (many clients in a network using it). But there was no real use for JSP and/or servlets. Would it be considered "overkill"?

Well... I have considered web services too. Have the web services do all the EJB access. Keep it neutral and then allow any type of client to connect and take advantage of the web service.

Is this is a commonly used design?
[ January 15, 2005: Message edited by: Steve Buck ]
Jeanne Boyarsky
author & internet detective
Marshal

Joined: May 26, 2003
Posts: 30751
    
156

Steve,
It is a valid design to have the EJBs function as remote components called from the fat client. That's essentially what you have with servlets anyway. You are just moving the client from the servlet to the desktop app.


[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Would it be foolish to only use the EJB container?