<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=ttimbul" rel="nofollow">Thomas Timbul</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-5199?redirect=false" rel="nofollow">SPR-5199</a></strong> and commented</p>
<p dir="auto">For the sake of clarity/modularisation in my XML I am trying to separate out certain service definitions into separate files. It would be nice to see the re-emergence of 'merge' on the util: collection definitions in a way that definitions with the same ID are merged.</p>
<p dir="auto">For example (hope this submits in a readable way):</p>
<p dir="auto">[services.xml]<br>
&lt;util:map id="serviceMap" merge="true" /&gt;<br>
&lt;bean id="serviceProvider"&gt;<br>
&lt;property name="serviceMap" ref="serviceMap" /&gt;<br>
&lt;/bean&gt;</p>
<p dir="auto">[service1.xml]<br>
&lt;util:map id="serviceMap" merge="true"&gt;<br>
&lt;entry key="S1" ref="service1" /&gt;<br>
&lt;/util:map&gt;<br>
&lt;bean id="service1" ..... /&gt;</p>
<p dir="auto">[service2.xml]<br>
&lt;util:map id="serviceMap" merge="true"&gt;<br>
&lt;entry key="S2" ref="service2" /&gt;<br>
&lt;/util:map&gt;<br>
&lt;bean id="service2" ..... /&gt;</p>
<p dir="auto">There are probably workarounds for this, but for the moment I would be forced to have the serviceMap defined completely in a single place.</p>
<hr>
<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="398100553" data-permission-text="Title is private" data-url="https://github.com/spring-projects/spring-framework/issues/11189" data-hovercard-type="issue" data-hovercard-url="/spring-projects/spring-framework/issues/11189/hovercard" href="https://github.com/spring-projects/spring-framework/issues/11189">#11189</a> Introduce 'merge' attribute for util namespace collection elements</li>
</ul>
<p dir="auto">3 votes, 2 watchers</p>
<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=dlux" rel="nofollow">Balázs Szabó</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-884?redirect=false" rel="nofollow">SPR-884</a></strong> and commented</p>
<p dir="auto">When a proxy is created with the lookup-method injection, and dependency checking is switched on, then it complains for a previously non-existing property called 'callbacks'.</p>
<p dir="auto">I figured out that it is because cglib proxies automatically implements the Factory interface which has this property exposed.</p>
<p dir="auto">To fix this, please use the latest cglib and use the setUseFactory(false) on the enhancer instance of the instantiator.</p>
<hr>
<p dir="auto"><strong>Affects:</strong> 1.2 final</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="398056515" data-permission-text="Title is private" data-url="https://github.com/spring-projects/spring-framework/issues/5616" data-hovercard-type="issue" data-hovercard-url="/spring-projects/spring-framework/issues/5616/hovercard" href="https://github.com/spring-projects/spring-framework/issues/5616">#5616</a> Dependency checking doesn't work for beans using method injection (<em><strong>"is duplicated by"</strong></em>)</li>
</ul>