<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div>
<blockquote type="cite" class="">
<div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">The
only solution is to stop so many properties. The only real use for them is to expose settings that have to be injected into system beans. The resolver is a good example of that not being needed.</span><br class="">
</div>
</blockquote>
<div><br class="">
</div>
<div>I understand what you mean and I agree 95% in general.</div>
<div><br class="">
</div>
<div>The 5% “hmm” is the entanglement of authentication with attribute resolution, again. I think the goal was to reduce how much people need to know about LDAP in the base case, andddd here we are trying to figure out how to reduce how much people need to
know about LDAP again.</div>
<div><br class="">
</div>
<div>I don’t think the general idea of getting base cases into properties files is wrong here. I think there just needs to be a bolder line in two places:</div>
<div><br class="">
</div>
<div>1) Usage scenarios where you’re officially on your own. Documenting the assumptions briefly and explicitly in properties is probably a reasonable approximation.</div>
<div>2) Mingled XML and Spring and properties. I fault myself for not anticipating it, but it seems like people have “XML mode” and “not XML mode” in their heads, and never the two shall meet. As soon as they’re crossed, even if it looks simpler to me, it
looks like sheer mayhem to others. I have no idea how to help this other than really making the properties files really, really separate, or putting in big bold comments.</div>
<br class="">
<blockquote type="cite" class="">
<div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">I'm
not in favor of putting long notes in the files (SP used to do that, it was awful) but adding an explanatory comment about defaults is fine.</span></div>
</blockquote>
</div>
<br class="">
<div class="">Either’s fine. Even a URL would satisfy me. Just some bump that people would hit after a few hours.</div>
</body>
</html>