[BLOSSOM-239] Defining a Blossom component with a DynamicFragmentDefinition Created: 29/Aug/16  Updated: 17/Aug/23  Resolved: 17/Aug/23

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

Type: Improvement Priority: Neutral
Reporter: Leo Lozes Assignee: Unassigned
Resolution: Workaround exists Votes: 0
Labels: blossom, cache
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
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 are trying to define a component, and we wonder if it would be possible to define the fragmentDefintion as a @Template property, as explained in the docs .

We checked the Blossom module code and didn't find anything related with the DynamicFragmentDefinition, so maybe it's still not implemented.

Workaround
We're using the @PreRegister annotation to define this property:

@PreRegister
public void register(BlossomTemplateDefinition templateDefinition) {
  FragmentDefinition fragmentDefinition = new DynamicFragmentDefinition();
  templateDefinition.setFragmentDefinition(fragmentDefinition);
}

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