[BLOSSOM-134] Show registered Blossom Templates/Components in admincentral Created: 23/Sep/13  Updated: 03/Nov/20  Resolved: 23/Sep/13

Status: Closed
Project: Blossom
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Sigurd Rolfes Assignee: Tobias Mattsson
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
supersession
supersedes MGNLUI-6145 checkBoxField: 'defaultValue' propert... 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   

It would be fine to have registered Blossom Templates/Components visible in the admincentral view.

When implementing components via Blossom (Spring controllers) you don't see them in the modules structure so you can't be sure if everything is fine and components are registrated correctly.

I would like to have them in the modules structure as any other component, e. g. with property type=blossom.

This way you can see all components, blossom and non-blossom components, that may be chosen for configuring availability.



 Comments   
Comment by Tobias Mattsson [ 23/Sep/13 ]

Hi Sigurd,

Unless you see problems during startup all should be fine and all the components should be registered correctly.

Changing the mechanism to store also in the JCR would be an inferior solution and would conflict with the default registration by configuration mechanism.

If you do a find-a-all-files in your IDE for "<your-module>:components/" you will get a list of all available components in your project. Also consider using the @AvailableComponentClasses annotation to not have to repeat the ids everywhere.

Comment by Sigurd Rolfes [ 23/Sep/13 ]

Hi Tobias,

sure, for me it is not a great problem. But imagine a master user who configures availability and composes pages/ares. This is not necessarily a developer or at least a Spring developer.

The developer would have to tell him or make a separate list of all ids of implemented controllers.

You could put it at a place where it does not hurt, e. g. Blossom module (similar to the dialogs in version 2.0).

Sigurd

Comment by Tobias Mattsson [ 23/Sep/13 ]

We have plans going forward to provide an improved user experience for configuring templates and dialogs. As an example picking available options rather than putting down the exact ids. I think this is best served there.

Thanks for your input!

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