> > > In preparation for the initial milestone release of Struts Shale 1.0.0, a > > release candidate has been made available at: > > > http://people.apache.org/~craigmcc/struts-shale-1.0.0-rc1/> > org/craigmcc/struts-shale-1.0.0-rc1/> > > (TIME LIMITED URL) > > Echoing Niall's congratulations, and because he took care of the > contents of the release, I'll focus on the use-cases app. (Except > that I would also recommend moving the release notes to the top > level.) > > What about moving the 'Log On Dialog' use case to a separate section > with a warning about the back button problem? Otherwise, people are > going to do things like... Log On Dialog -> Back -> Rolodex... and > think that the Rolodex is broken. >
The rolodex example should work now. It needed a navigation rule and to bypass validation. > I added a cancel button to the logon page to give the user a way out > if he doesn't want to log on or create an account. It seems to work, > but you should probably check. :) > > Often when I click a link for the first time, nothing happens. > Clicking again works, but I haven't isolated it. > You are seeing how myfaces handles the browser back. When using server side state saving in myfaces, the component tree is invalidated after the next component tree is built. The first click from a browser back builds the view. Using client side state saving will solve this with myfaces. The RI seems to handle caching differently. If you think about what JSF is doing here... The same problem is handled in Struts by creating two actions, one that stages the data and one that responds to the post. Or, if you like using the single action to a view, you would have to create some parameter passing system, like the LookupDispatchAction to identify if the page was being loaded or posted. JSF handles this to the point that I sometimes forget all the code that I once had to chain together. > Possibly related to the 'nothing happens' problem, I tried adding > target="_new" to the JSP Remoting links. It does open a new window, > but every _other_ time you click, it just displays usecases.faces in > the new window. Close it and click again, and you get a new window > with the (correct) xml response. > > On the validation page, the link back to the main page has > immediate=true, but the JavaScript validation still fires. You can't > get off the page without filling in the expiration date. > > (I changed the current year for the copyright on the Javadocs, and > fixed the title for the test framework.) > > Thanks, > -- > Wendy Gary > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
