solution 1. persisting data may cause some problems,
for example performance, as users may need to create a
few detail objects. I prefer to keep these objects in
View and provide a 'Done' button, which will then let
Action to do the persistence.
Another problem is that in my Use Case, the detail
Session scoped forms are one of my favorite things about Struts. Seems
like you have a situation for them.
Make sure you keep all session-scoped form fields Serializable or mark
them as transient if they are not.
Clever implementations of ActionForm.reset can make memory management
easier.
thanks.
i saw some discussion earlier (search for request
against session). It seems that people recommond not
to use session scope forms.
so out of these three, which is my best choice then:
- Struts workflow extension
- hidden field
- session scope form
many thanks !
--- Erik Weber [EMAIL
It depends upon the architecture you want to follow. There are multiple
ways this can be done
1. Create the 2 jsp as independent jsp. Thus the list jsp jsp always
fetches from DB when we bring control to that.
Clicking add on the list jsp leads to the adddetails jsp which submit
data to DB.
4 matches
Mail list logo
