Beehive
  1. Beehive
  2. BEEHIVE-82

Page Flow Overview - hitting a page flow URL

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: V1Alpha
    • Fix Version/s: V1Beta
    • Component/s: Documentation
    • Labels:
      None

      Description

      I think it would be nice if the overview mentioned that page flows are URL-addressable. Hitting /foo/MyPageFlow.jpf creates foo.MyPageFlow (if it's not already created) and runs its begin action. Similarly, hitting /foo/someAction.do creates foo.MyPageFlow (if it's not already created) and runs action "someAction".

        Activity

        Hide
        Steve Hanson added a comment -

        I added the following text to the 'overview' topic:

        "
        Note that controller classes, and the actions they contain, are URL addressable. Hitting the following URL creates an instance of the controller class foo.MyControllerClass and runs its begin action. (When no other action is specified, the begin method is run by default.)

        http://some.domain.com/foo/MyControllerClass.jpf

        Hitting the following URL creates an instance of foo.MyControllerClass (if it doesn't already exist) and invokes the someAction action. Note that the controller class isn't mentioned by name: it's assumed that only one controller class exists in the directory, so there is only one candidate controller class to instantiate.

        http://some.domain.com/foo/someAction.do
        "

        Show
        Steve Hanson added a comment - I added the following text to the 'overview' topic: " Note that controller classes, and the actions they contain, are URL addressable. Hitting the following URL creates an instance of the controller class foo.MyControllerClass and runs its begin action. (When no other action is specified, the begin method is run by default.) http://some.domain.com/foo/MyControllerClass.jpf Hitting the following URL creates an instance of foo.MyControllerClass (if it doesn't already exist) and invokes the someAction action. Note that the controller class isn't mentioned by name: it's assumed that only one controller class exists in the directory, so there is only one candidate controller class to instantiate. http://some.domain.com/foo/someAction.do "
        Hide
        Nathan Jantz added a comment -

        Verified in 1.0m1-rc2.

        Show
        Nathan Jantz added a comment - Verified in 1.0m1-rc2.

          People

          • Assignee:
            Nathan Jantz
            Reporter:
            Rich Feit
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development