<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=nebhale" rel="nofollow">nebhale</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-1555?redirect=false" rel="nofollow">SPR-1555</a></strong> and commented</p>
<p dir="auto">I'd like to see support for the TestNG framework in the Spring Mocks area.  To that end, I've gone ahead and done an initial conversion using the existing AbstractSpringContextTest and it's subclasses.  As I worked on it, I felt that there was a ton of logic that would have to be duplicated in both trees and can probably be abstracted in some way.  In addition there's backwards compatibility using XBean for TestNG if you want to support pre 1.5 (non-annotation) use of TestNG.</p>
<p dir="auto">As far as the changes go, I simply removed the TestCase extension point and used annotations to get the setUp() method to run at the beginning of each test class.  In addition, I removed the tearDown() and the onSetUp() and onTearDown() methods.  TestNG guarentees that multiple 'beforeTestClass' and 'beforeTestMethod' are executed descending through the inheritence tree.  In addition, this should give users more power as they can now set dependencies of methods to guarentee order.  In addition in the Transaction classes, the creation and rollback of the transactions area listed as 'before/afterTestMethod'.</p>
<p dir="auto">I realize that this is simply a first cut and there will still need to be work done.  I'd like to see this as part of 2.0 final, but understand if it can't make it.  If you want me to redo the work with design input from you all, that'd be OK as well.</p>
<hr>
<p dir="auto"><strong>Affects:</strong> 2.0 M1</p>
<p dir="auto"><strong>Attachments:</strong></p>
<ul dir="auto">
<li><a href="https://jira.spring.io/secure/attachment/11352/AbstractDependencyInjectionSpringContextTests.java" rel="nofollow">AbstractDependencyInjectionSpringContextTests.java</a> (<em>9.88 kB</em>)</li>
<li><a href="https://jira.spring.io/secure/attachment/11351/AbstractSpringContextTests.java" rel="nofollow">AbstractSpringContextTests.java</a> (<em>4.26 kB</em>)</li>
<li><a href="https://jira.spring.io/secure/attachment/11354/AbstractTransactionalDataSourceSpringContextTests.java" rel="nofollow">AbstractTransactionalDataSourceSpringContextTests.java</a> (<em>2.69 kB</em>)</li>
<li><a href="https://jira.spring.io/secure/attachment/11353/AbstractTransactionalSpringContextTests.java" rel="nofollow">AbstractTransactionalSpringContextTests.java</a> (<em>8.14 kB</em>)</li>
</ul>
<p dir="auto">9 votes, 7 watchers</p>
<p dir="auto"><strong><a href="https://jira.spring.io/secure/ViewProfile.jspa?name=gmatthews" rel="nofollow">Greg Matthews</a></strong> opened <strong><a href="https://jira.spring.io/browse/SPR-1423?redirect=false" rel="nofollow">SPR-1423</a></strong> and commented</p>
<p dir="auto">When building a web application, you typically need to present messages to the user that can be an error, information, or warning.</p>
<p dir="auto">There is no built in support for this in Spring, other than the Errors interface.</p>
<p dir="auto">It would be good if there was built in support for:</p>
<ol dir="auto">
<li>A parameterized message level. e.g. Error, Info, Warning.</li>
<li>The ability for messages to survive a redirect (likely by storing them in session, and having the JSP page clear session state when messages are displayed). This point probably relates more the SpringWEB rather than SpringCORE because it needs to know about sessions.</li>
</ol>
<hr>
<p dir="auto"><strong>Affects:</strong> 1.2.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="398049488" data-permission-text="Title is private" data-url="https://github.com/spring-projects/spring-framework/issues/4895" data-hovercard-type="issue" data-hovercard-url="/spring-projects/spring-framework/issues/4895/hovercard" href="https://github.com/spring-projects/spring-framework/issues/4895">#4895</a> Create a notion of "Warnings" (<em><strong>"duplicates"</strong></em>)</li>
</ul>