Problem t:datascroller does not work in shale dialog

• Key: SHALE-341
• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Priority: Major
• Assignee: Unassigned
• Reporter: mario buonopane
• Affects Version/s: 1.0.4-SNAPSHOT
• Fix Version/s: 1.0.4

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).

 

Comments

[mario buonopane]

This is a simple application that reproduce the problem.
if you run the dataScroller.jsp page directly (http://xxxx/Datascroller/dataScroller.faces) the t:datascroller works fine.

If you run dataScroller.jsp in a Shale Dialog does NOT work fine. To test this case run the url http://xxxx/Datascroller/ and then click the "Start" button.

[Craig McClanahan]

Revised version of the example application that includes the Shale JARs that will be in the 20061201 nightly build. With these jars, the data scroller works as expected inside a dialog.

[Craig McClanahan]

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.