<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=goonie" rel="nofollow">Andreas Schildbach</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-4368?redirect=false" rel="nofollow">SPR-4368</a></strong> and commented</p>
<p dir="auto"><code class="notranslate">@RequestMapping</code> largely takes the responsibilities of the former AbstractFormController.isFormSubmission().</p>
<p dir="auto">Unfortunately, I stumbled upon some cases that are not handled yet by <code class="notranslate">@RequestMapping</code> (well).</p>
<ol dir="auto">
<li>Mapping only matches if command object is present / not present</li>
</ol>
<p dir="auto">I use this frequently if a have a form with http-method GET (e.g. read-only search forms). In this case, I cannot distinguish by method, and I do not want to distinguish by parameter (the naming of the parameters is up to Spring Binding / Tag Library).</p>
<ol start="2" dir="auto">
<li>Mapping only matches if parameter is not present</li>
</ol>
<p dir="auto">Although not needed as urgently as 1), it would make <code class="notranslate">@RequestMappings</code> easier to formulate and a bit more robust. For example, I see some cases where you want a parameter to be present, and on the other related mapping you want the parameter to not be present.</p>
<hr>
<p dir="auto"><strong>Affects:</strong> 2.5.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="398094573" data-permission-text="Title is private" data-url="https://github.com/spring-projects/spring-framework/issues/10360" data-hovercard-type="issue" data-hovercard-url="/spring-projects/spring-framework/issues/10360/hovercard" href="https://github.com/spring-projects/spring-framework/issues/10360">#10360</a> Request header filtering in <code class="notranslate">@RequestMapping</code> (<em><strong>"duplicates"</strong></em>)</li>
</ul>
<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=msample" rel="nofollow">Mike Sample</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-1727?redirect=false" rel="nofollow">SPR-1727</a></strong> and commented</p>
<p dir="auto">Context: org.springframework.beans.*</p>
<p dir="auto">It would be nice to the ability to create PropertyTypeConverters using<br>
the same PropertyEditorRegistrySupport object as used by the<br>
ArgumentConvertingMethodInvoker.  This allows custom PropertyEditors<br>
to have access to converters without having to create duplicate<br>
PropertyEditorRegistrySupport objects. This approach would permit<br>
return values to be converted as well.</p>
<p dir="auto">A getter/setter in ArgumentConvertingMethodInvoker for the<br>
PropertyEditorRegistrySupport would solve the problem. This would also<br>
allow it to be reused in other Invokers etc.</p>
<hr>
<p dir="auto">No further details from <a href="https://jira.spring.io/browse/SPR-1727?redirect=false" rel="nofollow">SPR-1727</a></p>