[MAGNOLIA-925] Filter configuration in config repository Created: 11/Jun/06 Updated: 23/Jan/13 Resolved: 27/Oct/06 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 3.0 Beta 1 |
| Fix Version/s: | 3.0 RC4 |
| Type: | Improvement | Priority: | Blocker |
| Reporter: | Fabrizio Giustina | Assignee: | Fabrizio Giustina |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: |
| Description |
|
Complete the work on info.magnolia.cms.filters.MagnoliaManagedFilter:
This could allow modules to add filters at runtime, without any need for modifying web.xml, and changing parameters without a restart (for example, login configuration) |
| Comments |
| Comment by Philipp Bracher [ 09/Aug/06 ] |
|
Fabrizios instructions how to proceed: This is what should be done:
|
| Comment by Sameer Charles [ 09/Aug/06 ] |
|
Did someone started on this issue? if not I will implement as stated in the mail from fabrizio. |
| Comment by Sameer Charles [ 10/Aug/06 ] |
|
Updated FilterManager so it reads filters from Configuration, its not an ObservedManager
Wont change anything for the moment, needs more testing. |
| Comment by Fabrizio Giustina [ 14/Aug/06 ] |
|
added priority handling and moved cache filter configuration to cache module. Also read parameters from jcr. |
| Comment by Philipp Bracher [ 22/Aug/06 ] |
|
The filters are nor reinitialized by changing there configuration. If one changes for example the bypass property the server needs a restart (actually the instance is not responding any more). The problem is that the FilterManager should call the init() method of the filters and not the MagnoliaManagedFilter.init() method. |
| Comment by Fabrizio Giustina [ 06/Oct/06 ] |
|
reload issue fixed in svn |
| Comment by Magnolia International [ 27/Oct/06 ] |
|
reopening to change fix version to rc4 |