<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 5/13/14 5:03 PM, Cantor, Scott
wrote:<br>
</div>
<blockquote cite="mid:CF9800B7.CC4E%25cantor.2@osu.edu" type="cite">
<pre wrap="">On 5/13/14, 4:58 PM, "Tom Zeller" <a class="moz-txt-link-rfc2396E" href="mailto:tzeller@dragonacea.biz"><tzeller@dragonacea.biz></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
Understood, and for tests, @ContextConfiguration takes an initializers
parameter. But, our ReloadableSpringService class uses
SpringSupport#newContext() to create a new application context, so we
will have to apply the custom app ctx initializer manually, IIUC. Most
of those services are in system/conf/services-system.xml, I think.
</pre>
</blockquote>
<pre wrap="">
Only if properties aren't inherited, </pre>
</blockquote>
<br>
Right. To just do some global properties, we should just need the 1
initializer declared for the root web app context.<br>
<br>
My other comments about using initializers in other places was
musing that they would be nice to have if you wanted to do something
else and more complex with the non-root contexts.<br>
<br>
<blockquote cite="mid:CF9800B7.CC4E%25cantor.2@osu.edu" type="cite">
<pre wrap="">but I thought they were.
</pre>
</blockquote>
<br>
I mentioned on the Friday call, but I did test this in a scratch
workspace with some manually created generic contexts, and the
properties were inherited as expected, based on having looked at
their code.<br>
<br>
</body>
</html>