The implementation is defined as a bean, but we didn't provide a way
to change the bean used. That means you can't plugin your
implementation without building the plugin yourself. I will fix in
trunk soon, if you want to build it yourself, you need to change this
file:

 /plugins/convention/src/main/resources/struts-plugin.xml

and change this line:

<bean type="org.apache.struts2.convention.ActionNameBuilder"
class="org.apache.struts2.convention.SEOActionNameBuilder"/>

with your actual class.

musachy

On Tue, Feb 10, 2009 at 10:16 PM, denis cabasson
<denis.cabas...@polytechnique.org> wrote:
> Hi folks!
>
> I am using Struts 2.0.14 on a project with a fairly big existing codebase. I
> just tried to upgrade to struts 2.1.6 (as the release is now in GA).
> We were using extensively the zero configuration approach with the
> codebehind plugin and I am now looking at upgrading to the convention
> plugin.
>
> My last remaining hurdle is the change in the ActionNameBuilder. The plugin
> uses the SEOActionNameBuilder which is a big change from what we had in
> Struts 2.0.14 : The name of our action is no longer myProfile, but
> my-profile, which involves changing all existing references to the action by
> its name (and we have quite a fex of them).
>
> So I'd like to use the convention plugin, with DefaultActionNameBuilder
> instead of the SEO. I configured struts.xml to have this bean created, my
> question is how do I get the convention plugin to use that one rather than
> the SEO one?
>
> Thanks for your help, and keep up the good work, you the struts team!
>
> Denis.
>



-- 
"Hey you! Would you help me to carry the stone?" Pink Floyd

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org

Reply via email to