I noticed that the Clay component saves the displayElementObject state in saveState. It would seem to me that this would cause some unnecessary overhead in terms of space when using server side state management. Since the displayElement root is already being cached globally in the TemplateConfigBean, would it be a valid optimization to have the Clay component retrieve it from there instead of "caching" it as part of the component state?
Is there any reason why this needs to be saved as component state? Thanks, Ryan
