Prasanna, Generally, Spring configuration files should be packaged in their associated JARs with property substitution for configurable items (e.g. connection pool min and max sizes). Unfortunately, Spring does not allow component wiring to be modified through property files. Since plugins are new components, we have to expose the underlying Spring configuration files to allow plugins to be loaded. I think our current approach was a solid pragmatic step forward -- a nice midpoint between nothing and a complete driver/plugin model.
Thanks, -John On Aug 21, 2013, at 9:51 AM, Prasanna Santhanam <t...@apache.org> wrote: > On Tue, Aug 20, 2013 at 05:43:17PM -0400, John Burwell wrote: >> Leaky Abstraction: Plugins are registered through a Spring >> configuration file. In addition to being operator unfriendly (most >> sysadmins are not Spring experts nor do they want to be), we expose >> the core bootstrapping mechanism to operators. Therefore, a >> misconfiguration could negatively impact the injection/configuration >> of internal management server components. Essentially handing them >> a loaded shotgun pointed at our right foot. > > This has been my pet-peeve too and I was told you can write properties files > above the spring contexts to make it simpler for operators to look at. > > Overall a great proposal and look forward to see more concrete steps > that follow on the implementation details. > > -- > Prasanna., > > ------------------------ > Powered by BigRock.com >
signature.asc
Description: Message signed with OpenPGP using GPGMail
