Task #6598
Make global objects, that should be available in runtime evaluations, configurable
| Status: | Resolved | Start date: | 2010-02-25 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Andreas Förthner | % Done: | 100% |
|
| Category: | AOP | |||
| Target version: | TYPO3 Flow Base Distribution - 1.0 alpha 10 | |||
| Sprint: | Has patch: | |||
| PHP Version: | Complexity: |
Description
At the moment only current.party can be referenced within a pointcut expression. There should be a configuration setting where you can register other objects under the "current." scope. The setting must have an unique name like "party" and a PHP statement, that retrieves this object like "$objectManager->getObject('foo')->getSomething();"
Associated revisions
- [+TASK] FLOW3 (Object): Added session scope related methods to the object manager and interface.
- [+FEATURE] FLOW3 (AOP): Added a matches operator as a new possibility for runtime evaluations.
- [+FEATURE] FLOW3 (AOP): Global objects available in runtime evaluations can now be configured in the settings. Resolves #6598.
- [+FEATURE] FLOW3 (Security): Implemented query rewriting according to the security policy. Relates to #5659, Resolves #6604.
History
#1 Updated by Andreas Förthner about 5 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset r4613.
#2 Updated by Andreas Förthner about 5 years ago
- Status changed from Resolved to Accepted
We should simply use object names and fetch the objects from the object manager. No evil eval anymore.
#3 Updated by Robert Lemke about 5 years ago
- Status changed from Accepted to Resolved
- Target version set to 1.0 alpha 10