[BLOSSOM-199] Exception thrown when dialog factory fails should include called method in message Created: 23/Jan/15  Updated: 30/Jan/15  Resolved: 23/Jan/15

Status: Closed
Project: Blossom
Component/s: None
Affects Version/s: None
Fix Version/s: 3.0.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

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)

 Description   

Exceptions spell out only the class when a @DialogFactory annotated method is called.

It should include the method to make debugging easier.

Like this:

Caused by: info.magnolia.registry.RegistrationException: Failed to create dialog for method [public void info.magnolia.blossom.sample.module.MainTemplate.dialog(info.magnolia.ui.dialog.config.DialogBuilder,info.magnolia.ui.framework.config.UiConfig)]
	at info.magnolia.module.blossom.dialog.BlossomDialogDefinitionProvider.getDialogDefinition(BlossomDialogDefinitionProvider.java:78)
	at info.magnolia.ui.dialog.registry.DialogDefinitionRegistry.getDialogDefinition(DialogDefinitionRegistry.java:60)
	at info.magnolia.module.blossom.dialog.BlossomFormDialogPresenter.start(BlossomFormDialogPresenter.java:90)
	... 103 more

Generated at Sun Feb 11 23:31:08 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.