You can subscribe to this list here.
| 2003 |
Jan
|
Feb
(55) |
Mar
(100) |
Apr
(203) |
May
(330) |
Jun
(190) |
Jul
(302) |
Aug
(323) |
Sep
(197) |
Oct
(245) |
Nov
(490) |
Dec
(330) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(194) |
Feb
(400) |
Mar
(416) |
Apr
(415) |
May
(359) |
Jun
(381) |
Jul
(491) |
Aug
(311) |
Sep
(291) |
Oct
(273) |
Nov
(355) |
Dec
(266) |
| 2005 |
Jan
(306) |
Feb
(303) |
Mar
(520) |
Apr
(346) |
May
(255) |
Jun
(221) |
Jul
(171) |
Aug
(247) |
Sep
(147) |
Oct
(125) |
Nov
(165) |
Dec
(65) |
| 2006 |
Jan
(90) |
Feb
(53) |
Mar
(121) |
Apr
(103) |
May
(113) |
Jun
(103) |
Jul
(104) |
Aug
(67) |
Sep
(78) |
Oct
(82) |
Nov
(78) |
Dec
(70) |
| 2007 |
Jan
(77) |
Feb
(76) |
Mar
(63) |
Apr
(30) |
May
(47) |
Jun
(41) |
Jul
(44) |
Aug
(44) |
Sep
(49) |
Oct
(33) |
Nov
(25) |
Dec
(21) |
| 2008 |
Jan
(45) |
Feb
(13) |
Mar
(15) |
Apr
(12) |
May
(9) |
Jun
(33) |
Jul
(30) |
Aug
(7) |
Sep
(20) |
Oct
(17) |
Nov
(20) |
Dec
(10) |
| 2009 |
Jan
(8) |
Feb
(5) |
Mar
(12) |
Apr
(17) |
May
(19) |
Jun
(97) |
Jul
(77) |
Aug
(33) |
Sep
(24) |
Oct
(41) |
Nov
(16) |
Dec
(32) |
| 2010 |
Jan
(24) |
Feb
(14) |
Mar
(50) |
Apr
(71) |
May
(70) |
Jun
(64) |
Jul
(45) |
Aug
(62) |
Sep
(32) |
Oct
(4) |
Nov
(12) |
Dec
(2) |
| 2011 |
Jan
(1) |
Feb
(3) |
Mar
(4) |
Apr
(3) |
May
(6) |
Jun
(1) |
Jul
(4) |
Aug
(3) |
Sep
(4) |
Oct
(6) |
Nov
(3) |
Dec
(3) |
| 2012 |
Jan
(4) |
Feb
(8) |
Mar
(6) |
Apr
(10) |
May
(2) |
Jun
(3) |
Jul
(11) |
Aug
(10) |
Sep
(4) |
Oct
|
Nov
(1) |
Dec
(1) |
| 2013 |
Jan
(4) |
Feb
(1) |
Mar
(9) |
Apr
(1) |
May
(8) |
Jun
(2) |
Jul
(5) |
Aug
(2) |
Sep
|
Oct
(3) |
Nov
(10) |
Dec
(8) |
| 2014 |
Jan
(3) |
Feb
(12) |
Mar
(9) |
Apr
(12) |
May
(2) |
Jun
|
Jul
(3) |
Aug
(1) |
Sep
(1) |
Oct
(4) |
Nov
|
Dec
(2) |
| 2015 |
Jan
(1) |
Feb
(3) |
Mar
(4) |
Apr
(9) |
May
(2) |
Jun
(2) |
Jul
|
Aug
(2) |
Sep
(7) |
Oct
(9) |
Nov
(7) |
Dec
(9) |
| 2016 |
Jan
(7) |
Feb
(5) |
Mar
(5) |
Apr
(5) |
May
(8) |
Jun
(4) |
Jul
(5) |
Aug
(4) |
Sep
(6) |
Oct
(7) |
Nov
(2) |
Dec
(3) |
| 2017 |
Jan
(7) |
Feb
(8) |
Mar
(7) |
Apr
(3) |
May
(4) |
Jun
(3) |
Jul
(5) |
Aug
(8) |
Sep
(4) |
Oct
(2) |
Nov
(3) |
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2019 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2021 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
(5) |
Sep
(2) |
Oct
|
Nov
|
Dec
(1) |
| 2026 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Darren D. <da...@da...> - 2004-03-25 01:09:58
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 25 March 2004 00:19, j=FCrgen h=F6ller [werk3AT] wrote: > ***** Look outside, Spring is here! ***** > (for the northern hemisphere, at least ;-) Great effort Juergen - well done, and thanks! I've posted a brief announcement to comp.lang.java.programmer (but my ISP=20 chose tonight to have their NNTP server go belly up, so it may take a while= =20 to appear) Cheers, =2D --=20 Darren Davison Public Key: http://www.davison.uk.net/key.jsp =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAYjFgKLMLAN01aw0RAjRfAJ9eQq9sdzouaYRfMA5ROVatXYqRdgCghhx2 asbfcqvxmRnOYUqJAIB9/bo=3D =3Dn7gS =2D----END PGP SIGNATURE----- |
|
From: <zh...@ne...> - 2004-03-25 00:52:05
|
Congratulations! Thanks all! I have posted the good news on Chinese Spring Framework forum. Regards, Zheng Ye >***** Look outside, Spring is here! ***** >(for the northern hemisphere, at least ;-) > > >Dear Spring community, > >I'm pleased to announce that Spring Framework 1.0 final has just been released. Thanks to all contributors and early adopters that have followed our 1.0 milestones and release candidates: Spring wouldn't be as mature as it is without you! > > >1. SCOPE > >Spring 1.0 is a complete Java/J2EE application framework, covering the following functionality: > >* the most sophisticated lightweight container available today, with various flavors of setter and constructor injection >* AOP interception framework based on the AOP Alliance interfaces, integrated with the core container >* JNDI support classes, allowing for easy wiring of Spring-managed beans with JNDI-located objects >* application context concept, providing resource loading and message access abstractions >* generic transaction management with pluggable strategies, supporting declarative and programmatic demarcation >* support for source-level metadata, with Commons Attributes as default implementation (e.g. for transaction attributes) >* generic DAO support, providing a generic data access exception hierarchy for use with any data access strategy >* JDBC abstraction that simplifies resource and error handling, also covering BLOB/CLOB support >* Hibernate support, providing SessionFactory management and transaction-scoped ThreadLocal Sessions >* support classes for JDO 1.0 and iBATIS SQL Maps 1.3/2.0, integrated with Spring's transaction management >* mail sender abstraction, with special support for JavaMail including convenient handling of file attachments >* scheduling support for Quartz and Timer, making it easy to invoke methods of Spring-managed beans >* remoting support for RMI, JAX-RPC and Caucho's Hessian/Burlap, for easy exposure of Spring-managed beans >* convenience classes for accessing and implementing EJBs, both local and remote >* web application context, for loading a Spring application context in a web environment >* flexible web MVC framework, built on strategy interfaces and integrated with various view technologies > >A unique benefit of Spring is the ability to apply declarative transactions to any POJO, with JTA or a local transaction strategy: This allows to have lightweight transactional business objects in any sort of environment, for example in a web app running on plain Tomcat. Spring's transaction management is also capable of managing associated resources like Hibernate Sessions, avoiding the burden of custom ThreadLocal Sessions. > >Building on the resource management infrastructure, Spring's HibernateTemplate significantly simplifies the implementation of Hibernate-based DAOs, reducing typical data access operations to single statements. A similar level of convenience is available for JDBC in the form of Spring's JdbcTemplate, and for iBATIS SQL Maps 1.3/2.0 in the form of SqlMapTemplate respectively SqlMapClientTemplate. > >An important characteristic of Spring is that many of its features can be used individually, without the need to adopt an architecture that's completely based on Spring. Furthermore, a Spring-managed middle tier and all the functionality it provides can be reused in any sort of environment, be it a J2EE web application with a Spring web MVC, Struts, WebWork or Tapestry web tier, or a standalone application with a Swing user interface. > > >2. SAMPLES AND USAGES > >The Spring distribution comes with numerous sample applications. The "-with-dependencies" download includes all third-party libraries that are necessary for building an running them. > >* our JPetStore, adapting the iBATIS JPetStore with a Spring-managed middle tier and alternative Spring/Struts web tiers >* Petclinic, a simple database-driven web application that offers alternative Hibernate/JDBC data access strategies >* Countries, a web app that illustrates locale and theme handling, and the generation of PDF and Excel web views >* Image Database, a one-screen web app that illustrates BLOB/CLOB handling and Velocity/FreeMarker web views >* Tiles Example, demonstrating the use of Tiles with Spring's web MVC framework > >Spring is already used in a significant number of production applications, including mission-critical applications. Current adopters include a number of large banks and health care organizations in Europe and the US. Noteworthy usages of Spring in publically visible applications are: > >* Matt Raible's AppFuse (http://raibledesigns.com/wiki/Wiki.jsp?page=AppFuse) application skeleton, adopting Spring as middle tier framework with a Struts web tier >* Atlassian's new product Confluence (http://www.atlassian.com/software/confluence), built on a Spring middle tier and a WebWork2 web tier > > >3. UPGRADING > >Users upgrading from a Spring 1.0 milestone or release candidate, please see the changelog; there have been quite a few refinements in the details. Among the changes since 1.0 RC2 are: > >* AOP support upgraded to AOP Alliance 1.0 >* more sophisticated handling of indexed and mapped properties in BeanWrapperImpl >* new ResourceLoader interface, extended by the ApplicationContext interface >* ReloadableResourceBundleMessage supports configurable character encodings >* MimeMessageHelper supports configurable character encodings >* JdbcTemplate has new generic "execute" methods and refined "query" methods >* iBATIS SQL Maps 2.0 support upgraded to SQL Maps 2.0 RC1 >* added support for FreeMarker 2.3 > >Please note the following upgrade issues with respect to the AOP support: > >* you have to update your aopalliance.jar >* AdvisorAutoProxyCreator was renamed to DefaultAdvisorAutoProxyCreator >* TransactionAttributeSourceTransactionAroundAdvisor was renamed to TransactionAttributeSourceAdvisor >* custom Advisor implementations: getAdvice() now returns org.aopalliance.aop.Advice rather than Object >* if you implemented org.springframework.aop.MethodAfterReturningAdvice, replace with AfterReturningAdvice (no change in method signature) > > >Regards, > >Juergen |
|
From: Ross M. <ro...@at...> - 2004-03-25 00:47:38
|
Well done guys! j=FCrgen h=F6ller [werk3AT] wrote: > ***** Look outside, Spring is here! ***** > (for the northern hemisphere, at least ;-) > =20 > =20 > Dear Spring community, > =20 > I'm pleased to announce that Spring Framework 1.0 final has just been r= eleased. Thanks to all contributors and early adopters that have followed= our 1.0 milestones and release candidates: Spring wouldn't be as mature = as it is without you! > =20 > =20 > 1. SCOPE > =20 > Spring 1.0 is a complete Java/J2EE application framework, covering the = following functionality: > =20 > * the most sophisticated lightweight container available today, with va= rious flavors of setter and constructor injection > * AOP interception framework based on the AOP Alliance interfaces, inte= grated with the core container > * JNDI support classes, allowing for easy wiring of Spring-managed bean= s with JNDI-located objects > * application context concept, providing resource loading and message a= ccess abstractions > * generic transaction management with pluggable strategies, supporting = declarative and programmatic demarcation > * support for source-level metadata, with Commons Attributes as default= implementation (e.g. for transaction attributes) > * generic DAO support, providing a generic data access exception hierar= chy for use with any data access strategy > * JDBC abstraction that simplifies resource and error handling, also co= vering BLOB/CLOB support > * Hibernate support, providing SessionFactory management and transactio= n-scoped ThreadLocal Sessions > * support classes for JDO 1.0 and iBATIS SQL Maps 1.3/2.0, integrated w= ith Spring's transaction management > * mail sender abstraction, with special support for JavaMail including = convenient handling of file attachments > * scheduling support for Quartz and Timer, making it easy to invoke met= hods of Spring-managed beans > * remoting support for RMI, JAX-RPC and Caucho's Hessian/Burlap, for ea= sy exposure of Spring-managed beans > * convenience classes for accessing and implementing EJBs, both local a= nd remote > * web application context, for loading a Spring application context in = a web environment > * flexible web MVC framework, built on strategy interfaces and integrat= ed with various view technologies > =20 > A unique benefit of Spring is the ability to apply declarative transact= ions to any POJO, with JTA or a local transaction strategy: This allows t= o have lightweight transactional business objects in any sort of environm= ent, for example in a web app running on plain Tomcat. Spring's transacti= on management is also capable of managing associated resources like Hiber= nate Sessions, avoiding the burden of custom ThreadLocal Sessions. > =20 > Building on the resource management infrastructure, Spring's HibernateT= emplate significantly simplifies the implementation of Hibernate-based DA= Os, reducing typical data access operations to single statements. A simil= ar level of convenience is available for JDBC in the form of Spring's Jdb= cTemplate, and for iBATIS SQL Maps 1.3/2.0 in the form of SqlMapTemplate = respectively SqlMapClientTemplate. > =20 > An important characteristic of Spring is that many of its features can = be used individually, without the need to adopt an architecture that's co= mpletely based on Spring. Furthermore, a Spring-managed middle tier and a= ll the functionality it provides can be reused in any sort of environment= , be it a J2EE web application with a Spring web MVC, Struts, WebWork or = Tapestry web tier, or a standalone application with a Swing user interfac= e. > =20 > =20 > 2. SAMPLES AND USAGES > =20 > The Spring distribution comes with numerous sample applications. The "-= with-dependencies" download includes all third-party libraries that are n= ecessary for building an running them. > =20 > * our JPetStore, adapting the iBATIS JPetStore with a Spring-managed mi= ddle tier and alternative Spring/Struts web tiers > * Petclinic, a simple database-driven web application that offers alter= native Hibernate/JDBC data access strategies > * Countries, a web app that illustrates locale and theme handling, and = the generation of PDF and Excel web views > * Image Database, a one-screen web app that illustrates BLOB/CLOB handl= ing and Velocity/FreeMarker web views > * Tiles Example, demonstrating the use of Tiles with Spring's web MVC f= ramework > =20 > Spring is already used in a significant number of production applicatio= ns, including mission-critical applications. Current adopters include a n= umber of large banks and health care organizations in Europe and the US. = Noteworthy usages of Spring in publically visible applications are: > =20 > * Matt Raible's AppFuse (http://raibledesigns.com/wiki/Wiki.jsp?page=3D= AppFuse) application skeleton, adopting Spring as middle tier framework w= ith a Struts web tier > * Atlassian's new product Confluence (http://www.atlassian.com/software= /confluence), built on a Spring middle tier and a WebWork2 web tier > =20 > =20 > 3. UPGRADING > =20 > Users upgrading from a Spring 1.0 milestone or release candidate, pleas= e see the changelog; there have been quite a few refinements in the detai= ls. Among the changes since 1.0 RC2 are: > =20 > * AOP support upgraded to AOP Alliance 1.0 > * more sophisticated handling of indexed and mapped properties in BeanW= rapperImpl > * new ResourceLoader interface, extended by the ApplicationContext inte= rface > * ReloadableResourceBundleMessage supports configurable character encod= ings > * MimeMessageHelper supports configurable character encodings > * JdbcTemplate has new generic "execute" methods and refined "query" me= thods > * iBATIS SQL Maps 2.0 support upgraded to SQL Maps 2.0 RC1 > * added support for FreeMarker 2.3 > =20 > Please note the following upgrade issues with respect to the AOP suppor= t: > =20 > * you have to update your aopalliance.jar > * AdvisorAutoProxyCreator was renamed to DefaultAdvisorAutoProxyCreator > * TransactionAttributeSourceTransactionAroundAdvisor was renamed to Tra= nsactionAttributeSourceAdvisor > * custom Advisor implementations: getAdvice() now returns org.aopallian= ce.aop.Advice rather than Object > * if you implemented org.springframework.aop.MethodAfterReturningAdvice= , replace with AfterReturningAdvice (no change in method signature) >=20 > =20 > Regards, > =20 > Juergen > =20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=CCk > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer >=20 |
|
From: Thomas R. <tho...@tr...> - 2004-03-25 00:43:25
|
Juergen, Thanks! You deserve at least a day off :-) I have posted the news on the website. I will also post all the other files that have been updated. Thomas jürgen höller [werk3AT] wrote: >***** Look outside, Spring is here! ***** >(for the northern hemisphere, at least ;-) > > >Dear Spring community, > >I'm pleased to announce that Spring Framework 1.0 final has just been released. Thanks to all contributors and early adopters that have followed our 1.0 milestones and release candidates: Spring wouldn't be as mature as it is without you! > > >1. SCOPE > >Spring 1.0 is a complete Java/J2EE application framework, covering the following functionality: > >* the most sophisticated lightweight container available today, with various flavors of setter and constructor injection >* AOP interception framework based on the AOP Alliance interfaces, integrated with the core container >* JNDI support classes, allowing for easy wiring of Spring-managed beans with JNDI-located objects >* application context concept, providing resource loading and message access abstractions >* generic transaction management with pluggable strategies, supporting declarative and programmatic demarcation >* support for source-level metadata, with Commons Attributes as default implementation (e.g. for transaction attributes) >* generic DAO support, providing a generic data access exception hierarchy for use with any data access strategy >* JDBC abstraction that simplifies resource and error handling, also covering BLOB/CLOB support >* Hibernate support, providing SessionFactory management and transaction-scoped ThreadLocal Sessions >* support classes for JDO 1.0 and iBATIS SQL Maps 1.3/2.0, integrated with Spring's transaction management >* mail sender abstraction, with special support for JavaMail including convenient handling of file attachments >* scheduling support for Quartz and Timer, making it easy to invoke methods of Spring-managed beans >* remoting support for RMI, JAX-RPC and Caucho's Hessian/Burlap, for easy exposure of Spring-managed beans >* convenience classes for accessing and implementing EJBs, both local and remote >* web application context, for loading a Spring application context in a web environment >* flexible web MVC framework, built on strategy interfaces and integrated with various view technologies > >A unique benefit of Spring is the ability to apply declarative transactions to any POJO, with JTA or a local transaction strategy: This allows to have lightweight transactional business objects in any sort of environment, for example in a web app running on plain Tomcat. Spring's transaction management is also capable of managing associated resources like Hibernate Sessions, avoiding the burden of custom ThreadLocal Sessions. > >Building on the resource management infrastructure, Spring's HibernateTemplate significantly simplifies the implementation of Hibernate-based DAOs, reducing typical data access operations to single statements. A similar level of convenience is available for JDBC in the form of Spring's JdbcTemplate, and for iBATIS SQL Maps 1.3/2.0 in the form of SqlMapTemplate respectively SqlMapClientTemplate. > >An important characteristic of Spring is that many of its features can be used individually, without the need to adopt an architecture that's completely based on Spring. Furthermore, a Spring-managed middle tier and all the functionality it provides can be reused in any sort of environment, be it a J2EE web application with a Spring web MVC, Struts, WebWork or Tapestry web tier, or a standalone application with a Swing user interface. > > >2. SAMPLES AND USAGES > >The Spring distribution comes with numerous sample applications. The "-with-dependencies" download includes all third-party libraries that are necessary for building an running them. > >* our JPetStore, adapting the iBATIS JPetStore with a Spring-managed middle tier and alternative Spring/Struts web tiers >* Petclinic, a simple database-driven web application that offers alternative Hibernate/JDBC data access strategies >* Countries, a web app that illustrates locale and theme handling, and the generation of PDF and Excel web views >* Image Database, a one-screen web app that illustrates BLOB/CLOB handling and Velocity/FreeMarker web views >* Tiles Example, demonstrating the use of Tiles with Spring's web MVC framework > >Spring is already used in a significant number of production applications, including mission-critical applications. Current adopters include a number of large banks and health care organizations in Europe and the US. Noteworthy usages of Spring in publically visible applications are: > >* Matt Raible's AppFuse (http://raibledesigns.com/wiki/Wiki.jsp?page=AppFuse) application skeleton, adopting Spring as middle tier framework with a Struts web tier >* Atlassian's new product Confluence (http://www.atlassian.com/software/confluence), built on a Spring middle tier and a WebWork2 web tier > > >3. UPGRADING > >Users upgrading from a Spring 1.0 milestone or release candidate, please see the changelog; there have been quite a few refinements in the details. Among the changes since 1.0 RC2 are: > >* AOP support upgraded to AOP Alliance 1.0 >* more sophisticated handling of indexed and mapped properties in BeanWrapperImpl >* new ResourceLoader interface, extended by the ApplicationContext interface >* ReloadableResourceBundleMessage supports configurable character encodings >* MimeMessageHelper supports configurable character encodings >* JdbcTemplate has new generic "execute" methods and refined "query" methods >* iBATIS SQL Maps 2.0 support upgraded to SQL Maps 2.0 RC1 >* added support for FreeMarker 2.3 > >Please note the following upgrade issues with respect to the AOP support: > >* you have to update your aopalliance.jar >* AdvisorAutoProxyCreator was renamed to DefaultAdvisorAutoProxyCreator >* TransactionAttributeSourceTransactionAroundAdvisor was renamed to TransactionAttributeSourceAdvisor >* custom Advisor implementations: getAdvice() now returns org.aopalliance.aop.Advice rather than Object >* if you implemented org.springframework.aop.MethodAfterReturningAdvice, replace with AfterReturningAdvice (no change in method signature) > > >Regards, > >Juergen > > > >------------------------------------------------------- >This SF.Net email is sponsored by: IBM Linux Tutorials >Free Linux tutorial presented by Daniel Robbins, President and CEO of >GenToo technologies. Learn everything from fundamentals to system >administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > > |
|
From: <jue...@we...> - 2004-03-25 00:21:18
|
***** Look outside, Spring is here! ***** (for the northern hemisphere, at least ;-) =20 =20 Dear Spring community, =20 I'm pleased to announce that Spring Framework 1.0 final has just been = released. Thanks to all contributors and early adopters that have = followed our 1.0 milestones and release candidates: Spring wouldn't be = as mature as it is without you! =20 =20 1. SCOPE =20 Spring 1.0 is a complete Java/J2EE application framework, covering the = following functionality: =20 * the most sophisticated lightweight container available today, with = various flavors of setter and constructor injection * AOP interception framework based on the AOP Alliance interfaces, = integrated with the core container * JNDI support classes, allowing for easy wiring of Spring-managed beans = with JNDI-located objects * application context concept, providing resource loading and message = access abstractions * generic transaction management with pluggable strategies, supporting = declarative and programmatic demarcation * support for source-level metadata, with Commons Attributes as default = implementation (e.g. for transaction attributes) * generic DAO support, providing a generic data access exception = hierarchy for use with any data access strategy * JDBC abstraction that simplifies resource and error handling, also = covering BLOB/CLOB support * Hibernate support, providing SessionFactory management and = transaction-scoped ThreadLocal Sessions * support classes for JDO 1.0 and iBATIS SQL Maps 1.3/2.0, integrated = with Spring's transaction management * mail sender abstraction, with special support for JavaMail including = convenient handling of file attachments * scheduling support for Quartz and Timer, making it easy to invoke = methods of Spring-managed beans * remoting support for RMI, JAX-RPC and Caucho's Hessian/Burlap, for = easy exposure of Spring-managed beans * convenience classes for accessing and implementing EJBs, both local = and remote * web application context, for loading a Spring application context in a = web environment * flexible web MVC framework, built on strategy interfaces and = integrated with various view technologies =20 A unique benefit of Spring is the ability to apply declarative = transactions to any POJO, with JTA or a local transaction strategy: This = allows to have lightweight transactional business objects in any sort of = environment, for example in a web app running on plain Tomcat. Spring's = transaction management is also capable of managing associated resources = like Hibernate Sessions, avoiding the burden of custom ThreadLocal = Sessions. =20 Building on the resource management infrastructure, Spring's = HibernateTemplate significantly simplifies the implementation of = Hibernate-based DAOs, reducing typical data access operations to single = statements. A similar level of convenience is available for JDBC in the = form of Spring's JdbcTemplate, and for iBATIS SQL Maps 1.3/2.0 in the = form of SqlMapTemplate respectively SqlMapClientTemplate. =20 An important characteristic of Spring is that many of its features can = be used individually, without the need to adopt an architecture that's = completely based on Spring. Furthermore, a Spring-managed middle tier = and all the functionality it provides can be reused in any sort of = environment, be it a J2EE web application with a Spring web MVC, Struts, = WebWork or Tapestry web tier, or a standalone application with a Swing = user interface. =20 =20 2. SAMPLES AND USAGES =20 The Spring distribution comes with numerous sample applications. The = "-with-dependencies" download includes all third-party libraries that = are necessary for building an running them. =20 * our JPetStore, adapting the iBATIS JPetStore with a Spring-managed = middle tier and alternative Spring/Struts web tiers * Petclinic, a simple database-driven web application that offers = alternative Hibernate/JDBC data access strategies * Countries, a web app that illustrates locale and theme handling, and = the generation of PDF and Excel web views * Image Database, a one-screen web app that illustrates BLOB/CLOB = handling and Velocity/FreeMarker web views * Tiles Example, demonstrating the use of Tiles with Spring's web MVC = framework =20 Spring is already used in a significant number of production = applications, including mission-critical applications. Current adopters = include a number of large banks and health care organizations in Europe = and the US. Noteworthy usages of Spring in publically visible = applications are: =20 * Matt Raible's AppFuse = (http://raibledesigns.com/wiki/Wiki.jsp?page=3DAppFuse) application = skeleton, adopting Spring as middle tier framework with a Struts web = tier * Atlassian's new product Confluence = (http://www.atlassian.com/software/confluence), built on a Spring middle = tier and a WebWork2 web tier =20 =20 3. UPGRADING =20 Users upgrading from a Spring 1.0 milestone or release candidate, please = see the changelog; there have been quite a few refinements in the = details. Among the changes since 1.0 RC2 are: =20 * AOP support upgraded to AOP Alliance 1.0 * more sophisticated handling of indexed and mapped properties in = BeanWrapperImpl * new ResourceLoader interface, extended by the ApplicationContext = interface * ReloadableResourceBundleMessage supports configurable character = encodings * MimeMessageHelper supports configurable character encodings * JdbcTemplate has new generic "execute" methods and refined "query" = methods * iBATIS SQL Maps 2.0 support upgraded to SQL Maps 2.0 RC1 * added support for FreeMarker 2.3 =20 Please note the following upgrade issues with respect to the AOP = support: =20 * you have to update your aopalliance.jar * AdvisorAutoProxyCreator was renamed to DefaultAdvisorAutoProxyCreator * TransactionAttributeSourceTransactionAroundAdvisor was renamed to = TransactionAttributeSourceAdvisor * custom Advisor implementations: getAdvice() now returns = org.aopalliance.aop.Advice rather than Object * if you implemented org.springframework.aop.MethodAfterReturningAdvice, = replace with AfterReturningAdvice (no change in method signature) =20 Regards, =20 Juergen =20 |
|
From: Ou, R. <Ro...@sa...> - 2004-03-24 16:46:08
|
+1 =20 We do this for our project... =20 Rong -----Original Message----- From: spr...@li... = [mailto:spr...@li...]On Behalf = Of Cameron Braid Sent: Tuesday, March 23, 2004 9:22 PM To: spr...@li... Subject: [Springframework-developer] JARs .. can they be named based on = their version ? I have run into a problem with supporting multiple applications that use = different spring versions. =20 We store all of our jars, for every application, in a repository. =20 In eclipse we link against them, and when deploying we copy them into = the war/ear. =20 I upgraded an app to spring 1.0 HEAD yesterday, causing the new = aopalliance.jar to be overwritten in our repository. =20 I now receive an aopalliance exception because an app, using spring rc1, = requres the older aopalliance.jar file. =20 This issue would be avoided if every jar that spring uses (including the = spring generated jars) are stamped with their version in the filename. =20 I (and others) managed to convince Hibernate, WebWork2 and Xwork to = follow this pattern as well.=20 =20 I think it is a great idea as it explicitly allows identification of = changes in jars. =20 Any thoughts ? =20 Cameron. |
|
From: <jue...@we...> - 2004-03-24 15:10:28
|
Note that the Spring jar files contain the exact version number in the = manifest file within the jar, just like jars of Apache products do. = Furthermore, as of the upcoming 1.0 final, our third-party lib directory = contains a readme.txt that specifies the exact product version and usage = within Spring for each jar. Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Colin Sampaleanu Sent: Wednesday, March 24, 2004 4:34 AM To: spr...@li... Subject: Re: [Springframework-developer] JARs .. can they be named based on their version ? Cameron, What's stopping you from renaming them yourself, and deploying that way? = This is what I do personally in some projects that use Spring.=20 Everything has a version number, whether it shipped that way or not. I realize we could do it too in Spring out of the gate, but there's pros = and cons to both sides though... Regards, Colin Cameron Braid wrote: > I have run into a problem with supporting multiple applications that=20 > use different spring versions. > =20 > We store all of our jars, for every application, in a repository. > =20 > In eclipse we link against them, and when deploying we copy them into=20 > the war/ear. > =20 > I upgraded an app to spring 1.0 HEAD yesterday, causing the new=20 > aopalliance.jar to be overwritten in our repository. > =20 > I now receive an aopalliance exception because an app, using spring=20 > rc1, requres the older aopalliance.jar file. > =20 > This issue would be avoided if every jar that spring uses (including=20 > the spring generated jars) are stamped with their version in the = filename. > =20 > I (and others) managed to convince Hibernate, WebWork2 and Xwork to=20 > follow this pattern as well.=20 > =20 > I think it is a great idea as it explicitly allows identification of=20 > changes in jars. > =20 > Any thoughts ? > =20 > Cameron. ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli= ck _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Rodney G. A. \(Krosslink\) <ro...@kr...> - 2004-03-24 15:04:55
|
Hi, I have some problem in the MVC's binding process, when a class have =
two properties of the same type, eg:
class Wheel {
private Long id;
private String name;
=20
}
class Car {
private Wheel wheel1;
private Wheel wheel2;=20
}
This two classes with his sets and gets appropiates methods, and a jsp =
to drive this properties like that excerpt:
<tr>
<td>Wheel 1:</td>
<spring:bind path=3D"obj.wheel1.id">
<td>
<select name=3D"<c:out value=3D"${status.expression}"/>">
<c:forEach var=3D"wheel" items=3D"${wheels}">
<c:if test=3D"${obj.wheel1.id =3D=3D wheel.id}">
<OPTION selected=3D"<c:out =
value=3D"${obj.wheel1.id}"/>" value=3D"<c:out =
value=3D"${wheel.id}"/>"><c:out value=3D"${wheel.name}"/></OPTION>
</c:if>
<c:if test=3D"${obj.wheel1.id !=3D wheel.id}">
<OPTION value=3D"<c:out value=3D"${wheel.id}"/>"><c:out =
value=3D"${wheel.name}"/></OPTION>
</c:if>
</c:forEach>
</select>
</td>
</spring:bind>
</tr>
<tr>
<td>Wheel 2:</td>
<spring:bind path=3D"obj.wheel2.id">
<td>
<select name=3D"<c:out value=3D"${status.expression}"/>">
<c:forEach var=3D"wheel" items=3D"${wheels}">
<c:if test=3D"${obj.wheel2.id =3D=3D wheel.id}">
<OPTION selected=3D"<c:out =
value=3D"${obj.wheel2.id}"/>" value=3D"<c:out =
value=3D"${wheel.id}"/>"><c:out value=3D"${wheel.name}"/></OPTION>
</c:if>
<c:if test=3D"${obj.wheel2.id !=3D wheel.id}">
<OPTION value=3D"<c:out value=3D"${wheel.id}"/>"><c:out =
value=3D"${wheel.name}"/></OPTION>
</c:if>
</c:forEach>
</select>
</td>
</spring:bind>
</tr>
When a submit happens and Spring is going to update the values captured =
to the Bean, the two properties of the same type take the value of the =
first properties that is procesed in the bind algorithm, when the =
process finish the two properties get the same value, any help will be =
preciate. I already debugged some of the Spring code, and perhaps the =
problems is in the class "BeanWrapperImpl" method "setPropertyValue" =
when working with nested properties.
Best Regards, Rodney
Spring is really a powerfull framework, very good job, I already =
studying your samples and read documentation.
|
|
From: <ad...@te...> - 2004-03-24 14:58:46
|
On 03-24-2004 16:41 +1100 Mike Cannon-Brookes <mi...@at...> wrote: > Agreed - personally as a Maven shop this would be most appreciated. We > already name all of the Spring JARs as they come out, but it would be > very useful for some of the dependencies (although I know they're in a > .txt file somewhere from memory). Having jars contain version information poses a problem for version control systems. The file spring.jar gets updated and keeps it's history. A. -- Adam Sherman Technologist +1 (613) 797-6819 http://www.terravox.com/ |
|
From: Rod J. <rod...@in...> - 2004-03-24 06:59:49
|
I agree there's no prototype instance for what we do, but the effect is the same. I think we should keep "prototype" and clarify non-singleton. Regards, Rod ----- Original Message ----- From: "Colin Sampaleanu" <col...@ex...> To: <spr...@li...> Sent: Wednesday, March 24, 2004 3:21 AM Subject: [Springframework-developer] Singleton vs. Prototype, appropriateness of the latter as a name > I was doing a bit of proofing in the manual during a deploy, and was > thinking that to me, it seems to me to be appropriate to call singleton > beans singletons, but the name prototype as used in the manual for > non-singletons is not really appropriate. A prototype, as used in the > Gang of Four book, and as I would think if it just based on what that > word means > http://dictionary.reference.com/search?q=prototype > is a bean or object that exists, and is used as a prototype for creating > new objects, that is, the new objects are essentially copies of it. In > our case though, that's not a fair description; all we have is a bean > definition which is used to create new instances. > > Nitpicking, maybe, but I suggest that when we talk about this and > document this, we talk about beans being deployed in singleton and > non-singleton modes (or as singletons and non-singletons), and leave it > at that. > > Regards, > Colin > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Mike Cannon-B. <mi...@at...> - 2004-03-24 05:41:48
|
Agreed - personally as a Maven shop this would be most appreciated. We =20= already name all of the Spring JARs as they come out, but it would be =20= very useful for some of the dependencies (although I know they're in a =20= .txt file somewhere from memory). Cheers, Mike -- ATLASSIAN - http://www.atlassian.com/ Confluence - the professional J2EE wiki - tried it yet? http://www.atlassian.com/confluence/ On 24/03/2004, at 2:37 PM, Oliver Hutchison wrote: > I raised this as an issue in Jira. > > http://opensource.atlassian.com/projects/spring/secure/ViewIssue.jspa?=20= > ke > y=3DSPR-68 > > > > -----Original Message----- > From: Cameron Braid [mailto:ca...@da...] > Sent: Wednesday, 24 March 2004 2:22 PM > To: spr...@li... > Subject: [Springframework-developer] JARs .. can they be named based = on > their version ? > > > I have run into a problem with supporting multiple applications that =20= > use > different spring versions. > > We store all of our jars, for every application, in a repository. > > In eclipse we link against them, and when deploying we copy them into > the war/ear. > > I upgraded an app to spring 1.0 HEAD yesterday, causing the new > aopalliance.jar to be overwritten in our repository. > > I now receive an aopalliance exception because an app, using spring =20= > rc1, > requres the older aopalliance.jar file. > > This issue would be avoided if every jar that spring uses (including =20= > the > spring generated jars) are stamped with their version in the filename. > > I (and others) managed to convince Hibernate, WebWork2 and Xwork to > follow this pattern as well. > > I think it is a great idea as it explicitly allows identification of > changes in jars. > > Any thoughts ? > > Cameron. > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=CCk > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Oliver H. <Oli...@ou...> - 2004-03-24 03:38:10
|
I raised this as an issue in Jira.=20 http://opensource.atlassian.com/projects/spring/secure/ViewIssue.jspa?ke y=3DSPR-68 -----Original Message----- From: Cameron Braid [mailto:ca...@da...]=20 Sent: Wednesday, 24 March 2004 2:22 PM To: spr...@li... Subject: [Springframework-developer] JARs .. can they be named based on their version ? I have run into a problem with supporting multiple applications that use different spring versions. We store all of our jars, for every application, in a repository. In eclipse we link against them, and when deploying we copy them into the war/ear. I upgraded an app to spring 1.0 HEAD yesterday, causing the new aopalliance.jar to be overwritten in our repository. I now receive an aopalliance exception because an app, using spring rc1, requres the older aopalliance.jar file. This issue would be avoided if every jar that spring uses (including the spring generated jars) are stamped with their version in the filename. I (and others) managed to convince Hibernate, WebWork2 and Xwork to follow this pattern as well.=20 I think it is a great idea as it explicitly allows identification of changes in jars. Any thoughts ? Cameron. |
|
From: Colin S. <col...@ex...> - 2004-03-24 03:31:24
|
Cameron, What's stopping you from renaming them yourself, and deploying that way? This is what I do personally in some projects that use Spring. Everything has a version number, whether it shipped that way or not. I realize we could do it too in Spring out of the gate, but there's pros and cons to both sides though... Regards, Colin Cameron Braid wrote: > I have run into a problem with supporting multiple applications that > use different spring versions. > > We store all of our jars, for every application, in a repository. > > In eclipse we link against them, and when deploying we copy them into > the war/ear. > > I upgraded an app to spring 1.0 HEAD yesterday, causing the new > aopalliance.jar to be overwritten in our repository. > > I now receive an aopalliance exception because an app, using spring > rc1, requres the older aopalliance.jar file. > > This issue would be avoided if every jar that spring uses (including > the spring generated jars) are stamped with their version in the filename. > > I (and others) managed to convince Hibernate, WebWork2 and Xwork to > follow this pattern as well. > > I think it is a great idea as it explicitly allows identification of > changes in jars. > > Any thoughts ? > > Cameron. |
|
From: Cameron B. <ca...@da...> - 2004-03-24 03:22:11
|
I have run into a problem with supporting multiple applications that use different spring versions. We store all of our jars, for every application, in a repository. In eclipse we link against them, and when deploying we copy them into the war/ear. I upgraded an app to spring 1.0 HEAD yesterday, causing the new aopalliance.jar to be overwritten in our repository. I now receive an aopalliance exception because an app, using spring rc1, requres the older aopalliance.jar file. This issue would be avoided if every jar that spring uses (including the spring generated jars) are stamped with their version in the filename. I (and others) managed to convince Hibernate, WebWork2 and Xwork to follow this pattern as well. I think it is a great idea as it explicitly allows identification of changes in jars. Any thoughts ? Cameron. |
|
From: Colin S. <col...@ex...> - 2004-03-24 03:19:04
|
I was doing a bit of proofing in the manual during a deploy, and was thinking that to me, it seems to me to be appropriate to call singleton beans singletons, but the name prototype as used in the manual for non-singletons is not really appropriate. A prototype, as used in the Gang of Four book, and as I would think if it just based on what that word means http://dictionary.reference.com/search?q=prototype is a bean or object that exists, and is used as a prototype for creating new objects, that is, the new objects are essentially copies of it. In our case though, that's not a fair description; all we have is a bean definition which is used to create new instances. Nitpicking, maybe, but I suggest that when we talk about this and document this, we talk about beans being deployed in singleton and non-singleton modes (or as singletons and non-singletons), and leave it at that. Regards, Colin |
|
From: <tho...@tr...> - 2004-03-23 22:33:34
|
Same thing was true for queryForObject - it gave this amusing error org.springframework.dao.InvalidDataAccessApiUsageException: Result object (db-type="VARCHAR2" value="null") is of type [java.lang.String] and not of required type [java.lang.String] After the latest change it now returns a null. Thomas Quoting "jürgen höller [werk3AT]" <jue...@we...>: > Let's return 0, analogous to ResultSet.getInt; I'll fix this for 1.0 = > final (which is otherwise ready, including all docs and readmes). > =20 > Juergen > =20 > > ________________________________ > > Von: spr...@li... im Auftrag = > von tho...@tr... > Gesendet: Di 23.03.2004 22:47 > An: spr...@li... > Betreff: RE: [Springframework-developer] Getting ready for 1.0 final > > > > Found on minor quirk in the new JdbcTemlpate convenience methods. = > queryForInt > returns the following confusing exception when the query returns the = > value > NULL. > > org.springframework.dao.InvalidDataAccessApiUsageException: Result = > object > (db-type=3D"NUMBER" value=3D"null") is of type [java.math.BigDecimal] = > and not of > required type [java.lang.Number] > > We could either return 0 (like getInt() on the ResultSet would), or we = > could > throw an exception with a different message. > > What do you think? > > I don't think this is a big deal, so I would not delay the release for = > 1.0. > > Thomas > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli= > ck > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: <tho...@tr...> - 2004-03-23 22:28:40
|
I'm comitting these changes now - all tests pass!!! Thomas Quoting "jürgen höller [werk3AT]" <jue...@we...>: > Let's return 0, analogous to ResultSet.getInt; I'll fix this for 1.0 = > final (which is otherwise ready, including all docs and readmes). > =20 > Juergen > =20 > > ________________________________ > > Von: spr...@li... im Auftrag = > von tho...@tr... > Gesendet: Di 23.03.2004 22:47 > An: spr...@li... > Betreff: RE: [Springframework-developer] Getting ready for 1.0 final > > > > Found on minor quirk in the new JdbcTemlpate convenience methods. = > queryForInt > returns the following confusing exception when the query returns the = > value > NULL. > > org.springframework.dao.InvalidDataAccessApiUsageException: Result = > object > (db-type=3D"NUMBER" value=3D"null") is of type [java.math.BigDecimal] = > and not of > required type [java.lang.Number] > > We could either return 0 (like getInt() on the ResultSet would), or we = > could > throw an exception with a different message. > > What do you think? > > I don't think this is a big deal, so I would not delay the release for = > 1.0. > > Thomas > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli= > ck > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: <jue...@we...> - 2004-03-23 22:12:59
|
Let's return 0, analogous to ResultSet.getInt; I'll fix this for 1.0 = final (which is otherwise ready, including all docs and readmes). =20 Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von tho...@tr... Gesendet: Di 23.03.2004 22:47 An: spr...@li... Betreff: RE: [Springframework-developer] Getting ready for 1.0 final Found on minor quirk in the new JdbcTemlpate convenience methods. = queryForInt returns the following confusing exception when the query returns the = value NULL. org.springframework.dao.InvalidDataAccessApiUsageException: Result = object (db-type=3D"NUMBER" value=3D"null") is of type [java.math.BigDecimal] = and not of required type [java.lang.Number] We could either return 0 (like getInt() on the ResultSet would), or we = could throw an exception with a different message. What do you think? I don't think this is a big deal, so I would not delay the release for = 1.0. Thomas ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli= ck _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: <tho...@tr...> - 2004-03-23 21:47:52
|
Found on minor quirk in the new JdbcTemlpate convenience methods. queryForInt returns the following confusing exception when the query returns the value NULL. org.springframework.dao.InvalidDataAccessApiUsageException: Result object (db-type="NUMBER" value="null") is of type [java.math.BigDecimal] and not of required type [java.lang.Number] We could either return 0 (like getInt() on the ResultSet would), or we could throw an exception with a different message. What do you think? I don't think this is a big deal, so I would not delay the release for 1.0. Thomas |
|
From: Dmitriy K. <dko...@ru...> - 2004-03-23 01:06:42
|
Well, it's now -5C here in the NE of the USA (NY/NJ area) Arctic jet stream :-( Not quite Spring in the air yet ;-) Dmitriy. ----- Original Message ----- From: Keith Donald <kd...@cs...> Date: Monday, March 22, 2004 4:16 pm Subject: RE: [Springframework-developer] Getting ready for 1.0 final > If you guys need pictures of palm trees, I can send some ;) It's > already up > into the 80's here. > > However Seth Ladd gets my prize for the sweetest location, hard to > beatHawaii - it's spring year around there :) > > Keith > > -----Original Message----- > From: spr...@li... > [spr...@li...] On Behalf Of > Alef Arendsen > Sent: Monday, March 22, 2004 3:37 PM > To: spr...@li... > Subject: RE: [Springframework-developer] Getting ready for 1.0 final > > > No tulips in the center of Amsterdam anymore nowadays, too bad... > > By the way, I still have to see the first tulips popping up, it's > stillfreezing here ;-). > > Alef > > > In Amsterdam many years ago. > > > > Thomas > > > > Quoting Keith Donald <kd...@cs...>: > > > > > Hey nice touch with the 'spring is coming' logo on the web- > site! :) > > > = where was the photo taken? Keith > > > > > > > > > -----Original Message----- > > > From: spr...@li... > > > [spr...@li...] On > > > Behalf > > = > > > Of > > > j=FCrgen h=F6ller [werk3AT] > > > Sent: Friday, March 19, 2004 4:42 PM > > > To: spr...@li... > > > Subject: Re: [Springframework-developer] Getting ready for 1.0 > final> > > > > > > > FYI, I've addressed two recently reported bugs today, one > regarding > > > BeanWrapperImpl's handling of a single Object value for an > array > > > type, = the other regarding PropertyPlaceholderConfigurer > which > > > didn't parse inner = bean > > > definitions before. > > > =20 > > > To fix the PropertyPlaceholderConfigurer issue, I've > introduced a > > > BeanDefinition interface in the beans.factory.config package, = > > > encapsulating > > > the minimal set of bean definition info that's needed for = > > > post-processing > > > them. This replaces the former "getPropertyValues" and > > > "getConstructorArgumentValues" methods on ConfigurableBeanFactory. > > > RootBeanDefinition and ChildBeanDefinition implement the > BeanDefinition> > interface, therefore inner bean definitions can > be parsed through the > > > interface, without making PropertyPlaceholderConfigurer aware of > > > implementation stuff in the beans.factory.support pacakge. > > > =20 > > > Of course, this is incompatible in terms of the > ConfigurableBeanFactory> > interface, but this just affects custom > BeanFactoryPostProcessor> > implementations and custom integration > code, and it's trivial to adapt. > > = > > > As > > > we finally have a BeanDefinition interface now, instead of > > > AbstractBeanDefinition as the common root, I've also used > > > BeanDefinition within > AbstractBeanFactory/DefaultListableBeanFactory > > > and in the BeanDefinitionRegistry interface. It sure looks > cleaner > > > to pass in that interface instead of AbstractBeanDefinition. =20 > > > Feel free to review these changes tomorrow; we won't release > 1.0 final > > > before Saturday night. > > > =20 > > > Juergen > > > =20 > > > > > > ________________________________ > > > > > > Von: spr...@li... im > > > Auftrag = von j=FCrgen h=F6ller [werk3AT] > > > Gesendet: Do 18.03.2004 19:07 > > > An: spr...@li... > > > Betreff: [Springframework-developer] Fw: Getting ready for 1.0 > final> > > > > > > > > > > Peter has a point here. Obviously it's easy to address the > > > init-method = issue by looking for a no-arg method via plain > > > reflection. Note that we don't > > = > > > need > > > BeanWrapper's "invoke" method within the framework anymore > then: > > > Thus, I suggest to drop it completely rather than rework it to > > > support = overloaded methods. Its current javadoc already > > > discourages people to use it = anyway, so > > > I don't think that anyone will miss that method much. IMO, > BeanWrapper = > > > is > > > not about invoking arbitrary methods in the first place... > > > > > > Juergen > > > > > > > > > ________________________________ > > > > > > Von: j=FCrgen h=F6ller [werk3AT] > > > Gesendet: Do 18.03.2004 19:02 > > > An: Peter den Haan > > > Betreff: Re: Getting ready for 1.0 final > > > > > > > > > Peter, > > > > > > I've actually changed the determination of the destroy method > today, > > > to > > = > > > make > > > it work with "shutdown(boolean force)"-style methods (passing > in > > > true as argument in this case). A side effect of this change > is that > > > it looks = for a no-arg method first now, then for one with a > single > > > boolean parameter. > > > > > > I guess I'll rewrite the init-method determination with plain > > > reflection too, to always look for a no-arg method. I'm not > fond of > > > the "invoke" = method in the BeanWrapper interface anyway; I > might > > > suggest to drop it = completely. > > > I'll move this to the list. > > > > > > Juergen > > > > > > > > > ________________________________ > > > > > > Von: Peter den Haan [pde...@ob...] > > > Gesendet: Do 18.03.2004 18:13 > > > An: j=FCrgen h=F6ller [werk3AT] > > > Betreff: Re: Getting ready for 1.0 final > > > > > > > > > Juergen, > > > > > > I was intending to write a test case and fix for this, but it > looks > > > like > > = > > > I > > > may not come around to it in time. I found a limitation in = > > > BeanWrapperImpl that leads to what is arguably a bug in init- > method > > > and destroy-method. > > > > > > BeanWrapperImpl.invoke() looks up the method to invoke by > method > > > name, = not by method signature. In a class with overloaded > methods, > > > the behaviour = of > > > the code (in CachedIntrospectionResults) is essentially undefined. > > > > > > This has repercussions in a couple of places, among others the > = > > > init-method and destroy-method bean tag attributes. If a user > > > specifies destroy-method=3D"close", it is clear that the > intention > > > is for the = no-arg > > > form of this method to be called even if there are other, > overloaded> > versions. This doesn't work at present. > > > > > > The solution I wanted to implement is to modify = > > > CachedIntrospectionResults to key its method information on > method > > > signature rather than just = method > > > name (the current getMethodDescriptor(String methodName) can > remain> > supported for backwards compatibility, although I would > want to better > > > define its semantics). A new getMethodDescriptor(String > methodName, = > > > Object[] > > > args) would implement logic to find the best matching method > given the > > > argument count and types, using the algorithm specified in JLS = > > > 15.12.2.2. > > > > > > I can have a stab at implementing this over the weekend, or > enter it > > > in > > = > > > Jira > > > as a bug (or enhancement). Please let me know what you prefer. > > > > > > Regards, > > > > > > Peter den Haan > > > Principal Systems Engineer > > > OBJECTIVITY > > > Tel: 024 7642 0000 > > > Fax: 024 7642 0001 > > > Email: pde...@ob... > > > www.objectivity.co.uk <=20" > target="l">http://www.objectivity.co.uk/>=20> > > > > The contents of this email and any attachments are strictly > > > confidential > > = > > > and > > > intended solely for the attention of the named addressee(s). > If you > > > are > > = > > > not > > > the addressee(s) you are not authorised to, and must not > disclose, > > > copy, distribute, or retain this message without prior written > > > authority. This footnote also confirms that this message has > been > > > swept for the presence > > = > > > of > > > computer viruses but this does not guarantee that it is virus > free.> > > > > > > > > > > > ____________________________________________________________________> > ____ > > > This e-mail has been scanned for all viruses by Star Internet. > The = > > > service > > > is powered by MessageLabs. For more information on a proactive = > > > anti-virus > > > service working around the clock, around the globe, visit: > > > http://www.star.net.uk > > > > ________________________________________________________________________> > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by: IBM Linux Tutorials > > > Free Linux tutorial presented by Daniel Robbins, President and > CEO > > > of = GenToo technologies. Learn everything from fundamentals > to > > > system > > > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=3Dick> > _______________________________________________ > > > Springframework-developer mailing list > > > Spr...@li... > > > https://lists.sourceforge.net/lists/listinfo/springframework- > develop> > er > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by: IBM Linux Tutorials > > > Free Linux tutorial presented by Daniel Robbins, President and > CEO > > > of = GenToo technologies. Learn everything from fundamentals > to > > > system > > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=CCk > > > _______________________________________________ > > > Springframework-developer mailing list > > > Spr...@li... > > > https://lists.sourceforge.net/lists/listinfo/springframework- > develop> > er > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by: IBM Linux Tutorials > > > Free Linux tutorial presented by Daniel Robbins, President and > CEO > > > of GenToo technologies. Learn everything from fundamentals to > system > > > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=clic> > k > > > _______________________________________________ > > > Springframework-developer mailing list > > > Spr...@li... > > > https://lists.sourceforge.net/lists/listinfo/springframework- > developer> > > > > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: IBM Linux Tutorials > > Free Linux tutorial presented by Daniel Robbins, President and > CEO of > > GenToo technologies. Learn everything from fundamentals to > system > > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click> _______________________________________________ > > Springframework-developer mailing list > > Spr...@li... > > https://lists.sourceforge.net/lists/listinfo/springframework- > developer > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO > of GenToo > technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Seth L. <se...@eh...> - 2004-03-22 21:36:48
|
Keith Donald wrote: > If you guys need pictures of palm trees, I can send some ;) It's already up > into the 80's here. > > However Seth Ladd gets my prize for the sweetest location, hard to beat > Hawaii - it's spring year around there :) hehe except when it's the rainy season, which happens to be right now. Speaking of, if anyone is in Hawaii and wants to talk Spring, or just Java stuff in general, let me know! Also, I was at the San Diego Software Symposium (the nofluffjuststuff one) last week and Spring was definitely the buzz. Looking forward to 1.0! Thanks to everyone for their hard work. Seth |
|
From: Keith D. <kd...@cs...> - 2004-03-22 21:16:06
|
If you guys need pictures of palm trees, I can send some ;) It's = already up into the 80's here. However Seth Ladd gets my prize for the sweetest location, hard to beat Hawaii - it's spring year around there :) Keith -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf = Of Alef Arendsen Sent: Monday, March 22, 2004 3:37 PM To: spr...@li... Subject: RE: [Springframework-developer] Getting ready for 1.0 final No tulips in the center of Amsterdam anymore nowadays, too bad... By the way, I still have to see the first tulips popping up, it's still freezing here ;-). Alef > In Amsterdam many years ago. >=20 > Thomas >=20 > Quoting Keith Donald <kd...@cs...>: >=20 > > Hey nice touch with the 'spring is coming' logo on the web-site! :) = > > =3D where was the photo taken? Keith > > > > > > -----Original Message----- > > From: spr...@li... > > [mailto:spr...@li...] On=20 > > Behalf > =3D > > Of > > j=3DFCrgen h=3DF6ller [werk3AT] > > Sent: Friday, March 19, 2004 4:42 PM > > To: spr...@li... > > Subject: Re: [Springframework-developer] Getting ready for 1.0 final > > > > > > FYI, I've addressed two recently reported bugs today, one regarding=20 > > BeanWrapperImpl's handling of a single Object value for an array=20 > > type, =3D the other regarding PropertyPlaceholderConfigurer which=20 > > didn't parse inner =3D bean > > definitions before. > > =3D20 > > To fix the PropertyPlaceholderConfigurer issue, I've introduced a > > BeanDefinition interface in the beans.factory.config package, =3D > > encapsulating > > the minimal set of bean definition info that's needed for =3D > > post-processing > > them. This replaces the former "getPropertyValues" and > > "getConstructorArgumentValues" methods on ConfigurableBeanFactory. > > RootBeanDefinition and ChildBeanDefinition implement the = BeanDefinition > > interface, therefore inner bean definitions can be parsed through = the > > interface, without making PropertyPlaceholderConfigurer aware of > > implementation stuff in the beans.factory.support pacakge. > > =3D20 > > Of course, this is incompatible in terms of the = ConfigurableBeanFactory > > interface, but this just affects custom BeanFactoryPostProcessor > > implementations and custom integration code, and it's trivial to = adapt. > =3D > > As > > we finally have a BeanDefinition interface now, instead of=20 > > AbstractBeanDefinition as the common root, I've also used=20 > > BeanDefinition within AbstractBeanFactory/DefaultListableBeanFactory = > > and in the BeanDefinitionRegistry interface. It sure looks cleaner=20 > > to pass in that interface instead of AbstractBeanDefinition. =3D20 > > Feel free to review these changes tomorrow; we won't release 1.0 = final > > before Saturday night. > > =3D20 > > Juergen > > =3D20 > > > > ________________________________ > > > > Von: spr...@li... im=20 > > Auftrag =3D von j=3DFCrgen h=3DF6ller [werk3AT] > > Gesendet: Do 18.03.2004 19:07 > > An: spr...@li... > > Betreff: [Springframework-developer] Fw: Getting ready for 1.0 final > > > > > > > > Peter has a point here. Obviously it's easy to address the=20 > > init-method =3D issue by looking for a no-arg method via plain=20 > > reflection. Note that we don't > =3D > > need > > BeanWrapper's "invoke" method within the framework anymore then:=20 > > Thus, I suggest to drop it completely rather than rework it to=20 > > support =3D overloaded methods. Its current javadoc already=20 > > discourages people to use it =3D anyway, so > > I don't think that anyone will miss that method much. IMO, = BeanWrapper =3D > > is > > not about invoking arbitrary methods in the first place... > > > > Juergen > > > > > > ________________________________ > > > > Von: j=3DFCrgen h=3DF6ller [werk3AT] > > Gesendet: Do 18.03.2004 19:02 > > An: Peter den Haan > > Betreff: Re: Getting ready for 1.0 final > > > > > > Peter, > > > > I've actually changed the determination of the destroy method today, = > > to > =3D > > make > > it work with "shutdown(boolean force)"-style methods (passing in=20 > > true as argument in this case). A side effect of this change is that = > > it looks =3D for a no-arg method first now, then for one with a = single=20 > > boolean parameter. > > > > I guess I'll rewrite the init-method determination with plain=20 > > reflection too, to always look for a no-arg method. I'm not fond of=20 > > the "invoke" =3D method in the BeanWrapper interface anyway; I might = > > suggest to drop it =3D completely. > > I'll move this to the list. > > > > Juergen > > > > > > ________________________________ > > > > Von: Peter den Haan [mailto:pde...@ob...] > > Gesendet: Do 18.03.2004 18:13 > > An: j=3DFCrgen h=3DF6ller [werk3AT] > > Betreff: Re: Getting ready for 1.0 final > > > > > > Juergen, > > > > I was intending to write a test case and fix for this, but it looks=20 > > like > =3D > > I > > may not come around to it in time. I found a limitation in =3D=20 > > BeanWrapperImpl that leads to what is arguably a bug in init-method=20 > > and destroy-method. > > > > BeanWrapperImpl.invoke() looks up the method to invoke by method=20 > > name, =3D not by method signature. In a class with overloaded = methods,=20 > > the behaviour =3D of > > the code (in CachedIntrospectionResults) is essentially undefined. > > > > This has repercussions in a couple of places, among others the =3D=20 > > init-method and destroy-method bean tag attributes. If a user=20 > > specifies destroy-method=3D3D"close", it is clear that the intention = > > is for the =3D no-arg > > form of this method to be called even if there are other, overloaded > > versions. This doesn't work at present. > > > > The solution I wanted to implement is to modify =3D=20 > > CachedIntrospectionResults to key its method information on method=20 > > signature rather than just =3D method > > name (the current getMethodDescriptor(String methodName) can remain > > supported for backwards compatibility, although I would want to = better > > define its semantics). A new getMethodDescriptor(String methodName, = =3D > > Object[] > > args) would implement logic to find the best matching method given = the > > argument count and types, using the algorithm specified in JLS =3D > > 15.12.2.2. > > > > I can have a stab at implementing this over the weekend, or enter it = > > in > =3D > > Jira > > as a bug (or enhancement). Please let me know what you prefer. > > > > Regards, > > > > Peter den Haan > > Principal Systems Engineer > > OBJECTIVITY > > Tel: 024 7642 0000 > > Fax: 024 7642 0001 > > Email: pde...@ob... > > www.objectivity.co.uk = <http://www.objectivity.co.uk/>=3D20 > > > > The contents of this email and any attachments are strictly=20 > > confidential > =3D > > and > > intended solely for the attention of the named addressee(s). If you = > > are > =3D > > not > > the addressee(s) you are not authorised to, and must not disclose,=20 > > copy, distribute, or retain this message without prior written=20 > > authority. This footnote also confirms that this message has been=20 > > swept for the presence > =3D > > of > > computer viruses but this does not guarantee that it is virus free. > > > > > > > > ____________________________________________________________________ > > ____ > > This e-mail has been scanned for all viruses by Star Internet. The = =3D > > service > > is powered by MessageLabs. For more information on a proactive =3D > > anti-virus > > service working around the clock, around the globe, visit: > > http://www.star.net.uk > > = ________________________________________________________________________ > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: IBM Linux Tutorials > > Free Linux tutorial presented by Daniel Robbins, President and CEO=20 > > of =3D GenToo technologies. Learn everything from fundamentals to=20 > > system=20 > > = administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id638&op=3D3Dick > > _______________________________________________ > > Springframework-developer mailing list=20 > > Spr...@li... > > https://lists.sourceforge.net/lists/listinfo/springframework-develop > > er > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: IBM Linux Tutorials > > Free Linux tutorial presented by Daniel Robbins, President and CEO=20 > > of =3D GenToo technologies. Learn everything from fundamentals to=20 > > system=20 > > = administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id638&op=3DCCk > > _______________________________________________ > > Springframework-developer mailing list=20 > > Spr...@li... > > https://lists.sourceforge.net/lists/listinfo/springframework-develop > > er > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: IBM Linux Tutorials > > Free Linux tutorial presented by Daniel Robbins, President and CEO=20 > > of GenToo technologies. Learn everything from fundamentals to system = > > = administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli= c > > k > > _______________________________________________ > > Springframework-developer mailing list > > Spr...@li... > > = https://lists.sourceforge.net/lists/listinfo/springframework-developer > > >=20 >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of=20 > GenToo technologies. Learn everything from fundamentals to system=20 > = administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli= ck > _______________________________________________ > Springframework-developer mailing list=20 > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of = GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli= ck _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Alef A. <al...@jt...> - 2004-03-22 20:32:20
|
No tulips in the center of Amsterdam anymore nowadays, too bad... By the way, I still have to see the first tulips popping up, it's still freezing here ;-). Alef > In Amsterdam many years ago. > > Thomas > > Quoting Keith Donald <kd...@cs...>: > > > Hey nice touch with the 'spring is coming' logo on the web-site! :) = > > where > > was the photo taken? Keith > > > > > > -----Original Message----- > > From: spr...@li... > > [mailto:spr...@li...] On Behalf > = > > Of > > j=FCrgen h=F6ller [werk3AT] > > Sent: Friday, March 19, 2004 4:42 PM > > To: spr...@li... > > Subject: Re: [Springframework-developer] Getting ready for 1.0 final > > > > > > FYI, I've addressed two recently reported bugs today, one regarding > > BeanWrapperImpl's handling of a single Object value for an array type, = > > the > > other regarding PropertyPlaceholderConfigurer which didn't parse inner = > > bean > > definitions before. > > =20 > > To fix the PropertyPlaceholderConfigurer issue, I've introduced a > > BeanDefinition interface in the beans.factory.config package, = > > encapsulating > > the minimal set of bean definition info that's needed for = > > post-processing > > them. This replaces the former "getPropertyValues" and > > "getConstructorArgumentValues" methods on ConfigurableBeanFactory. > > RootBeanDefinition and ChildBeanDefinition implement the BeanDefinition > > interface, therefore inner bean definitions can be parsed through the > > interface, without making PropertyPlaceholderConfigurer aware of > > implementation stuff in the beans.factory.support pacakge. > > =20 > > Of course, this is incompatible in terms of the ConfigurableBeanFactory > > interface, but this just affects custom BeanFactoryPostProcessor > > implementations and custom integration code, and it's trivial to adapt. > = > > As > > we finally have a BeanDefinition interface now, instead of > > AbstractBeanDefinition as the common root, I've also used BeanDefinition > > within AbstractBeanFactory/DefaultListableBeanFactory and in the > > BeanDefinitionRegistry interface. It sure looks cleaner to pass in that > > interface instead of AbstractBeanDefinition. > > =20 > > Feel free to review these changes tomorrow; we won't release 1.0 final > > before Saturday night. > > =20 > > Juergen > > =20 > > > > ________________________________ > > > > Von: spr...@li... im Auftrag = > > von > > j=FCrgen h=F6ller [werk3AT] > > Gesendet: Do 18.03.2004 19:07 > > An: spr...@li... > > Betreff: [Springframework-developer] Fw: Getting ready for 1.0 final > > > > > > > > Peter has a point here. Obviously it's easy to address the init-method = > > issue > > by looking for a no-arg method via plain reflection. Note that we don't > = > > need > > BeanWrapper's "invoke" method within the framework anymore then: Thus, I > > suggest to drop it completely rather than rework it to support = > > overloaded > > methods. Its current javadoc already discourages people to use it = > > anyway, so > > I don't think that anyone will miss that method much. IMO, BeanWrapper = > > is > > not about invoking arbitrary methods in the first place... > > > > Juergen > > > > > > ________________________________ > > > > Von: j=FCrgen h=F6ller [werk3AT] > > Gesendet: Do 18.03.2004 19:02 > > An: Peter den Haan > > Betreff: Re: Getting ready for 1.0 final > > > > > > Peter, > > > > I've actually changed the determination of the destroy method today, to > = > > make > > it work with "shutdown(boolean force)"-style methods (passing in true as > > argument in this case). A side effect of this change is that it looks = > > for a > > no-arg method first now, then for one with a single boolean parameter. > > > > I guess I'll rewrite the init-method determination with plain reflection > > too, to always look for a no-arg method. I'm not fond of the "invoke" = > > method > > in the BeanWrapper interface anyway; I might suggest to drop it = > > completely. > > I'll move this to the list. > > > > Juergen > > > > > > ________________________________ > > > > Von: Peter den Haan [mailto:pde...@ob...] > > Gesendet: Do 18.03.2004 18:13 > > An: j=FCrgen h=F6ller [werk3AT] > > Betreff: Re: Getting ready for 1.0 final > > > > > > Juergen, > > > > I was intending to write a test case and fix for this, but it looks like > = > > I > > may not come around to it in time. I found a limitation in = > > BeanWrapperImpl > > that leads to what is arguably a bug in init-method and destroy-method. > > > > BeanWrapperImpl.invoke() looks up the method to invoke by method name, = > > not > > by method signature. In a class with overloaded methods, the behaviour = > > of > > the code (in CachedIntrospectionResults) is essentially undefined. > > > > This has repercussions in a couple of places, among others the = > > init-method > > and destroy-method bean tag attributes. If a user specifies > > destroy-method=3D"close", it is clear that the intention is for the = > > no-arg > > form of this method to be called even if there are other, overloaded > > versions. This doesn't work at present. > > > > The solution I wanted to implement is to modify = > > CachedIntrospectionResults > > to key its method information on method signature rather than just = > > method > > name (the current getMethodDescriptor(String methodName) can remain > > supported for backwards compatibility, although I would want to better > > define its semantics). A new getMethodDescriptor(String methodName, = > > Object[] > > args) would implement logic to find the best matching method given the > > argument count and types, using the algorithm specified in JLS = > > 15.12.2.2. > > > > I can have a stab at implementing this over the weekend, or enter it in > = > > Jira > > as a bug (or enhancement). Please let me know what you prefer. > > > > Regards, > > > > Peter den Haan > > Principal Systems Engineer > > OBJECTIVITY > > Tel: 024 7642 0000 > > Fax: 024 7642 0001 > > Email: pde...@ob... > > www.objectivity.co.uk <http://www.objectivity.co.uk/>=20 > > > > The contents of this email and any attachments are strictly confidential > = > > and > > intended solely for the attention of the named addressee(s). If you are > = > > not > > the addressee(s) you are not authorised to, and must not disclose, copy, > > distribute, or retain this message without prior written authority. This > > footnote also confirms that this message has been swept for the presence > = > > of > > computer viruses but this does not guarantee that it is virus free. > > > > > > > > ________________________________________________________________________ > > This e-mail has been scanned for all viruses by Star Internet. The = > > service > > is powered by MessageLabs. For more information on a proactive = > > anti-virus > > service working around the clock, around the globe, visit: > > http://www.star.net.uk > > ________________________________________________________________________ > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: IBM Linux Tutorials > > Free Linux tutorial presented by Daniel Robbins, President and CEO of = > > GenToo > > technologies. Learn everything from fundamentals to system > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=3Dick > > _______________________________________________ > > Springframework-developer mailing list > > Spr...@li... > > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: IBM Linux Tutorials > > Free Linux tutorial presented by Daniel Robbins, President and CEO of = > > GenToo > > technologies. Learn everything from fundamentals to system > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=CCk > > _______________________________________________ > > Springframework-developer mailing list > > Spr...@li... > > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: IBM Linux Tutorials > > Free Linux tutorial presented by Daniel Robbins, President and CEO of > > GenToo technologies. Learn everything from fundamentals to system > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > > _______________________________________________ > > Springframework-developer mailing list > > Spr...@li... > > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Ou, R. <Ro...@sa...> - 2004-03-22 19:54:26
|
Yes, the cvs version worked. Thanks!
Rong
> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...]
> On Behalf
> Of j=FCrgen h=F6ller [werk3AT]
> Sent: Monday, March 22, 2004 12:02 PM
> To: spr...@li...
> Subject: RE: [Springframework-developer] property placeholder=20
> in nested
> bean definitions
>=20
>=20
> Yep, that's a bug - it's already fixed in CVS, to be included=20
> in the upcoming 1.0 final.
>=20
> Juergen
>=20
>=20
> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...]
> On Behalf
> Of Ou, Rong
> Sent: Monday, March 22, 2004 6:35 PM
> To: spr...@li...
> Subject: [Springframework-developer] property placeholder in=20
> nested bean
> definitions
>=20
>=20
> Hi all,
>=20
> I am not sure if this is a "feature" or a bug, but here it is.
>=20
> I am trying to use property placeholders in my bean=20
> definition. I also happen to have some nested bean=20
> definitions. But it seems the property placeholders only work=20
> on top level bean definitions, not inside the nested ones.
>=20
> So this works:
>=20
> <beans>
> <bean class=3D"com.foo.A">
> <property name=3D"b">
> <ref bean=3D"b"/>
> </property>
> </bean>
> <bean id=3D"b" class=3D"com.foo.B">
> <property name=3D"xyz">
> <value>${xyz.value}</value>
> </property>
> </bean>
> </beans>
>=20
> But this doesn't:
>=20
> <beans>
> <bean class=3D"com.foo.A">
> <property name=3D"b">
> <bean id=3D"b" class=3D"com.foo.B">
> <property name=3D"xyz">
> <value>${xyz.value}</value>
> </property>
> </bean>
> </property>
> </bean>
> </beans>
>=20
> Is this a bug?
>=20
> Thanks,
>=20
> Rong
> =20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=3Dick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=3Dick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20
|
|
From: <jue...@we...> - 2004-03-22 18:03:46
|
Yep, that's a bug - it's already fixed in CVS, to be included in the =
upcoming 1.0 final.
Juergen
-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of Ou, Rong
Sent: Monday, March 22, 2004 6:35 PM
To: spr...@li...
Subject: [Springframework-developer] property placeholder in nested bean
definitions
Hi all,
I am not sure if this is a "feature" or a bug, but here it is.
I am trying to use property placeholders in my bean definition. I also =
happen to have some nested bean definitions. But it seems the property =
placeholders only work on top level bean definitions, not inside the =
nested ones.
So this works:
<beans>
<bean class=3D"com.foo.A">
<property name=3D"b">
<ref bean=3D"b"/>
</property>
</bean>
<bean id=3D"b" class=3D"com.foo.B">
<property name=3D"xyz">
<value>${xyz.value}</value>
</property>
</bean>
</beans>
But this doesn't:
<beans>
<bean class=3D"com.foo.A">
<property name=3D"b">
<bean id=3D"b" class=3D"com.foo.B">
<property name=3D"xyz">
<value>${xyz.value}</value>
</property>
</bean>
</property>
</bean>
</beans>
Is this a bug?
Thanks,
Rong
=20
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer
|