[MGNLPN-171] Bind default implementation for SegmentRegistry in integration module Created: 13/Jun/14  Updated: 17/Jun/14  Resolved: 17/Jun/14

Status: Closed
Project: Magnolia Personalization
Component/s: Integration
Affects Version/s: None
Fix Version/s: 1.0

Type: Bug Priority: Critical
Reporter: Philip Mundt Assignee: Philip Mundt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File MGNLPN-171.patch    
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: Personalisation

 Description   

If one installs the integration module only, the missing default implementation of info.magnolia.personalization.registry.segment.SegmentRegistry will result in an guice error:

No implementation for info.magnolia.personalization.registry.segment.SegmentRegistry was bound.
while locating info.magnolia.personalization.registry.segment.SegmentRegistry
    for parameter 1 at info.magnolia.personalization.variant.RegistryVariantResolver.<init>(RegistryVariantResolver.java:48)


 Comments   
Comment by Philip Mundt [ 13/Jun/14 ]

Attached a patch which fixes the issue by using a NullSegmentRegistry.

Generated at Mon Feb 12 06:35:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.