<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=marcelstoer" rel="nofollow">Marcel Stör</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-9722?redirect=false" rel="nofollow">SPR-9722</a></strong> and commented</p>
<p dir="auto">With <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="398088112" data-permission-text="Title is private" data-url="https://github.com/spring-projects/spring-framework/issues/9462" data-hovercard-type="issue" data-hovercard-url="/spring-projects/spring-framework/issues/9462/hovercard" href="https://github.com/spring-projects/spring-framework/issues/9462">#9462</a> support for default values was added.</p>
<p dir="auto">However, I observed that they are applied too early if you have a hierarchy or cascade of property placeholder configurers:</p>
<ul dir="auto">
<li>Spring loops through the prioritized list of configurers</li>
<li>if property X is not found in the first configurer the default value is returned<br>
--&gt; the whole list should be processed first before the default value is used</li>
</ul>
<hr>
<p dir="auto"><strong>Affects:</strong> 3.1.1</p>
<p dir="auto"><strong>Issue Links:</strong></p>
<ul dir="auto">
<li><a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="398152264" data-permission-text="Title is private" data-url="https://github.com/spring-projects/spring-framework/issues/14292" data-hovercard-type="issue" data-hovercard-url="/spring-projects/spring-framework/issues/14292/hovercard" href="https://github.com/spring-projects/spring-framework/issues/14292">#14292</a> <code class="notranslate">@Value</code> assigns the default property value (if specified) before all property locations are examined, resulting in assigning a default to a property which is defined in a properties file. (<em><strong>"is duplicated by"</strong></em>)</li>
</ul>
<p dir="auto">1 votes, 3 watchers</p>
<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=ziezi" rel="nofollow">Lachezar Kozhuharov</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-9474?redirect=false" rel="nofollow">SPR-9474</a></strong> and commented</p>
<p dir="auto">I would expect the matching pattern not to partially enforce the query structure. Expected behavior is to fully enforce it or not to enforce it at all. This would be useful when for example building a RESTful service client. A query like "a=b&amp;filter=c==d" is not properly processed and results in URI change.</p>
<hr>
<p dir="auto"><strong>Affects:</strong> 3.1 RC2</p>
<p dir="auto"><strong>Issue Links:</strong></p>
<ul dir="auto">
<li><a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="398153675" data-permission-text="Title is private" data-url="https://github.com/spring-projects/spring-framework/issues/14465" data-hovercard-type="issue" data-hovercard-url="/spring-projects/spring-framework/issues/14465/hovercard" href="https://github.com/spring-projects/spring-framework/issues/14465">#14465</a> Erroneous "0" returned where empty string expected in call through the RestTemplate (<em><strong>"duplicates"</strong></em>)</li>
</ul>
<p dir="auto"><strong>Referenced from:</strong> commits <a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/spring-projects/spring-framework/commit/2965df6bee12638e3e1a1208c382679fe3d46751/hovercard" href="https://github.com/spring-projects/spring-framework/commit/2965df6bee12638e3e1a1208c382679fe3d46751"><tt>2965df6</tt></a></p>