[MAGNOLIA-1508] content2bean: allow forcing object creating Created: 04/May/07 Updated: 23/Jan/13 Resolved: 04/May/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | 3.1 M2 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Philipp Bärfuss |
| 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)
|
| Description |
|
Allow putting the processor in a force creation mode, so that it creates the object sturcture as good as possible. This is very important if you don't like to let fail the creation process only because the user defined a wrong class for a subelement. Example: build the filters even if the user misconfigured one of the voters, otherwise the admin interface is not reachable |