<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=matw" rel="nofollow">Mathew Wyatt</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-4054?redirect=false" rel="nofollow">SPR-4054</a></strong> and commented</p>
<p dir="auto">When i have a "prototype" (defined as prototype in the spring-config) bean which implements the ApplicationContextAware interface, it is eagerly instantiated when the application context is loaded. Which means i have a bean floating around in space which i can not get reference to. It seems poor practice to have a floating unreferenced (unreferenced by me explicitly) bean floating around?... In my case, the floating bean is throwing runtime exceptions, because of dependencies on a swing ancestor component...</p>
<p dir="auto">see post - <a href="http://forum.springframework.org/showthread.php?t=44522&amp;highlight=ApplicationContextAware" rel="nofollow">http://forum.springframework.org/showthread.php?t=44522&amp;highlight=ApplicationContextAware</a></p>
<hr>
<p dir="auto"><strong>Affects:</strong> 2.0.7</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="398082679" data-permission-text="Title is private" data-url="https://github.com/spring-projects/spring-framework/issues/8790" data-hovercard-type="issue" data-hovercard-url="/spring-projects/spring-framework/issues/8790/hovercard" href="https://github.com/spring-projects/spring-framework/issues/8790">#8790</a> ApplicationListeners cannot be lazy initialized (<em><strong>"is duplicated by"</strong></em>)</li>
<li><a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="398091587" data-permission-text="Title is private" data-url="https://github.com/spring-projects/spring-framework/issues/9921" data-hovercard-type="issue" data-hovercard-url="/spring-projects/spring-framework/issues/9921/hovercard" href="https://github.com/spring-projects/spring-framework/issues/9921">#9921</a> Prototype beans that implement ApplicationListener shouldn't be created during container initialization</li>
</ul>
<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=cert" rel="nofollow">Pavel Nemec</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-9839?redirect=false" rel="nofollow">SPR-9839</a></strong> and commented</p>
<p dir="auto">Detail description is on forum(see Reference URL)</p>
<p dir="auto">use case: Custom RequestParamMethodArgumentResolver that would parse and validate serialized object received in request parameter.</p>
<p dir="auto">found problems:<br>
1)As opposed to default resolvers, custom resolver can't obtain messageConverters in constructor, because it's created before RequestMappingHandlerAdapter that registers custom resolvers and messageConverters.</p>
<p dir="auto">2)HandlerMethodArgumentResolverComposite doesn't provide any way to place custom resolver before catch-all resolvers.</p>
<p dir="auto">3)HttpMessageConverter doesn't provide any way to get instructed to read message from parameter instead of request body.</p>
<p dir="auto">There is a workaround for all issues but one must dig in framework source code to find a solution.</p>
<hr>
<p dir="auto"><strong>Affects:</strong> 3.1.2</p>
<p dir="auto"><strong>Reference URL:</strong> <a href="http://forum.springsource.org/showthread.php?130618-Custom-HandlerMethodArgumentResolver-that-uses-messageConverters" rel="nofollow">http://forum.springsource.org/showthread.php?130618-Custom-HandlerMethodArgumentResolver-that-uses-messageConverters</a></p>