During decorator rendering, Confluence does not use a velocity context exposing the current application state with respect to spring beans or Velocity context item plugin modules.

This regression has been caused by the axing of some ostensibly redundant code from the ProfilingPageFilter and the ApplyDecoratorDirective. This code instantiates a new ConfluenceVelocityContext and copies its keys over to the context provided by the WebWork VelocityManager. This is actually necessary as the chained ConfluenceVelocityContext used by the WebWork context is instantiated once at bootstrapping and is reused for all subsequent requests. This context will never change and never see any newly enabled velocity context modules (and will never remove any disabled ones either).

The main symptom of this bug is that Velocity context item modules will not be available when Confluence is first upgraded or setup or a plugin containing such modules is installed for the first time.