>From: "Sean Schofield" <[EMAIL PROTECTED]> > > No I'm not proposing we deal with generating HTML rendering business > as far as dialogs are concerned. [I'll post a more detailed > explanation on the shale dev list where that belongs.] >
This might not be a bad idea. The struts synchronization token is wired to the html:form and html:link jsp tags. They propagates forward a token that represents a context. A unique token could be used to identify simultaneous dialogs per session. We could inject this token using the same method that we add javascript to the commands onclick event for commons validator. This doesn't work with components that hijack the response writer for more than their own renderering. Tomahawk as one of these kind of components and I wouldn't doubt if Trinidad does too. Gary > @Adam: If you're not already subscribed to shale dev we'd love to have > you over there. Specifically, we could benefit from your insight > regarding dialogs. > > @Everyone Else: This goes for you too. If you're using JSF you'll > want to check out Shale which just builds on JSF and provides a lot of > cool stuff missing from the spec. > > Sean > > On 8/24/06, Gary VanMatre wrote: > > > > > > >From: "Adam Winer" > > > > >Wrong list, sure, but since you opened up the can of worms... > > > > > >Is Shale really planning on getting into the HTML-rendering > > >business? > > > > > > > > > What do you mean by "HTML-rendering business"? > > > > We have custom components that do rendering. Clay has been around better > > than a year now and provides rich view composition using various templating > > options. Clay is a component in of itself that simple builds a subtree of > > components using a mechanism other than JSP tags. The clay component > > renders it children. When using full html (tapestry like) views or full xml > > (tiles like) views, the clay component is the only child under the view > > root > > so it pretty much renderers the full page. > > > > > > > > > > >-- Adam > > > > > > > > > Gary
