Re: [Springframework-developer] Preparing for 1.1.5

[Juergen H. <ju...@in...>]

Spring developers, everybody,

I intend to release Spring 1.1.5 this Sunday (hard deadline). We need to go
for Spring 1.2 RC1 right afterwards, releasing JMX support and Hibernate3
support, so we shouldn't lose any time. So please, test the current CVS
contents (or a current nightly snapshot) thoroughly, and refrain from
non-trivial code changes!

One area worth re-testing, for example, is JDBC/Hibernate resource
management: There have been some recent changes, in particular affecting a
combination of  DataSourceTransactionManager/HibernateTransactionManager and
TransactionAwareDataSourceProxy. Of course, it's also important to check
that typical DataSourceTransactionManager/HibernateTransactionManager usage
still works properly, not causing resource leaks in any scenario.

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of Juergen Hoeller
Sent: Wednesday, February 16, 2005 8:20 PM
To: spr...@li...
Subject: [Springframework-developer] Preparing for 1.1.5


Everybody,

I've committed lots of minor fixes and enhancements that I've implemented in
the past two weeks (most of them driven by JIRA issues). See the changelog
for details. The most important changes are:

* I've added a "getBeanNamesForType" method to the ListableBeanFactory
interface, also checking FactoryBeans and manual singletons (in contrast to
"getBeanDefinitionNames"). This is an alternative to "getBeansOfType" that
avoids creating prototype instances (assuming that all that is needed are
the names).

* TransactionSynchronization objects can influence their execution order
through implementing the Ordered interface. This is used to always perform
JDBC Connection cleanup last, for example after Hibernate Session cleanup
(if any), and to always perform LobCreator cleanup first (while the JDBC
Connection is still active).

* I've introduced the C3P0 0.8.5 ComboPooledDataSource as connection pool
for Image Database, to show an alternative to Commons DBCP. I've also added
a C3P0NativeJdbcExtractor for C3P0 0.8.5 and later; for earlier C3P0
versions, SimpleNativeJdbcExtractor is sufficient.

* I've upgraded MockHttpServletRequest to Servlet API 2.4 and
MockPageContext to JSP API 2.0. An enhancement enabled by compiling against
JSP 2.0 is that JSP EL expressions in Spring's JSP tags will be parsed with
the JSP 2.0 ExpressionEvaluator on JSP 2.0, falling back to Jakarta JSTL for
earlier JSP versions.

* I've reworked JasperReportsMultiFormatView, in particular the
initialization code. I've also renamed its "discriminatorKey" property to
"formatKey", as a more expressive name and following the
AbstractJasperReportsView naming conventions ("reportDataKey" etc).

Note that because of the upgrade to Servlet 2.4 and JSP 2.0, servlet.jar has
been replaced with servlet-api.jar and jsp-api.jar. I've also upgraded EJB
to 2.1 to raise all versions to J2EE 1.4, having replaced EJB 2.0's ejb.jar
with EJB 2.1's ejb-api.jar. I've adapted all references that I could find
(build.xml etc).

Juergen



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer