[MAGNOLIA-3125] ObservedComponentFactory.newInstance() should return a null-object when the observed path doesn't exist yet and a default implementation can not be determined Created: 12/Mar/10  Updated: 04/Nov/15  Resolved: 04/Nov/15

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

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

Issue Links:
relation
is related to MAGNOLIA-3011 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)
Date of First Response:

 Description   

Since MAGNOLIA-3011, ObservedComponentFactory.newInstance() can return a new instance of the request object even if the observed path does not exist yet, as long as it's a concrete class. If the object is requested by interface, we could return a null-object implementation of the interface. (Proxytoy's null object proxy) for example is such an implementation)

There's a currently failing/commented out test, see: info.magnolia.objectfactory.ObservedComponentFactoryTest#testReturnsANullProxyUntilPathExistsForNonConcreteTypes



 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

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