While configuring /server/rendering/freemarker/sharedVariables, one can enter an endless loop, quickly resulting in a StackOverflowError; this happens, for instance, when adding a node under sharedVariables, and not filling it in it with a class attribute. The error only shows up on startup, so if the configuration is complete and correct before restarting Magnolia, one should be safe.

The reason this happens is because FreemarkerConfig#addSharedVariable needs an instance of ObjectWrapper, and in turns, our MagnoliaObjectWrapper needs an instance of FreemarkerConfig, which it gets via Components Since Content2Bean calls addSharedVariable() before FreemarkerConfig is registered in Components, this results in a stack overflow.