As long as it's a deprecation and not deletion, I think it will be fine. i.e. in 2.1.x you can configure the app to use the old mechanism.Yeah, that's a good idea. Perhaps a new plugin named convention or something. I'll create a dev branch and start with that name. We can always change it later. I'll package it in org.apache.struts2.convention and try to find some smaller property names (although I hoping that they won't be used much and being explicit is important).The only other (really small picky thing) is the name "codebehind". What I see Brian doing to providing mapping and configuration. When I think of "codebehind" I think of the code that looks up a result template following naming conventions. Although these may have been considered one-and-the-same, I think by separating them by names we can enhance both concurrently. i.e. rails scaffolding - introduce a plug-in that can generate JSP code by reflecting on the action
-bp
smime.p7s
Description: S/MIME Cryptographic Signature
