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 ]
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.