Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tapestry Wiki" for change notification.
The following page has been changed by ErikVullings: http://wiki.apache.org/tapestry/WishList ------------------------------------------------------------------------------ + * Better/easier support for invalidating session commonly needed for log out action. Or at least some method for reinstantiation of visit object and forgetting all pages. + * Add a way to prevent double click similar to Struts token + * Support web flows + * Support web continuations + {{{I don't see this as a feature of Tapestry. + Once 3.1 comes along with Hivemind services you could create a service that + enabled continations by using one of the libraries out there that support this. + Like rife, pico threads, or ATCT (commercial)- Geoff }}} + {{{Are you sure? I guess it isn't possible without a complete support by Tapestry framework}}} + {{{ The cool thing is that once Tapestry is integrated with Hivemind you can add services with all kinds + of interesting functionality, like continuations or Spring-like transaction support. + In fact I believe that the current Tapestry services themselves (like Asset, Action, Page, etc) are + going to become Hivemind services. }}} + * Add runtime exception logging through commons-logging *along* with displaying them on Exception page. Exception page is nice during development, but insufficient for deployment since I cannot go through let's say file logs and see what happened badly yesterday. This additional logging should not be performed inside default exception page class, since user could specify his own exception page and forget to implement logging inside new class. + * Add skinning functionality (add skin string to html search, i.e. file_skin_EN_US.html) * Listener methods that take actual typed parameters rather than having to pull them from service parameters * Cleaner URL's, to really help with ["J2EESecurity"] * Easier testability of Tapestry pages/components + * Fix for security hole in asset service + * Allow simpler validation - for example, bypass invoking listener method and return to same page if validation errors occur + * Better support for hot deploy, allowing new page and component templates/specifications to be picked up at runtime. WebOGNL has a timestamp dependency check, which would be nice to borrow from. + * Let the component user be able to set the template for the component just as easily as set a paramemter. + * For component beans, add a set-static-property type of capability, instead of shoehorning in a string using an expression setter. + * Unified the way to process validation, make all form components support displayName property and be able to support validator. Let the FieldLabel highlight the label automatically when the field is required. + * It would be great if there was a way to carry through form parameters. Say I have pages A and B. B is a general purpose page used to lookup information. It should be possible to navigate from A to B back to A and keep the form parameters of that were set in A. At the moment you would need to make B record the values in hidden fields then submit them back to A or use persistent properties. It would be great to be able to automatically pass these parameters along without making B explicitly aware of A's parameters since B might be used in other contexts. Hope that makes sense. It's hard to explain. + * Allow use of "id" attribute instead of "jwcid", so that templates are truly pure HTML. Perhaps even make the scheme for tagging the binding name flexible. + * The biggest issue I have had (and have seen a lot others have) is with pleasing the rewind cycle. The rewind has to be completely transparent which means we should by default make all form elements serialize their state in hidden fields and allow the user to opt out. Many of these wishes are already being acted upon, see ["Tapestry31"]. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
