| Key: |
SHALE-341
|
| Type: |
Bug
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
mario buonopane
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
|
|
Environment:
|
windows tomcat/websphere
|
|
|
I have a simple page with a t:dataTable and a t:datascroller. The datascroller does work correctly if the page is not part of a Shale Dialog. If I put this page in a Shale dialog, the datascroller does NOT work correctly (does not change page and always shows the first page).
|
|
Description
|
I have a simple page with a t:dataTable and a t:datascroller. The datascroller does work correctly if the page is not part of a Shale Dialog. If I put this page in a Shale dialog, the datascroller does NOT work correctly (does not change page and always shows the first page).
|
Show » |
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#481140 |
Fri Dec 01 03:56:17 UTC 2006 |
craigmcc |
When BasicDialogContext.advance() was called with a null outcome, we were
correctly staying in the same state (to emulate JSF standard navigation
behavior), but we were *incorrectly* recreating the view. This would destroy
any accumulated information in the component tree and cause it to be
reinitialized, which was the proximate cause for this particular sample app
failing.
Change things so that a null outcome causes us to stay in the same state
*without* recreating the view. Thanks to Mario Buonopane for the concise
reproducible test case, and to Gary for pointing right at the problem area.
SHALE-341
|
| Files Changed |
MODIFY
/shale/framework/trunk/shale-dialog-basic/src/main/java/org/apache/shale/dialog/basic/BasicDialogContext.java
|
|
Problem t:datascroller does not work in shale dialog
