Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: (Per TAP5-1217) Added a couple sections from the long-lost 5.2 trunk docs

...

Notice that Chooser.tml contains an ActionLink component. When rendered on the page, the ActionLink component creates a link with an action URL, which in component event request URL, with the event type set to "action". In this case might look like http://localhost:8080/chooser.select/3

...

Returning false is the same as returning null; event processing will continue to look for more event handlers, in the same component or its parent.

When an event bubbles up from a component to its container, the origin of the event is changed to be the component. For example, a Form component inside a BeanEditForm component may fire a success event. The page containing the BeanEditForm may listen for that event, but it will be from the BeanEditForm component (which makes sense, because the id of the Form inside the BeanEditForm is part of the BeanEditForm's implementation, not its public interface).

Event Method Exceptions

Event methods are allowed to throw any exception (not just runtime exceptions). If an event method does throw an exception, Tapestry will catch the thrown exception and ultimately display the exception report page.

...