Yes, there's no documentation (yet), but what you are trying to do can be accomplished with the tapx/Dynamic component (part of tapx-core).
Alas, you'll need to build it yourself (using Gradle, so it's easy) since I haven't updated the tapestry360 Bamboo for Gradle, so no nightly builds. On Thu, Nov 4, 2010 at 7:28 AM, Michael Gentry <[email protected]>wrote: > On Thu, Nov 4, 2010 at 10:21 AM, Thiago H. de Paula Figueiredo > <[email protected]> wrote: > > On Thu, 04 Nov 2010 12:05:25 -0200, Michael Gentry < > [email protected]> > > wrote: > > > >> I believe running exploded is against the security regulations here. > > > > Why? > > > That is a long story to answer, but let's just say they have security > guidelines they (the production support team) follow. > > > >> Also, wouldn't you have to turn production mode off for Tapestry to > >> pick up changes to the TML? > > > > Absolutely no. Tapestry picks up changes (aka live class reloading) in > > templates, property files and component, page and mixin classes in > > production mode too. Production mode, as far as I can remember, affects > just > > the default error page and some configuration symbols. > > > I did not realize that. I guess coming from a WebObjects background, > I expected production mode to turn off the template reloading feature > to improve performance (no scanning for changes, for example). I've > learned something new today. :-) > > Thanks, > > mrg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
