Bug #2601
canProcessRequest doesn't accept mocked requests
| Status: | Resolved | Start date: | 2009-02-09 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | Robert Lemke | % Done: | 100% |
|
| Category: | MVC | |||
| Target version: | TYPO3 Flow Base Distribution - 1.0 alpha 1 | |||
| PHP Version: | Complexity: | |||
| Has patch: | Affected Flow version: |
Description
Currently the canProcessRequest() method only checks if the class name of the request 100% matches the class names specified in $this->supportedRequestTypes. Therefore sub classes of these (like mock web requests) are not accepted.
Associated revisions
Known issue in this commit: the TYPO3 backend and TYPO3CR backend don't work at the moment because the REST controller is not fully functional.
- FLOW3: (MVC) The canProcessRequest() method in the AbstractController now also accepts sub classes of the supported request types. Fixes #2601
- FLOW3: (MVC) Refactored parts of the ActionController. Also changed the order in which certain methods are called. The order is now: resolveActionMethodName(), initializeArguments(), mapRequestArgumentsToLocalArguments(), initializeView(), initializeAction(), callActionMethod(). Also resolves #2580.
- FLOW3: (MVC) Fixed parts of the RESTController. Note: the show, delete and update actions currently don't work due to a new way of handling ids. I'm working on it ...
- FLOW3: (MVC) Wrote proper tests for the REST controller. There are still missing tests for resolveActionMethodName() method.
History
#1 Updated by Robert Lemke over 6 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Applied in changeset r1884.