[ https://issues.apache.org/jira/browse/WW-5301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17706722#comment-17706722 ]
Kusal Kithul-Godage edited comment on WW-5301 at 3/30/23 6:43 AM: ------------------------------------------------------------------ [~lukaszlenart] If the VelocityManager was registered as part of StrutsBeanSelectionProvider as it was previously, the issue would be solved. But how will that work given the class is now part of a separate plugin? was (Author: JIRAUSER298544): [~lukaszlenart] If the VelocityManager was registered as part StrutsBeanSelectionProvider as it was previously, the issue would be solved. But how will that work given the class is now part of a separate plugin? > Impossible to select alternate default VelocityManager bean > ----------------------------------------------------------- > > Key: WW-5301 > URL: https://issues.apache.org/jira/browse/WW-5301 > Project: Struts 2 > Issue Type: Bug > Components: Core, Plugin - Velocity > Affects Versions: 6.1.1 > Reporter: Kusal Kithul-Godage > Priority: Major > Fix For: 6.2.0 > > > I'm possibly missing something here but as far as I can tell > struts-plugin.xml is always loaded before struts.xml. > This means the default VelocityManager bean (#registerBeanSelection) will > always be selected before the default bean can be configured via > {{struts.velocity.manager.classname}} > Changing the load order here probably isn't a good solution either. -- This message was sent by Atlassian Jira (v8.20.10#820010)