[MAGNOLIA-4291] ioc: allow configuration of non scoped objects Created: 01/Jul/11  Updated: 22/Mar/12  Resolved: 29/Aug/11

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

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:
relation
is related to MAGNOLIA-4260 ioc: component configuration in modul... 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   

We currently support singletons and request and session scoped mappings to be configured in Guice. Other configured mapped are kept for use with newInstance(...).

We need separate config for non-scoped objects that we need in the container and those that should be used with newInstance(...)



 Comments   
Comment by Tobias Mattsson [ 15/Jul/11 ]

See more details at
http://wiki.magnolia-cms.com/display/DEV/Guice+implementation#Guiceimplementation-Additionalconstructorarguments

Comment by Philipp Bärfuss [ 12/Aug/11 ]

Is this a ticket we have to work on in sprint I?

Comment by Tobias Mattsson [ 15/Aug/11 ]

Yes, we have to come up with a design for this.

Comment by Tobias Mattsson [ 29/Aug/11 ]

This is handled by configuring them as type mappings in the module descriptor.

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