<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=patrickmcmichael" rel="nofollow">Patrick W. McMichael</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-2196?redirect=false" rel="nofollow">SPR-2196</a></strong> and commented</p>
<p dir="auto">In straight MVC (no WebFlow), there is a referenceData method that gets<br>
called when hitting a SimpleFormController in GET mode.  This is very useful<br>
for things like pulldown contents on a search form, etc.</p>
<p dir="auto">However, this method does not get called in POST mode.  When your success page is different than<br>
the search page this presents no problem.  However, if you want the search results to<br>
show up in a table below the search form, for example, the onSubmit method<br>
would need to do some duplicate calls for that pulldown data, as the form only knows which value in the<br>
pulldown was submitted.  We could just have referenceData and onSubmit both delegate<br>
to the same helper method, and then onSubmit would manually add the pulldown<br>
contents to the returned model.  What would be really nice would to be able to<br>
control whether or not referenceData was needed in POST mode.</p>
<hr>
<p dir="auto"><strong>Affects:</strong> 1.2.7</p>
<p dir="auto">2 votes, 3 watchers</p>
<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=paul4christ79" rel="nofollow">Paul Benedict</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-3729?redirect=false" rel="nofollow">SPR-3729</a></strong> and commented</p>
<p dir="auto">The idea that Spring JavaConfig uses Java visibility keywords to expose or hide bean references is an interesting idea. Can that also be implemented in XML?</p>
<p dir="auto">Example:<br>
&lt;bean id="myBean" class="com...MyBean" visibility="public" /&gt;</p>
<p dir="auto">I don't know what good values would be: public/private? The idea being that when multiple application contexts are combined into a parent, they cannot be seen except from within the child context. I was in a meeting with developers complaining about clashing bean names when combing files. This would help alleviate such situations.</p>
<hr>
<p dir="auto"><strong>Affects:</strong> 2.1 M3</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="398051836" data-permission-text="Title is private" data-url="https://github.com/spring-projects/spring-framework/issues/5099" data-hovercard-type="issue" data-hovercard-url="/spring-projects/spring-framework/issues/5099/hovercard" href="https://github.com/spring-projects/spring-framework/issues/5099">#5099</a> Restrict visibility of beans in app context (<em><strong>"duplicates"</strong></em>)</li>
</ul>