<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=bamthomas" rel="nofollow">Bruno Thomas</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-1352?redirect=false" rel="nofollow">SPR-1352</a></strong> and commented</p>
<p dir="auto">Would it be possible to add a macro in spring.vm taking into account parameters for messages. For now we defined it in another macro file with :</p>
<p dir="auto">#macro(springMessageWithArgs $code $args)$springMacroRequestContext.getMessage($code, $args)#end</p>
<hr>
<p dir="auto"><strong>Affects:</strong> 1.2.5</p>
<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=markjvickers" rel="nofollow">Mark Vickers</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-1116?redirect=false" rel="nofollow">SPR-1116</a></strong> and commented</p>
<p dir="auto">Recent change to AbstractBeanFactory getType() causes all beans of the form &lt;bean factory-method=""/&gt; to be instantiated as soon as the container encounters a bean using autowiring.</p>
<p dir="auto">This leads to an unpredictable (or at least, unexpected) order of bean instantiation.  Applications working under 1.2rc1 may fail under 1.2.2.</p>
<p dir="auto">Just want to make sure the implications of this change to the getType() method are fully thought through.  Those of us using factory-method to make legacy code amenable to IOC could have a tough time with this change.</p>
<p dir="auto">Is the run-time type returned by the factory-method really necessary here?  Couldn't we reflectively get at the return type of factory-method instead, and wouldn't that be good enough?  Or, could we not overload the class attribute of the bean?</p>
<p dir="auto">More details at:<br>
<a href="http://forum.springframework.org/viewtopic.php?t=6937" rel="nofollow">http://forum.springframework.org/viewtopic.php?t=6937</a></p>
<p dir="auto">Note: <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="398058361" data-permission-text="Title is private" data-url="https://github.com/spring-projects/spring-framework/issues/5819" data-hovercard-type="issue" data-hovercard-url="/spring-projects/spring-framework/issues/5819/hovercard" href="https://github.com/spring-projects/spring-framework/issues/5819">#5819</a> outlines a (somewhat) related concern.</p>
<hr>
<p dir="auto"><strong>Affects:</strong> 1.2.2</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="398058257" data-permission-text="Title is private" data-url="https://github.com/spring-projects/spring-framework/issues/5812" data-hovercard-type="issue" data-hovercard-url="/spring-projects/spring-framework/issues/5812/hovercard" href="https://github.com/spring-projects/spring-framework/issues/5812">#5812</a> Autoproxy problems upgrading from 1.2.1 to 1.2.2 (<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="398058495" data-permission-text="Title is private" data-url="https://github.com/spring-projects/spring-framework/issues/5833" data-hovercard-type="issue" data-hovercard-url="/spring-projects/spring-framework/issues/5833/hovercard" href="https://github.com/spring-projects/spring-framework/issues/5833">#5833</a> Property expansion broken by 1.2.2 (<em><strong>"is duplicated by"</strong></em>)</li>
</ul>