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

2017-07-12 Thread Ken McWilliams
Thank you for meditating on this! On Mon, Jul 10, 2017 at 2:07 AM, Lukasz Lenart wrote: > I thought about this idea and it requires implementation of a root > Dispatcher with list of child Dispatchers per config file/package/etc. > Doable but won't happen soon ;-) > > 2017-06-23 23:22 GMT+02:00

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

2017-07-10 Thread Lukasz Lenart
I thought about this idea and it requires implementation of a root Dispatcher with list of child Dispatchers per config file/package/etc. Doable but won't happen soon ;-) 2017-06-23 23:22 GMT+02:00 Ken McWilliams : > Yes, something like that. > > But I think i can be done in a hackish way without

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

2017-06-23 Thread Ken McWilliams
Yes, something like that. But I think i can be done in a hackish way without much change. Really it is the conventions plugin that is at fault, or rather a lack of convention regarding sharing configuration that aught to be standardized. The beans and constants are currently scoped globally, just

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

2017-06-22 Thread Lukasz Lenart
2017-06-22 2:45 GMT+02:00 Ken McWilliams : > 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 jus

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

2017-06-21 Thread Ken McWilliams
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)

2017-06-21 Thread Adam Brin
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)

2017-06-21 Thread Ken McWilliams
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

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

2017-06-20 Thread Lukasz Lenart
2017-06-20 21:48 GMT+02:00 Ken McWilliams : > I like to use the conventions plugin but find myself fighting with it more > often than not. > > I think conventions should establish a "convention". Now the plugin > certainly does this in the *singular* but say I want restful services > handled by con

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

2017-06-20 Thread Ken McWilliams
I like to use the conventions plugin but find myself fighting with it more often than not. I think conventions should establish a "convention". Now the plugin certainly does this in the *singular* but say I want restful services handled by conventions, and then I want perhaps a set of packages to