I agree with the initial assessment that XInclude is the way to go. If someone wants to use XInclude, they should provide the right parser implementation to make it available. I wouldn't bend over backward to do your own inclusion mechanism; put it on the consumer to provide the appropriate parser.
Cheers, Paul On Wed, Mar 2, 2016 at 12:39 PM, Gary Gregory <[email protected]> wrote: > Stemming from discussion in > https://github.com/apache/logging-log4j2/pull/25 > > How about finally adding our own include mechanism: > > <Include monitorIntervalSeconds="60">file://...</Include> > > If Configuration has a monitorInterval, then Includes inherit the > setting, if you set an Include monitorInterval to 0 then, then it is not > watched. > > Thoughts? > > Gary > > -- > E-Mail: [email protected] | [email protected] > Java Persistence with Hibernate, Second Edition > <http://www.manning.com/bauer3/> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > Spring Batch in Action <http://www.manning.com/templier/> > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory >
