<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=devijvers" rel="nofollow">Steven Devijver</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-599?redirect=false" rel="nofollow">SPR-599</a></strong> and commented</p>
<p dir="auto">It would be nice if the property editors registered with BeanWrapperImpl are also used on value elements in lists and maps. Right now they are handled as strings and need to be handled by the classes that receive them. This leads to boilerplate code that could be avoided.</p>
<p dir="auto">Using BeanWrapperImpl on list and map elements would be possible in my view since the destination type is Object. No default editors are registered for Object so none of them would be picked. This would allow users to register a custom editor for Object that would inject other types than strings.</p>
<p dir="auto">Registering a custom editor with Object doesn't interfere with normal property handling as the default editors come first in the list.</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="398053423" data-permission-text="Title is private" data-url="https://github.com/spring-projects/spring-framework/issues/5271" data-hovercard-type="issue" data-hovercard-url="/spring-projects/spring-framework/issues/5271/hovercard" href="https://github.com/spring-projects/spring-framework/issues/5271">#5271</a> Property editors support for indexed and mapped properties (<em><strong>"duplicates"</strong></em>)</li>
</ul>
<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=memelet" rel="nofollow">Barry Kaplan</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-2275?redirect=false" rel="nofollow">SPR-2275</a></strong> and commented</p>
<p dir="auto">AbstractTransactionalSpringContextTests has no onSetup* hook for test methods marked as <code class="notranslate">@NotTransactional</code>. The onSetup methods only invokes onSetupBeforeTransaction if the transactionDefinition is not null. And since the AbstractTransactionalSpringContextTests.onSetup is set to be final, there is no way to add in any type of additional setup hooks.</p>
<p dir="auto">Maybe onSetup/TeardownBeforeNonTransaction()?</p>
<hr>
<p dir="auto"><strong>Affects:</strong> 2.0 RC2</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="398077335" data-permission-text="Title is private" data-url="https://github.com/spring-projects/spring-framework/issues/8081" data-hovercard-type="issue" data-hovercard-url="/spring-projects/spring-framework/issues/8081/hovercard" href="https://github.com/spring-projects/spring-framework/issues/8081">#8081</a> AbstractTransactionalSpringContextTests shoud still call onSetupBeforeTransaction if transactions are prevented (<em><strong>"is duplicated by"</strong></em>)</li>
</ul>
<p dir="auto">1 votes, 1 watchers</p>