On Fri, Jan 16, 2009 at 1:42 PM, Christian Edward Gruber <christianedwardgru...@gmail.com> wrote: > In some ways, a Page is just a Component that has no parent.
A page is a top level component. Technically, the page component is actually the root component of the actual page (true pages are a concept internal to Tapestry) but it all works out the same in the end. Pages have a lifecycle (loaded, attached and detached). > I'm not 100% > sure why they're separated, except that it's a historical artifact. A bit more than that. Naming: page names can appear in URLs whereas component types do not, instead component ids. Pages do have some special responsibilities (activation, passivation, error handling). > Components (and pages being a special-case component) are a piece of java > software that renders itself (usually as tags and possibly with a body, > which may contain the renderings of other components.) It's quite different > than tag-libs. Taglibs get turned into generated code that executes with > other JSP code. Components don't generate code, they are live objects with > life-cycles that respond to events, just like a swing or Mac-OS Cocoa > component. JSP's code gets turned into a very very long execute() method on > a servlet, so there's lots of entanglement. There was a good article on > this in the t5 docs, but I can't remember which one. > > Christian. > > On 16-Jan-09, at 16:01 , mjparme wrote: > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
