[MAGNOLIA-3011] ObservedComponentFactory.newInstance() should return a default implementation when the observed path doesn't exist yet Created: 15/Jan/10  Updated: 23/Jan/13  Resolved: 12/Mar/10

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: None
Fix Version/s: 4.3

Type: Improvement Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MAGNOLIA-3080 Cleanup conundrum between FreemarkerH... Closed
duplicate
is duplicated by MAGNOLIA-2533 FactoryUtil$ObservedObjectFactory sho... Closed
relation
is related to MAGNOLIA-2553 FactoryUtil: should return a proxy ob... Closed
is related to MAGNOLIA-3125 ObservedComponentFactory.newInstance(... Closed
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   

ObservedComponentFactory.newInstance() currently returns null when the observed path doesn't exist yet. It should return a default implementation (to be configured) or some form of null proxy (see for example Proxytoy's null object proxy) so that client code can always keep a reference to the observed singleton without having to care about it's state on the repo, thus making the observation/factory system entirely transparent.



 Comments   
Comment by Magnolia International [ 12/Mar/10 ]

Done for concrete classes; see MAGNOLIA-3125 for interfaces.

Generated at Mon Feb 12 03:42:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.