Resources.

[Rod Widdowson]

Done.  

See r4940

The somewhat surprising result is that we do *not* need a bean factory to
achieve this, maybe it is because I was just looking at string parameters. 

What I have not looked at is how to inject the property-placeholder
programmatically.  The spring injection as per 
http://svn.shibboleth.net/view/java-identity-provider/trunk/idp-attribute-re
solver-spring/src/test/resources/net/shibboleth/idp/attribute/resolver/sprin
g/naturestudy/CustomBeanReplace.xml?view=markup

is a wee bit ugly.

I had initially intended to look at a filtering
org.springframework.core.io.Resource at the same time.  But given this
result it didn't seem worthwhile.

Rod

> -----Original Message-----
> From: dev-bounces at shibboleth.net [mailto:dev-bounces at shibboleth.net]
> On Behalf Of Tom Zeller
> Sent: 08 November 2013 21:20
> To: Shib Dev
> Subject: Re: Resources.
> Importance: Low
> 
> > http://stackoverflow.com/questions/12936080/using-a-properties-file-
> with-a-custom-bean-parser.
> 
> Rod, do you think you could add a unit test that verifies the behavior
> described above, where post-processing is silently omitted if we do
> not provide a FactoryBean when using our custom extensible XML
> authoring, please ?
> 
> Let's make sure the FactoryBeans are necessary, first, methinks, and
> test Spring 4 too.
> --
> To unsubscribe from this list send an email to dev-
> unsubscribe at shibboleth.net