How to remove custom thymeleaf beans from widgets (What are all the beans?…
How to remove custom thymeleaf beans from widgets
Can we remove all of them?
Remove all except
What are all the beans?
widget's way of retrieving
Why is this needed?
talks to CMS
talks to NavigationWebService
talks to EventReg
talks to TripsWebService
Talks to CMS to get article metadata
generic call to retrieve data from
only in rei.com
gets inspriational(?) type of data
who would use this?
Currently, it only retrieves
content from EventReg
Need Monitoring set up
What does monitoring
mean in this aspect?
CMS gets notified when changes
occur that relate to the annotated
What constitutes as a change?
new one gets introduced
an annotation (or numerous annotations)
What kind of dashboard is needed?
count of all annotated beans
how can we do this?
count of all widgets using annotated beans
How can we do this?
count of all page configs with widgets that have annotated beans
Add performance enhancements
an annotated bean referenced multiple times
within a widget
in multiple widgets within the same page cofig
within a ContentDataModel
how can we prove these features are actually enhancing page loading times?
A naming convention is chosen for model
why is this important?
our widget creators/maintainers need to know
the way to get the models that get created
What are some naming conventions?
Where will the annotated beans move to?
As a list of key/value pairs in ContentDataModel property
As a list of key/value pairs in a ComponentConfig
as a list of key/value pairs in page-configs
Can these values be verified pre-render time?
This is true currently
Key/value pairs could be written like proxyable
How will users know what to put in this list?
How can this solution support dynamic content?
What is dynamic content in this aspect?
Do we need to worry about this now?
This could be a
instead of a
Where will the 'dynamic' content come from?
Needs to be backwards compatible
The current way needs to be supported
how to do achieve this?
What downstream changes
CMS to support Hippo changes
retrieves new key/value pair
from CMS and does something
similar to proxyable to get content
data retrieved gets injected into
How to tackle recursive calls?
What constitutes as a