<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=grzes" rel="nofollow">Grzegorz Grzybek</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-6714?redirect=false" rel="nofollow">SPR-6714</a></strong> and commented</p>
<p dir="auto">There is:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="EvaluationContext context = new StandardEvaluationContext();
context.setRootObject(tesla);"><pre class="notranslate"><code class="notranslate">EvaluationContext context = new StandardEvaluationContext();
context.setRootObject(tesla);
</code></pre></div>
<p dir="auto">but <code class="notranslate">setRootObject</code> method is undefined for interface <code class="notranslate">EvaluationContext</code>. It probably should be:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="StandardEvaluationContext context = new StandardEvaluationContext();
context.setRootObject(tesla);"><pre class="notranslate"><code class="notranslate">StandardEvaluationContext context = new StandardEvaluationContext();
context.setRootObject(tesla);
</code></pre></div>
<hr>
<p dir="auto"><strong>Affects:</strong> 3.0 GA</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="398101606" data-permission-text="Title is private" data-url="https://github.com/spring-projects/spring-framework/issues/11318" data-hovercard-type="issue" data-hovercard-url="/spring-projects/spring-framework/issues/11318/hovercard" href="https://github.com/spring-projects/spring-framework/issues/11318">#11318</a> Bug in SpEL documentation (<em><strong>"duplicates"</strong></em>)</li>
</ul>
<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=aclement" rel="nofollow">Andy Clement</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-6831?redirect=false" rel="nofollow">SPR-6831</a></strong> and commented</p>
<p dir="auto">Spin off from <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="398102268" data-permission-text="Title is private" data-url="https://github.com/spring-projects/spring-framework/issues/11411" data-hovercard-type="issue" data-hovercard-url="/spring-projects/spring-framework/issues/11411/hovercard" href="https://github.com/spring-projects/spring-framework/issues/11411">#11411</a>.  As described there:</p>
<p dir="auto">Although Keiths test now passes, more work is needed in ReflectivePropertyAccessor for a few reasons, but I wouldn't do that so close to a release:</p>
<ul dir="auto">
<li>too much duplication in there and its messy</li>
<li>the typeDescriptorCache looks unnecessary</li>
<li>BeanTypeDescriptors are built separately for property reads and property writes. I did not want to switch to letting the PropertyDescriptor discover setters/getters (with limited time until release) and I didn't want to introduce the new cost of reflectively hunting for the opposing accessor when it may not be used (so hunting for the setter when a field is being read, just so the BeanTypeDescriptor would be fully populated). This means that metadata attached to the 'other accessor' may not make it through to the conversion. So if you annotate the setter, it wont (I dont think) affect the conversion service call for a property read. And if you annotate the getter, it wont affect the conversion service call for a property write. More thought and testing required here. Keith can probably knock up a test that shows this limitation - I'll need to discuss it with him how much of a likely real world issue it is.</li>
</ul>
<p dir="auto">This Jira is to cover the work to address that.</p>
<hr>
<p dir="auto"><strong>Affects:</strong> 3.0 GA</p>