<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=bram" rel="nofollow">Bram Smeets</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-772?redirect=false" rel="nofollow">SPR-772</a></strong> and commented</p>
<p dir="auto">There is a problem with multiple schedulers. It is impossible to get two schedulers using the SchedulerFactoryBean. The main problem is that a NullPointerException occurs while initializing the SchedulerFactoryBean when the schedulerName property has been set.</p>
<p dir="auto">More information:<br>
<a href="http://forum.springframework.org/viewtopic.php?t=3089" rel="nofollow">http://forum.springframework.org/viewtopic.php?t=3089</a></p>
<hr>
<p dir="auto"><strong>Affects:</strong> 1.1.5</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="398056097" data-permission-text="Title is private" data-url="https://github.com/spring-projects/spring-framework/issues/5569" data-hovercard-type="issue" data-hovercard-url="/spring-projects/spring-framework/issues/5569/hovercard" href="https://github.com/spring-projects/spring-framework/issues/5569">#5569</a> quartz scheduler factory cannot produce multiple schedulers (<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="398228423" data-permission-text="Title is private" data-url="https://github.com/spring-projects/spring-framework/issues/21423" data-hovercard-type="issue" data-hovercard-url="/spring-projects/spring-framework/issues/21423/hovercard" href="https://github.com/spring-projects/spring-framework/issues/21423">#21423</a> SchedulerFactoryBean should not override explicit "org.quartz.scheduler.instanceName" setting with bean name</li>
</ul>
<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=plethora" rel="nofollow">Taras Tielkes</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-3995?redirect=false" rel="nofollow">SPR-3995</a></strong> and commented</p>
<p dir="auto">Since code is quite similar/duplicate, the issue is quite similar to <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="398080761" data-permission-text="Title is private" data-url="https://github.com/spring-projects/spring-framework/issues/8543" data-hovercard-type="issue" data-hovercard-url="/spring-projects/spring-framework/issues/8543/hovercard" href="https://github.com/spring-projects/spring-framework/issues/8543">#8543</a><br>
At the moment handler mappings are loader eagerly (see DefaultNamespaceHandlerResolver).</p>
<p dir="auto">A lazy loading implementation would perform just as well in the scenario when mappings are actually consulted.<br>
In the scenario where mappings are never used (eg. only "beans" namespace elements) this should provide a noticeable performance increase.</p>
<hr>
<p dir="auto"><strong>Affects:</strong> 2.0.7, 2.1 M4</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="398081749" data-permission-text="Title is private" data-url="https://github.com/spring-projects/spring-framework/issues/8669" data-hovercard-type="issue" data-hovercard-url="/spring-projects/spring-framework/issues/8669/hovercard" href="https://github.com/spring-projects/spring-framework/issues/8669">#8669</a> Lazy loading of NamespaceHandlers when a namespace is actually accessed</li>
</ul>