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

------------------------------------------------------------------------------
  How about a Tapestry Context? I've built one for our projects, it sets the 
Visit into ThreadLocal. This way, helper classes don't have to pass around the 
Visit. The extended BasePage implements IPageListener and sets (and unsets) the 
Visit. Classes that control web flow can grab it themselves. You could also put 
HttpRequest in it for implementing Portal support (this was mentioned in HLS's 
post as problematic). Probably all of a 30 minute job.
  
  A supported tag in the html, jwcid="[EMAIL PROTECTED]" would be nice. We put 
all component definitions in our .page files (as everyone should) to separate 
HTML development from Java development. However, we typically need at least a 
couple of copies of links etc., and having such a tag would be much cleaner 
than all the alias components that blindly make more ids with a number tacked 
on the end!
+ {{{much needed. the restriction of not being able to reuse component 
instances encourages people to define components in the html - ps}}}
  
   * Make Tapestry pages somehow "compileable", adding support for this for ANT 
and so on. I'm going to make Ognl 3.0 generate java code (Dmitriy Kiriy, 
KiriyDmitriy at yandex.ru)
   * 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. 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to