I have an ordering application that will use stateful session beans to do
the business logic. It can store session state in those stateful session
beans. What implications does this have on the way state is handled in the
upstream Struts app?
 
In short, the Actions will be calling various Stateful Session Beans to do
the actual work.  These are used for various reasons with the main one being
their built-in transaction support (online orders...need to be either
done...or not done). How should state be handled and at what level
(page...request...session...) in the upstream struts portion? 
 
Thanks!

Reply via email to