Skip to main contentdfsdf

Qingbo Zhou's List: Tapestry

  • Mar 15, 09

    All incoming requests originate with the TapestryFilter, which is configured inside the application's web.xml.

    The TapestryFilter is responsible for a number of startup and initialization functions.

    When it receives a request, the TapestryFilter obtains the HttpServletRequestHandler service, and invokes its service() method.

    tapestry.apache.org/...request.html tapestry

    • All incoming requests originate with the TapestryFilter, which is configured inside the application's web.xml.

      The TapestryFilter is responsible for a number of startup and initialization functions.

      When it receives a request, the TapestryFilter obtains the HttpServletRequestHandler service, and invokes its service() method.

  • Mar 15, 09

    tapestry.apache.org/...event.html tapestry

    • The ActionLink component creates an action URL.

      The URL identifies the page that contains the component ("chooser"), the type of event (unless it is "action", the default and most common event type), the id of the component within the page ("select"), plus the additional context value(s).

      A sample URL: http://localhost:8080/chooser.select/3.

      When there are additional context values, they are appended to the path.

    • "action" is the name of the default event type; the ActionLink and Form components each use this event type. If you omit the component part of the OnEvent annotation, then you'll recieve notifications from all contained components, possibly including nested components (due to event bubbling).
1 - 4 of 4
20 items/page
List Comments (0)