Re: Limitations using Struts2-conventions-plugin (lack of multiple configuration roots)

Sure, doing Struts2/Shiro integration at the moment. Will come back to this, it was a rant from running into issues when setting up some personal demo projects. The limitation from one static configuration to cover all conventions (which really just lets you use one convention, at least well). And

Re: Limitations using Struts2-conventions-plugin (lack of multiple configuration roots)

Hi Ken, I think I’m with Lukasz, I wonder if the following might be useful for folks to get onto the same page (just from my own head): • a sample project that shows the trade-offs? • a diagram or visualization that shows how the new model might lay out? thanks, adam -- ___

Re: Limitations using Struts2-conventions-plugin (lack of multiple configuration roots)

Sure, it would be most ideal if there could be variables scoped to struts action packages, and accessible from only within that package. Step 1 (Create beans and constants scoped to the package level): Simply creating an interceptor to hold all the configuration that is currently found in struts-p