Activity
From 2009-03-31 to 2009-04-29
2009-04-22
-
18:00 Bug #3152 (Resolved): The Reflection does not recognize changes in class files
- Applied in changeset r2175.
-
16:44 Bug #3152 (Resolved): The Reflection does not recognize changes in class files
- If a class file is changed in development context, the Reflection Service should re-reflect that class and store the ...
-
18:00 Bug #3121 (Resolved): canProcessRequest is not called in ActionControllers
- Applied in changeset r2175.
-
17:15 Feature #3153 (New): Support of action based filter rules defined by annotation.
- Similar to #3092 there should be a way to declare additional filter rules for the arguments of an action method:
<... -
09:12 Bug #3130 (Needs Feedback): ValidatorResolver does not work for float/numeric/mixed typed method arguments
- If committed a fix for this in r2171. This needs verification as I don't have an overview of all implications. Valida...
2009-04-18
-
17:44 Bug #3130 (Resolved): ValidatorResolver does not work for float/numeric/mixed typed method arguments
- While implementing view helpers for Fluid I'm struggling with validation of the view helper arguments:...
2009-04-17
-
15:03 Bug #3121 (Resolved): canProcessRequest is not called in ActionControllers
- It seems, canProcessRequest() is never called in Action Controllers, so CLI-Controllers can be called through the bro...
2009-04-16
-
09:00 Feature #3092 (Resolved): Support annotation-based validation rules in controller actions
- Applied in changeset r2159.
-
01:00 Feature #3091 (Resolved): Support new method "initializeXYAction" in controllers
- Applied in changeset r2152.
2009-04-15
-
01:24 Feature #3093 (Resolved): Implement annotation based validation rules for models
- Make these @validate annotations work in a model:...
-
01:11 Feature #3092 (Resolved): Support annotation-based validation rules in controller actions
- It should be possible to define additional validation rules for arguments of a controller action by declaring them in...
-
01:05 Feature #3091 (Resolved): Support new method "initializeXYAction" in controllers
- Controllers should check if a method "initializeFooAction" exists for an action "foo" and call it before the action "...
2009-04-06
-
08:05 Feature #3041 (Closed): Caching Framework - ask for validity
- It woul be useful to ask the cache if it is still valid.
Background:
If something critical is cached - that for ...
2009-04-03
-
23:00 Bug #3034 (Resolved): The Resolve Handler Resolver doesn't check if potential resolve handlers are registered objects
- Applied in changeset r2127.
-
22:05 Bug #3034 (Resolved): The Resolve Handler Resolver doesn't check if potential resolve handlers are registered objects
- While resolving possible resolve handlers, a list of all classes implementing the ResolveHandlerInterface is compiled...
-
22:08 Bug #3027: Rev 2122 results in an Exeption when loading FLOW3 a second time after clearing the chache
- This Exception is created when an aspect for the RequestHandler is defined.
After removing the aspect the exception ... -
22:07 Bug #3027: Rev 2122 results in an Exeption when loading FLOW3 a second time after clearing the chache
- Christoph Blömer wrote:
> I made a new checkout, cleared the cache und tried it again.
>
> The problem still exis... -
21:19 Bug #3027: Rev 2122 results in an Exeption when loading FLOW3 a second time after clearing the chache
- I made a new checkout, cleared the cache und tried it again.
The problem still exists. Nothing has changed.
The b... -
18:00 Bug #3027 (Resolved): Rev 2122 results in an Exeption when loading FLOW3 a second time after clearing the chache
- Applied in changeset r2123.
-
16:12 Bug #3027: Rev 2122 results in an Exeption when loading FLOW3 a second time after clearing the chache
- Explanation of the reason for this bug:
The object manager's registerObjectType() method registers the RouterInter... -
14:09 Bug #3027: Rev 2122 results in an Exeption when loading FLOW3 a second time after clearing the chache
- Attached a backtrace exploiting this bug
-
11:05 Bug #3027 (Accepted): Rev 2122 results in an Exeption when loading FLOW3 a second time after clearing the chache
-
12:29 Feature #3030 (Resolved): Testing framework can send bug report to mailinglist
- After the test suites are completed and a test failed, ask the Developer if a detailed bug report should be send to t...
-
11:50 Bug #3029 (Resolved): Routing is not working correctly on all platforms
- I am getting this error when i request any URL with a path part (http://flow3.local/testing , http://flow3.local/test...
2009-04-02
-
22:19 Bug #3027 (Resolved): Rev 2122 results in an Exeption when loading FLOW3 a second time after clearing the chache
- In Development Context I get:
#1166550023: Object "F3\WebDAV\MVC\RequestHandler_AOPProxy_Development" is not registe...
2009-03-31
Also available in: Atom