Versions Compared

Old Version 23

changes.mady.by.user Howard Ship

Saved on

compared with

New Version 24

changes.mady.by.user Howard Ship

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

Although you code Tapestry pages and components as if they were ordinary POJOs

Footnote
Wiki Markup
{footnote}Plain Old Java Object. Tapestry does not require you to extend any base classes or implement any special interfaces.{footnote}
Plain Old Java Object. Tapestry does not require you to extend any base classes or implement any special interfaces.
, as deployed by Tapestry they are closer to a traditional servlet: a single instance of each page services requests from multiple threads. Behind the scenes, Tapestry transforms you code, rewriting it on the fly.
...
Support for multiple Tapestry applications in the same web application was a specific non-goal in Tapestry 5 (it needlessly complicated Tapestry 4). Given how loosely connected Tapestry 5 pages are from each other, there doesn't seem to be an advantage to doing so ... and certainly, in terms of memory utilization, there is a significant down side, were it even possible.
 Wiki Markup
{scrollbar}
...
 Wiki Markup
{display-footnotes}