[MAGNOLIA-4375] Support thread local nested component providers Created: 17/Apr/12  Updated: 31/May/12  Resolved: 07/May/12

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

Type: Improvement Priority: Neutral
Reporter: Tobias Mattsson Assignee: Tobias Mattsson
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-4356 Update 5.0 branch for Magnolia 4.5 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   

In order to use child component providers, for instance one for every user housing the vaadin application he/she interacts with, we need support for exposing that component provider via info.magnolia.objectfactory.Components. It should be implemented using a thread local that gets set once we're executing code residing in such a child component provider.



 Comments   
Comment by Daniel Lipp [ 27/Apr/12 ]

missing unit test

Comment by Tobias Mattsson [ 07/May/12 ]

Test added.

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