> I'm using an action to retrieve a list of entities and render these as a
> list, the user can then select an edit button that calls an action that
> retrieves the individual entity and renders the edit page. Once the user
has
> completed editing they hit the save button which calls the action th
2016-01-04 20:52 GMT+01:00 Xu, Hui@DCSS :
> Question modified:
> We are planning to migrate our application written in Struts 1 to Struts 2.
> We want to have Struts 1 and Struts 2 coexist as we migrate our application.
> We have a few pages that need to share state. Currently this is implemented
I'm using an action to retrieve a list of entities and render these as a
list, the user can then select an edit button that calls an action that
retrieves the individual entity and renders the edit page. Once the user has
completed editing they hit the save button which calls the action that calls
Im facing the same issue, has anybody arrived at a solution or found a
way to resolve this issue ???
-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
Question modified:
We are planning to migrate our application written in Struts 1 to Struts 2. We
want to have Struts 1 and Struts 2 coexist as we migrate our application. We
have a few pages that need to share state. Currently this is implemented in
Struts 1 by defining a conversation.
1.
We are planning to migrate our application written in Struts 1 to Struts 2. We
want to have Struts 1 and Struts 2 coexist as we migrate our application. We
have a few pages that need to share state. Currently this is implemented in
Struts 1 by defining a conversation. How do we implement this in
6 matches
Mail list logo
