using Velocity to externalize configuration properties ?

[Rod Widdowson]

I got side tracked while looking at Resources...

FYI:  On Friday I asked how hard it would be to provide our own plugin to go
from a <Something> to a Dom, thus allowing us to do our own schema
management.    I am new to the code and so if someone answered this and I
missed it I apologise.

I just happened upon XMLBeanDefinitionReader#setDocumentLoader()

Which takes one parameter of type
org.springframework.beans.factory.xml.DocumentLoader.  This is an interface
with but one method which effectively takes an org.xml.sax.InputSource, a
org.xml.sax.EntityResolver and a few other things and produces a
org.w3c.dom.Document from them.

This seems to answer the question of whether is possible (although as I say
someone probably answered that already), but I am not qualified to judge
whether that interface is something we could create based from our own
library code.

Rod

> -----Original Message-----
> From: dev-bounces at shibboleth.net [mailto:dev-bounces at shibboleth.net]
> On Behalf Of Cantor, Scott
> Sent: 03 August 2013 00:48
> To: Shib Dev
> Subject: Re: using Velocity to externalize configuration properties ?
> 
> On Aug 2, 2013, at 6:44 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:
> >
> > Not arguing, but it seems counterintuitive to replace a URN with a URL
> > to prevent remote lookups.
> 
> We wouldn't be subject to remote lookups, but it is silly to fix something
by
> adding a bogus location.
> 
> 
> -- Scott
> --
> To unsubscribe from this list send an email to dev-
> unsubscribe at shibboleth.net