[ http://issues.apache.org/struts/browse/SHALE-341?page=all ]
Craig McClanahan resolved SHALE-341.
------------------------------------
Fix Version/s: 1.0.4-SNAPSHOT
Resolution: Fixed
Gary's comment about BasicDialogContext.outcome(), on the user mailing list,
was spot on. When the incoming outcome was null, we were staying in the same
state (as expected), but we were mistakenly recreating the JSF view (with the
same view id). This would cause the loss of any data that the components had
stored in the component tree, which happens to include where <t:dataScroller>
maintains its state information.
The fixed code will be in the 20061201 version of the nightly build. Mario,
you'll note that Shale has gone through a pretty major refactoring since the
20060831 code you are working with, and the various pieces of functionality
have been separated into separate JAR files. That way, you only need to
include the pieces of Shale that you need for a particular app. Check the
documentation on the website <http://shale.apache.org/> for more on how to
configure each of the elements.
> Problem t:datascroller does not work in shale dialog
> ----------------------------------------------------
>
> Key: SHALE-341
> URL: http://issues.apache.org/struts/browse/SHALE-341
> Project: Shale
> Issue Type: Bug
> Affects Versions: 1.0.4-SNAPSHOT
> Environment: windows tomcat/websphere
> Reporter: mario buonopane
> Fix For: 1.0.4-SNAPSHOT
>
> Attachments: Datascroller.war, Datascroller2.war
>
>
> 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).
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
