On Wed, Aug 24, 2005 at 04:21:58PM +1000, Brett Porter wrote: > I think this is reasonable, but I'd like to allow multiple sources > (properties, and multiple files). The existence of the filtering element > can be used to trigger it. > > <filtering> > <filterTokens> > <token>value</token> > </filterTokens> > <filterFiles> > <filterFile>foo.properties</filterFile> > <filterFile>bar.properties</filterFile> > </filterFiles> > </filtering>
And what if you use something like this (in resource): <resource> ... <filtering>profile-reference</filtering> </resource> where the profile id references a filter specification along the above line augmented with an context name, which can be referenced. E.g. <filtering>WAS-5.1</filtering> incze --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
