[MAGNOLIA-7284] Registry registers object even if it is not instance of the registry class Created: 20/Mar/18  Updated: 20/Apr/18  Resolved: 18/Apr/18

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

Type: Bug Priority: Neutral
Reporter: Evzen Fochr Assignee: Evzen Fochr
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MTE-107 Move linkSwitchableField definition t... Closed
is depended upon by MGNLUI-4380 Report references to deprecated field... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: Kromeriz 139, Kromeriz 140, Kromeriz 141, Kromeriz 142, Kromeriz 143
Story Points: 5

 Description   

DialogDefinitionRegistry register object even if it is not instance of DialogDefinition and this can cause class cast exception for example while iterating through Collection<DefinitionProvider<T>> served by getAllProviders() in DialogDefinitionValidator. Exaple is /mtk/dialogs/components/linkSwitchableField.yaml



 Comments   
Comment by Roman Kovařík [ 20/Mar/18 ]

Isn't this a problem of abstract registry? If yes, could you move the ticket?

Comment by Evzen Fochr [ 26/Mar/18 ]

This PR will newly report:

 

This is caused by using of deprecated class RegexpVirtualURIMapping from info.magnolia.cms.beans.config instead of info.magnolia.virtualuri.mapping, Severe problem cause not loading definition.

Generated at Mon Feb 12 04:22:25 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.