Re: Design patterns for communicating between actions

Yoni Amir wrote: 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., You have few opions here, you can you action chaining: http

Re: Design patterns for communicating between actions

tion, 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

Re: Design patterns for communicating between actions

Which version of struts are you using? Yoni Amir wrote: 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

Design patterns for communicating between actions

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