Tapestry
  1. Tapestry
  2. TAPESTRY-2528

It should not be possible for component classes to be directly instantiated

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.13
    • Fix Version/s: 5.0.14
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      A common beginner idiom is:

      Object onAction()

      { return new OtherPage(); }

      When they should inject OtherPage.

      Currently, this code works and produces odd effects.

      An explicit error message is needed.

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Closed Closed
        49s 1 Howard M. Lewis Ship 19/Jul/08 18:49
        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12568785 ] jira [ 12590122 ]
        Mark Thomas made changes -
        Workflow jira [ 12435642 ] Default workflow, editable Closed status [ 12568785 ]
        Howard M. Lewis Ship made changes -
        Field Original Value New Value
        Fix Version/s 5.0.14 [ 12313214 ]
        Resolution Fixed [ 1 ]
        Status Open [ 1 ] Closed [ 6 ]
        Howard M. Lewis Ship created issue -

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development