Hello, I am working on my first struts application, and I was wondering about design patterns for communicating between actions. For example, I have actions A and B. A runs first and creates some data (e.g., a session bean). When B runs, it needs to verify that the data is actually available. This may be necessary both for security (if action A is a login action), and for correctness. In my case, it's just about correctness.
Before using struts, I'd implement this by saving the data in the session. With struts, I have few more options: 1) Implement the actions as SessionAware actions, and use the session to communicate. 2) Use global results from action A. I've read a little bit about it and I am not sure how it works. I'd appreciate if someone could post a link to a good article about global results. 3) Action chaining. This may not be feasible, because sometimes I want just action B to run. 4) ??? anything else that I am missing? Right now I am using the first option, but I don't know if that is the correct way to go. I'd appreciate any hely. Thanks, Jonathan
