2017-06-20 21:48 GMT+02:00 Ken McWilliams <ken.mcwilli...@gmail.com>: > 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 > contain public documents, and another set of packages to require some form > of security but also follow some sort of conventions... well I find it > impossible to use the conventions plugin and need to resort to additional > configuration. Creating packages in struts.xml, or using XML to override > the conventions. > > Do you think it would be reasonable to have the conventions plugin, create > a new configuration interceptor for which all the constants (package level > constants, as there is one interceptor instance per stack), and the rest of > the conventions configuration could be looked up from each of these > configurations? > > So the conventions plugin would need to check each struts package to see if > extends conventions-default and if so, wire the actions at startup for each > in turn. If that is too limiting perhaps just make this one interceptor a > requirement for the scan. > > Also under this scheme, it would be good to create an "include" for the > Java package scan rather than the "exclude" which is more suited to one > root. > > I think this scheme would greatly reduce annotation usage as it would be > possible to stay entirely within established conventions, rendering > overrides unnecessary.
This sounds interesting but I'm not really grasp all the details. Maybe we can start with a one thing and then implement another. Can you split your idea into single steps? Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
