[
https://issues.apache.org/jira/browse/WW-5301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17706299#comment-17706299
]
Kusal Kithul-Godage edited comment on WW-5301 at 3/29/23 9:46 AM:
------------------------------------------------------------------
Ah I see, I am defining the default bean in struts.xml using:
{{<constant name="struts.velocity.manager.classname"
value="com.CustomVelocityManager"/>}}
This is being ignored as the default VelocityManager bean has already been set
before this constant is read.
So do you think we should change the XML load order from
{{struts-default.xml,struts-plugin.xml,struts.xml}}
to
{{struts-default.xml,struts.xml,struts-plugin.xml}}
Will that cause any other issues?
was (Author: JIRAUSER298544):
Ah I see, I am defining the default bean in struts.xml using:
{{<constant name="struts.velocity.manager.classname"
value="com.CustomVelocityManager"/>}}
This is being ignored as the VelocityManager bean has already been registered
before this constant is read.
So do you think we should change the XML load order from
{{struts-default.xml,struts-plugin.xml,struts.xml}}
to
{{struts-default.xml,struts.xml,struts-plugin.xml}}
Will that cause any other issues?
> 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
>
> I'm possibly missing something here but as far as I can tell
> struts-plugin.xml is always loaded before struts.xml.
> Changing the load order here probably isn't a good solution either.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
