This week's book giveaway is in the Other Open Source APIs forum. We're giving away four copies of Storm Applied and have Sean Allen, Peter Pathirana & Matthew Jankowski on-line! See this thread for details.
SCEA part 2 task requires "Your architecture and design will be graded on how well it supports both web clients and application clients". There is no problem in suporting web clients. Will it be correct if in my architecture I publish the webservices corresponding to my EJB interfaces to enable support for application clients?
Why do you use EJB endpoint web service? In general, the EJB web service is a stateless web service. Then your web client and application client will maintain their own states in their session (that will have duplicated codes in both).
Joined: Mar 09, 2005
Thank you very much for reply.
Are you saying that it is better to use POJO end point and store the state there? I dont think that using Stateful bean to store state will be better. Stateful bean for each client will be taking a lot of resources.
Originally posted by Vlad Eroshin: ... application clients". ... Will it be correct if in my architecture I publish the webservices corresponding to my EJB interfaces to enable support for application clients?
When you will be asked in part III how an agent's Swing client is to access your webservices, what will you answer?