Release Notes - Red Hat Issue Tracker

Release Notes - Weld - Version 3.0.0.Alpha3 - HTML format

Configure Release Notes

Bug

[WELD-1774] - "Conversation already active" problem on tomcat when asynchronous processing
[WELD-1800] - Osgi paint example does not work
[WELD-1802] - Undertow - Weld integration issue causing threads to have invalid state

Task

[WELD-1787] - Improve event dispatching performance
[WELD-1788] - Create a test for asyc Servlet processing
[WELD-1791] - Revisit configuration
[WELD-1793] - Implement Event.fireAsync
[WELD-1801] - Make it possible to test system properties configuration during integration test run
[WELD-1807] - Consider using ForkJoinPool.commonPool() as the default executor service

Edit/Copy Release Notes

The text area below allows the project release notes to be edited and copied to another document.

Release Notes - Weld - Version 3.0.0.Alpha3
                                                            
<h2>        Bug
</h2>
<ul>
<li>[<a href='https://issues.redhat.com/browse/WELD-1774'>WELD-1774</a>] -         &quot;Conversation already active&quot; problem on tomcat when asynchronous processing
</li>
<li>[<a href='https://issues.redhat.com/browse/WELD-1800'>WELD-1800</a>] -         Osgi paint example does not work
</li>
<li>[<a href='https://issues.redhat.com/browse/WELD-1802'>WELD-1802</a>] -         Undertow - Weld integration issue causing threads to have invalid state
</li>
</ul>
    
<h2>        Task
</h2>
<ul>
<li>[<a href='https://issues.redhat.com/browse/WELD-1787'>WELD-1787</a>] -         Improve event dispatching performance
</li>
<li>[<a href='https://issues.redhat.com/browse/WELD-1788'>WELD-1788</a>] -         Create a test for asyc Servlet processing
</li>
<li>[<a href='https://issues.redhat.com/browse/WELD-1791'>WELD-1791</a>] -         Revisit configuration
</li>
<li>[<a href='https://issues.redhat.com/browse/WELD-1793'>WELD-1793</a>] -         Implement Event.fireAsync
</li>
<li>[<a href='https://issues.redhat.com/browse/WELD-1801'>WELD-1801</a>] -         Make it possible to test system properties configuration during integration test run
</li>
<li>[<a href='https://issues.redhat.com/browse/WELD-1807'>WELD-1807</a>] -         Consider using ForkJoinPool.commonPool() as the default executor service
</li>
</ul>