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: <jue...@we...> - 2003-12-18 19:31:55
|
Ross, I've just re-tested Petclinic from our current CVS HEAD against a = dropped-in Hibernate 2.1 final (plus cglib2, minus cglib-asm), with and = without OpenSessionInViewFilter. Works nicely for me - no VerifyErrors. = Could you please re-try and re-report if there are still issues? Note that the AOP framework is not migrated to CGLIB2 yet (it's in the = works), but this shouldn't affect you at all if you just proxy via = interfaces (the default). Simply remove cglib-asm from the class path, = drop in hibernate2, cglib2, eh-cache - and you should be done. Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Ross Mason Sent: Tuesday, December 16, 2003 11:46 PM To: spr...@li... Subject: Re: [Springframework-developer] Refreshing the ApplicationContext... Hi j=FCrgen, Sounds interesting, anything without EJB is always a bonus in my book -=20 excuse the pun ;-) We've actually decided to wait for the M4 release before migrating. The = problem is that we're using a hibernate 2.1 jar built from HEAD and I=20 was getting VerifyErrors errors when running with the latest from Spring = HEAD due to an incompatability with the two jars. If you would like me to test it once M4 is using hibernate 2.1 and=20 before you make the actual release I would be happy to. Cheers, Ross j=FCrgen h=F6ller [werk3AT] wrote: > It's "J2EE Development Without EJB", co-authored by Rod and me, the = follow-up to Rod's "J2EE Design and Development". Editing deadline is = mid January, so you can guess that we're quite busy! >=20 > Of course, the book uses Spring for all examples - but it is an = architecture book, not a Spring tutorial. A dedicated Spring book will = follow later next year :-) >=20 > BTW, does the OpenSessionInViewFilter work for you? If there are any = issues with it, please tell me before the M4 release... >=20 > Finally, is there some documentation on the "external-ref" mechanism = that you use for XWork/Spring integration? We will probably refer to = that in Spring docs and the book, so I'd like to make sure that we get = the syntax right. >=20 > Juergen >=20 >=20 > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...]On = Behalf > Of Ross Mason > Sent: Tuesday, December 16, 2003 3:39 AM > To: spr...@li... > Subject: Re: [Springframework-developer] Refreshing the > ApplicationContext... >=20 >=20 > Ok mate, sounds like it's time for you to hit the sack. >=20 > BTW What's the book? you can tell me in the morning ;-) >=20 > Cheers, >=20 > Ross >=20 > j=FCrgen h=F6ller [werk3AT] wrote: >=20 >=20 >>I could have thought of that if it wasn't already so late (3:20 in the = morning now). Yes, that's a known limitation: If you proxy an object, = both the proxy and the target object will match the type. You need to = resort to explicit references for such beans - as I said, this will even = work for specific references if you apply autowire-by-type in general. >>=20 >>BTW, have I mentioned that writing a book is *damn hard work*? ;-) >>=20 >>Juergen >>=20 >> >>________________________________ >> >>Von: spr...@li... im Auftrag = von Ross Mason >>Gesendet: Di 16.12.2003 02:23 >>An: spr...@li... >>Betreff: Re: [Springframework-developer] Refreshing the = ApplicationContext... >> >> >> >>Hi j=FCrgen, >> >>When I run getBeansOfType() on our config (turning off autowireByType) = I >>do get two beans returned: >>- I get the emialTemplateManager as expected (this is a proxy >>org.springframework.transaction.interceptor.TransactionProxyFactoryBean= ). >>- I also get back our emailTemplateManagerTarget which is our proxied >>object. >> >>This suggests you can't use autowireByType when using >>TransactionProxyFactoryBean or any other ProxyFactoryBean. Is this >>intended behaviour? >> >>Cheers, >> >>Ross >> >> >>j=FCrgen h=F6ller [werk3AT] wrote: >> >> >> >>>Ross, >>> >>>If you build a single context from multiple files, autowiring will = automatically scan all the bean definitions in those files. In your = case, I assume that you do have multiple definitions of type = EmailTemplateManager, possibly in two different context files. You could = check that programmatically by examining the result of = ApplicationContext.getBeansOfType(EmailTemplateManager.class, true, = true). >>> >>>In any case, even if you apply autowiring in general, you can always = override a specific dependency, like an explicit bean reference from = property "emailTemplateManager" of bean "notifierCreatePage" to a = specific bean of type EmailTemplateManager: >>> >>><bean id=3D"notifierCreatePage" class=3D"..." autowire=3D"byType"> >>> <property name=3D"emailTemplateManager"><ref = bean=3D"myEmailTemplateManager"/></property> >>> ... >>></bean> >>> >>>Juergen >>> >>> >>>________________________________ >>> >>>Von: spr...@li... im Auftrag = von Ross Mason >>>Gesendet: Di 16.12.2003 01:00 >>>An: spr...@li... >>>Betreff: Re: [Springframework-developer] Refreshing the = ApplicationContext... >>> >>> >>> >>>Hi j=FCrgen, >>> >>>We were using refresh as we needed to defer the initialisation of the >>>String container the first time our app is run until the user has = setup >>>their db settings, at which point we initialise the container. After >>>that, if/when the server is restarted we use your = ContextLoaderListener >>>is used to initialise the container. >>> >>>I think I've just realised what the problem is. We have 3 >>>applicationContexts and the bean causing the error is defined in a >>>different context. Is there a way to autowire over multiple = contexts? >>> >>>If this is the case, the exception for this scenario is a bit = misleading >>>as it tells me there is more than one satifiable dependency. >>> >>>The exception we get is - >>>org.springframework.beans.FatalBeanException: Can't resolve reference = to >>>bean 'notifierCreatePage' while setting property 'listeners[0]' on = bean >>>'producerCreatePage'; nested exception is: >>>org.springframework.beans.factory.UnsatisfiedDependencyException: = Bean >>>with name 'notifierCreatePage' has an unsatisfied dependency = expressed >>>through property 'emailTemplateManager': set this property value or >>>disable dependency checking for this bean; detail message =3D [There = are 2 >>>beans of type [interface >>>com.atlassian.confluence.mail.template.EmailTemplateManager] for >>>autowire by type. There should have been 1 to be able to autowire >>>property 'emailTemplateManager' of bean 'notifierCreatePage'.] >>>(This is very informative excetion BTW ;-)) >>> >>>Cheers, >>> >>>Ross >>> >>> >>>j=FCrgen h=F6ller [werk3AT] wrote: >>> >>> >>> >>> >>>>Hi Ross, >>>> >>>>"refresh" is now in ConfigurableApplicationContext, but you = shouldn't need that for typical usages anyway. I guess what you're = trying to do is custom initialization of the root WebApplicationContext, = storing it in a custom place via the setApplicationContext call. That = should be fine: I suppose that the error you're getting has other = origins. Autowiring has been significantly reworked; could you check for = which components you get more than one matching bean? The reason could = be that you actually *have* multiple matching beans, which just weren't = found by M2's autowire implementation, maybe due to being created by = FactoryBeans. Could you quote relevant parts of your configuration? >>>> >>>>Juergen >>>> >>>> >>>>________________________________ >>>> >>>>Von: spr...@li... im = Auftrag von Ross Mason >>>>Gesendet: Mo 15.12.2003 07:50 >>>>An: spr...@li... >>>>Betreff: [Springframework-developer] Refreshing the = ApplicationContext... >>>> >>>> >>>> >>>>Hi, >>>> >>>>In the latest source the ApplicationContext.refresh() method has = been >>>>removed. What is the recommended way of refreshing an >>>>applicationContext now. I'm trying - >>>> >>>> ContextLoader loader =3D new ContextLoader(); >>>> setApplicationContext( >>>>loader.initWebApplicationContext(servletContext) ); >>>> >>>>But I am getting an error saying that there is more than one = matching >>>>bean on some components when autoWiring by type. Our code and cofig >>>>works fine with M2 release, but we're mored to the latest source to = make >>>>use of the OpenSessionInViewFilter. >>>> >>>>Any ideas? >>>> >>>> >>>>Cheers, >>>> >>>>Ross >>>> >>>> >>>> >>>>------------------------------------------------------- >>>>This SF.net email is sponsored by: IBM Linux Tutorials. >>>>Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's >>>>Free Linux Tutorials. Learn everything from the bash shell to sys = admin. >>>>Click now! = http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick >>>>_______________________________________________ >>>>Springframework-developer mailing list >>>>Spr...@li... >>>>https://lists.sourceforge.net/lists/listinfo/springframework-develope= r >>>> >>>> >>>> >>>> >>>>------------------------------------------------------- >>>>This SF.net email is sponsored by: IBM Linux Tutorials. >>>>Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's >>>>Free Linux Tutorials. Learn everything from the bash shell to sys = admin. >>>>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=CCk >>>>_______________________________________________ >>>>Springframework-developer mailing list >>>>Spr...@li... >>>>https://lists.sourceforge.net/lists/listinfo/springframework-develope= r >>>> >>> >>> >>> >>> >>>------------------------------------------------------- >>>This SF.net email is sponsored by: IBM Linux Tutorials. >>>Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's >>>Free Linux Tutorials. Learn everything from the bash shell to sys = admin. >>>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&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. >>>Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's >>>Free Linux Tutorials. Learn everything from the bash shell to sys = admin. >>>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&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. >>Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's >>Free Linux Tutorials. Learn everything from the bash shell to sys = admin. >>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&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. >>Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's >>Free Linux Tutorials. Learn everything from the bash shell to sys = admin. >>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=CCk >>_______________________________________________ >>Springframework-developer mailing list >>Spr...@li... >>https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys = admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&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. > Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys = admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=CCk > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer >=20 ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's Free Linux Tutorials. Learn everything from the bash shell to sys = admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=3Dick _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Norris, T. <tys...@be...> - 2003-12-17 19:14:19
|
Hi All -=20 I'm trying to implement a very minimalist hibernate interface within our = application, and would like to do so without creating a Spring = application context. What I have working so far, and the problems with each: - extending HibernateDaoSupport - provides simple session = creation/access, but a new session is always created - extending HibernateDaoSupport; using = TransactionSynchronizationManager.initSynchronization() before getting = the HibernateTemplate - provides session creation and ThreadLocal = binding, but the session is never closed/removed (i.e. same session is = used indefinitely). I realize I will need to create some transactional boundaries to = properly handle this situation - any advice on how to do so easily? This solution need to operate within and without SLSB transactions.=20 My next approach will be to manually create a UserTransaction before the = query inits, and commit/rollback after my series of queries - similar to = the ThreadLocal-session-via-servlet-filter pattern.=20 I'm using weblogic, btw. thanks for any feedback tyson > This electronic transmission (and any attached document or file) is = confidential and intended for the sole use of the individual's) to whom = it is addressed. Any further distribution or copying of this message is = strictly prohibited. If you received this message in error, please = notify the sender, and destroy the message (and attached files), = immediately. BenefitPoint is not liable for any use or misuse contrary = to these directions >=20 >=20 |
|
From: Ross M. <ro...@at...> - 2003-12-16 22:46:04
|
Hi j=FCrgen, Sounds interesting, anything without EJB is always a bonus in my book -=20 excuse the pun ;-) We've actually decided to wait for the M4 release before migrating. The=20 problem is that we're using a hibernate 2.1 jar built from HEAD and I=20 was getting VerifyErrors errors when running with the latest from Spring=20 HEAD due to an incompatability with the two jars. If you would like me to test it once M4 is using hibernate 2.1 and=20 before you make the actual release I would be happy to. Cheers, Ross j=FCrgen h=F6ller [werk3AT] wrote: > It's "J2EE Development Without EJB", co-authored by Rod and me, the fol= low-up to Rod's "J2EE Design and Development". Editing deadline is mid Ja= nuary, so you can guess that we're quite busy! >=20 > Of course, the book uses Spring for all examples - but it is an archite= cture book, not a Spring tutorial. A dedicated Spring book will follow la= ter next year :-) >=20 > BTW, does the OpenSessionInViewFilter work for you? If there are any is= sues with it, please tell me before the M4 release... >=20 > Finally, is there some documentation on the "external-ref" mechanism th= at you use for XWork/Spring integration? We will probably refer to that i= n Spring docs and the book, so I'd like to make sure that we get the synt= ax right. >=20 > Juergen >=20 >=20 > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...]On Behalf > Of Ross Mason > Sent: Tuesday, December 16, 2003 3:39 AM > To: spr...@li... > Subject: Re: [Springframework-developer] Refreshing the > ApplicationContext... >=20 >=20 > Ok mate, sounds like it's time for you to hit the sack. >=20 > BTW What's the book? you can tell me in the morning ;-) >=20 > Cheers, >=20 > Ross >=20 > j=FCrgen h=F6ller [werk3AT] wrote: >=20 >=20 >>I could have thought of that if it wasn't already so late (3:20 in the = morning now). Yes, that's a known limitation: If you proxy an object, bot= h the proxy and the target object will match the type. You need to resort= to explicit references for such beans - as I said, this will even work f= or specific references if you apply autowire-by-type in general. >>=20 >>BTW, have I mentioned that writing a book is *damn hard work*? ;-) >>=20 >>Juergen >>=20 >> >>________________________________ >> >>Von: spr...@li... im Auftrag v= on Ross Mason >>Gesendet: Di 16.12.2003 02:23 >>An: spr...@li... >>Betreff: Re: [Springframework-developer] Refreshing the ApplicationCont= ext... >> >> >> >>Hi j=FCrgen, >> >>When I run getBeansOfType() on our config (turning off autowireByType) = I >>do get two beans returned: >>- I get the emialTemplateManager as expected (this is a proxy >>org.springframework.transaction.interceptor.TransactionProxyFactoryBean= ). >>- I also get back our emailTemplateManagerTarget which is our proxied >>object. >> >>This suggests you can't use autowireByType when using >>TransactionProxyFactoryBean or any other ProxyFactoryBean. Is this >>intended behaviour? >> >>Cheers, >> >>Ross >> >> >>j=FCrgen h=F6ller [werk3AT] wrote: >> >> >> >>>Ross, >>> >>>If you build a single context from multiple files, autowiring will aut= omatically scan all the bean definitions in those files. In your case, I = assume that you do have multiple definitions of type EmailTemplateManager= , possibly in two different context files. You could check that programma= tically by examining the result of ApplicationContext.getBeansOfType(Emai= lTemplateManager.class, true, true). >>> >>>In any case, even if you apply autowiring in general, you can always o= verride a specific dependency, like an explicit bean reference from prope= rty "emailTemplateManager" of bean "notifierCreatePage" to a specific bea= n of type EmailTemplateManager: >>> >>><bean id=3D"notifierCreatePage" class=3D"..." autowire=3D"byType"> >>> <property name=3D"emailTemplateManager"><ref bean=3D"myEmailTemplateM= anager"/></property> >>> ... >>></bean> >>> >>>Juergen >>> >>> >>>________________________________ >>> >>>Von: spr...@li... im Auftrag = von Ross Mason >>>Gesendet: Di 16.12.2003 01:00 >>>An: spr...@li... >>>Betreff: Re: [Springframework-developer] Refreshing the ApplicationCon= text... >>> >>> >>> >>>Hi j=FCrgen, >>> >>>We were using refresh as we needed to defer the initialisation of the >>>String container the first time our app is run until the user has setu= p >>>their db settings, at which point we initialise the container. After >>>that, if/when the server is restarted we use your ContextLoaderListene= r >>>is used to initialise the container. >>> >>>I think I've just realised what the problem is. We have 3 >>>applicationContexts and the bean causing the error is defined in a >>>different context. Is there a way to autowire over multiple contexts? >>> >>>If this is the case, the exception for this scenario is a bit misleadi= ng >>>as it tells me there is more than one satifiable dependency. >>> >>>The exception we get is - >>>org.springframework.beans.FatalBeanException: Can't resolve reference = to >>>bean 'notifierCreatePage' while setting property 'listeners[0]' on bea= n >>>'producerCreatePage'; nested exception is: >>>org.springframework.beans.factory.UnsatisfiedDependencyException: Bean >>>with name 'notifierCreatePage' has an unsatisfied dependency expressed >>>through property 'emailTemplateManager': set this property value or >>>disable dependency checking for this bean; detail message =3D [There a= re 2 >>>beans of type [interface >>>com.atlassian.confluence.mail.template.EmailTemplateManager] for >>>autowire by type. There should have been 1 to be able to autowire >>>property 'emailTemplateManager' of bean 'notifierCreatePage'.] >>>(This is very informative excetion BTW ;-)) >>> >>>Cheers, >>> >>>Ross >>> >>> >>>j=FCrgen h=F6ller [werk3AT] wrote: >>> >>> >>> >>> >>>>Hi Ross, >>>> >>>>"refresh" is now in ConfigurableApplicationContext, but you shouldn't= need that for typical usages anyway. I guess what you're trying to do is= custom initialization of the root WebApplicationContext, storing it in a= custom place via the setApplicationContext call. That should be fine: I = suppose that the error you're getting has other origins. Autowiring has b= een significantly reworked; could you check for which components you get = more than one matching bean? The reason could be that you actually *have*= multiple matching beans, which just weren't found by M2's autowire imple= mentation, maybe due to being created by FactoryBeans. Could you quote re= levant parts of your configuration? >>>> >>>>Juergen >>>> >>>> >>>>________________________________ >>>> >>>>Von: spr...@li... im Auftrag= von Ross Mason >>>>Gesendet: Mo 15.12.2003 07:50 >>>>An: spr...@li... >>>>Betreff: [Springframework-developer] Refreshing the ApplicationContex= t... >>>> >>>> >>>> >>>>Hi, >>>> >>>>In the latest source the ApplicationContext.refresh() method has been >>>>removed. What is the recommended way of refreshing an >>>>applicationContext now. I'm trying - >>>> >>>> ContextLoader loader =3D new ContextLoader(); >>>> setApplicationContext( >>>>loader.initWebApplicationContext(servletContext) ); >>>> >>>>But I am getting an error saying that there is more than one matching >>>>bean on some components when autoWiring by type. Our code and cofig >>>>works fine with M2 release, but we're mored to the latest source to m= ake >>>>use of the OpenSessionInViewFilter. >>>> >>>>Any ideas? >>>> >>>> >>>>Cheers, >>>> >>>>Ross >>>> >>>> >>>> >>>>------------------------------------------------------- >>>>This SF.net email is sponsored by: IBM Linux Tutorials. >>>>Become an expert in LINUX or just sharpen your skills. Sign up for I= BM's >>>>Free Linux Tutorials. Learn everything from the bash shell to sys ad= min. >>>>Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dcli= ck >>>>_______________________________________________ >>>>Springframework-developer mailing list >>>>Spr...@li... >>>>https://lists.sourceforge.net/lists/listinfo/springframework-develope= r >>>> >>>> >>>> >>>> >>>>------------------------------------------------------- >>>>This SF.net email is sponsored by: IBM Linux Tutorials. >>>>Become an expert in LINUX or just sharpen your skills. Sign up for I= BM's >>>>Free Linux Tutorials. Learn everything from the bash shell to sys ad= min. >>>>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=CCk >>>>_______________________________________________ >>>>Springframework-developer mailing list >>>>Spr...@li... >>>>https://lists.sourceforge.net/lists/listinfo/springframework-develope= r >>>> >>> >>> >>> >>> >>>------------------------------------------------------- >>>This SF.net email is sponsored by: IBM Linux Tutorials. >>>Become an expert in LINUX or just sharpen your skills. Sign up for IB= M's >>>Free Linux Tutorials. Learn everything from the bash shell to sys adm= in. >>>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&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. >>>Become an expert in LINUX or just sharpen your skills. Sign up for IB= M's >>>Free Linux Tutorials. Learn everything from the bash shell to sys adm= in. >>>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&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. >>Become an expert in LINUX or just sharpen your skills. Sign up for IBM= 's >>Free Linux Tutorials. Learn everything from the bash shell to sys admi= n. >>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&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. >>Become an expert in LINUX or just sharpen your skills. Sign up for IBM= 's >>Free Linux Tutorials. Learn everything from the bash shell to sys admi= n. >>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=CCk >>_______________________________________________ >>Springframework-developer mailing list >>Spr...@li... >>https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM= 's > Free Linux Tutorials. Learn everything from the bash shell to sys admi= n. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&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. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM= 's > Free Linux Tutorials. Learn everything from the bash shell to sys admi= n. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=CCk > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer >=20 |
|
From: <jue...@we...> - 2003-12-16 15:17:13
|
It's "J2EE Development Without EJB", co-authored by Rod and me, the = follow-up to Rod's "J2EE Design and Development". Editing deadline is = mid January, so you can guess that we're quite busy! Of course, the book uses Spring for all examples - but it is an = architecture book, not a Spring tutorial. A dedicated Spring book will = follow later next year :-) BTW, does the OpenSessionInViewFilter work for you? If there are any = issues with it, please tell me before the M4 release... Finally, is there some documentation on the "external-ref" mechanism = that you use for XWork/Spring integration? We will probably refer to = that in Spring docs and the book, so I'd like to make sure that we get = the syntax right. Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Ross Mason Sent: Tuesday, December 16, 2003 3:39 AM To: spr...@li... Subject: Re: [Springframework-developer] Refreshing the ApplicationContext... Ok mate, sounds like it's time for you to hit the sack. BTW What's the book? you can tell me in the morning ;-) Cheers, Ross j=FCrgen h=F6ller [werk3AT] wrote: > I could have thought of that if it wasn't already so late (3:20 in the = morning now). Yes, that's a known limitation: If you proxy an object, = both the proxy and the target object will match the type. You need to = resort to explicit references for such beans - as I said, this will even = work for specific references if you apply autowire-by-type in general. > =20 > BTW, have I mentioned that writing a book is *damn hard work*? ;-) > =20 > Juergen > =20 >=20 > ________________________________ >=20 > Von: spr...@li... im Auftrag = von Ross Mason > Gesendet: Di 16.12.2003 02:23 > An: spr...@li... > Betreff: Re: [Springframework-developer] Refreshing the = ApplicationContext... >=20 >=20 >=20 > Hi j=FCrgen, >=20 > When I run getBeansOfType() on our config (turning off autowireByType) = I > do get two beans returned: > - I get the emialTemplateManager as expected (this is a proxy > = org.springframework.transaction.interceptor.TransactionProxyFactoryBean).= > - I also get back our emailTemplateManagerTarget which is our proxied > object. >=20 > This suggests you can't use autowireByType when using > TransactionProxyFactoryBean or any other ProxyFactoryBean. Is this > intended behaviour? >=20 > Cheers, >=20 > Ross >=20 >=20 > j=FCrgen h=F6ller [werk3AT] wrote: >=20 >=20 >>Ross, >> >>If you build a single context from multiple files, autowiring will = automatically scan all the bean definitions in those files. In your = case, I assume that you do have multiple definitions of type = EmailTemplateManager, possibly in two different context files. You could = check that programmatically by examining the result of = ApplicationContext.getBeansOfType(EmailTemplateManager.class, true, = true). >> >>In any case, even if you apply autowiring in general, you can always = override a specific dependency, like an explicit bean reference from = property "emailTemplateManager" of bean "notifierCreatePage" to a = specific bean of type EmailTemplateManager: >> >><bean id=3D"notifierCreatePage" class=3D"..." autowire=3D"byType"> >> <property name=3D"emailTemplateManager"><ref = bean=3D"myEmailTemplateManager"/></property> >> ... >></bean> >> >>Juergen >> >> >>________________________________ >> >>Von: spr...@li... im Auftrag = von Ross Mason >>Gesendet: Di 16.12.2003 01:00 >>An: spr...@li... >>Betreff: Re: [Springframework-developer] Refreshing the = ApplicationContext... >> >> >> >>Hi j=FCrgen, >> >>We were using refresh as we needed to defer the initialisation of the >>String container the first time our app is run until the user has = setup >>their db settings, at which point we initialise the container. After >>that, if/when the server is restarted we use your = ContextLoaderListener >>is used to initialise the container. >> >>I think I've just realised what the problem is. We have 3 >>applicationContexts and the bean causing the error is defined in a >>different context. Is there a way to autowire over multiple contexts? >> >>If this is the case, the exception for this scenario is a bit = misleading >>as it tells me there is more than one satifiable dependency. >> >>The exception we get is - >>org.springframework.beans.FatalBeanException: Can't resolve reference = to >>bean 'notifierCreatePage' while setting property 'listeners[0]' on = bean >>'producerCreatePage'; nested exception is: >>org.springframework.beans.factory.UnsatisfiedDependencyException: Bean >>with name 'notifierCreatePage' has an unsatisfied dependency expressed >>through property 'emailTemplateManager': set this property value or >>disable dependency checking for this bean; detail message =3D [There = are 2 >>beans of type [interface >>com.atlassian.confluence.mail.template.EmailTemplateManager] for >>autowire by type. There should have been 1 to be able to autowire >>property 'emailTemplateManager' of bean 'notifierCreatePage'.] >>(This is very informative excetion BTW ;-)) >> >>Cheers, >> >>Ross >> >> >>j=FCrgen h=F6ller [werk3AT] wrote: >> >> >> >>>Hi Ross, >>> >>>"refresh" is now in ConfigurableApplicationContext, but you shouldn't = need that for typical usages anyway. I guess what you're trying to do is = custom initialization of the root WebApplicationContext, storing it in a = custom place via the setApplicationContext call. That should be fine: I = suppose that the error you're getting has other origins. Autowiring has = been significantly reworked; could you check for which components you = get more than one matching bean? The reason could be that you actually = *have* multiple matching beans, which just weren't found by M2's = autowire implementation, maybe due to being created by FactoryBeans. = Could you quote relevant parts of your configuration? >>> >>>Juergen >>> >>> >>>________________________________ >>> >>>Von: spr...@li... im Auftrag = von Ross Mason >>>Gesendet: Mo 15.12.2003 07:50 >>>An: spr...@li... >>>Betreff: [Springframework-developer] Refreshing the = ApplicationContext... >>> >>> >>> >>>Hi, >>> >>>In the latest source the ApplicationContext.refresh() method has been >>>removed. What is the recommended way of refreshing an >>>applicationContext now. I'm trying - >>> >>> ContextLoader loader =3D new ContextLoader(); >>> setApplicationContext( >>>loader.initWebApplicationContext(servletContext) ); >>> >>>But I am getting an error saying that there is more than one matching >>>bean on some components when autoWiring by type. Our code and cofig >>>works fine with M2 release, but we're mored to the latest source to = make >>>use of the OpenSessionInViewFilter. >>> >>>Any ideas? >>> >>> >>>Cheers, >>> >>>Ross >>> >>> >>> >>>------------------------------------------------------- >>>This SF.net email is sponsored by: IBM Linux Tutorials. >>>Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's >>>Free Linux Tutorials. Learn everything from the bash shell to sys = admin. >>>Click now! = http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick >>>_______________________________________________ >>>Springframework-developer mailing list >>>Spr...@li... >>>https://lists.sourceforge.net/lists/listinfo/springframework-developer= >>> >>> >>> >>> >>>------------------------------------------------------- >>>This SF.net email is sponsored by: IBM Linux Tutorials. >>>Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's >>>Free Linux Tutorials. Learn everything from the bash shell to sys = admin. >>>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&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. >>Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's >>Free Linux Tutorials. Learn everything from the bash shell to sys = admin. >>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&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. >>Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's >>Free Linux Tutorials. Learn everything from the bash shell to sys = admin. >>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=CCk >>_______________________________________________ >>Springframework-developer mailing list >>Spr...@li... >>https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys = admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=3Dick > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys = admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=CCk > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer >=20 ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's Free Linux Tutorials. Learn everything from the bash shell to sys = admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=3Dick _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Rod J. <rod...@in...> - 2003-12-16 13:11:22
|
I'm just looking at Juergen's JPetStore demo, which is very nice. Congratulations, Juergen! Trivial to get running as well--just copied it to Tomcat 5, started HSQLDB and all done. We need to modify the look and feel--ideally before M4. We should keep the iBATIS logo as it still uses iBATIS DB and is based on Clinton's original jPetStore, but we also need "powered by Spring" branding. Perhaps in the header? I was going to take a look at this myself, but then I remembered that my artistic skills are not going to help promote Spring... Regards, Rod |
|
From: Rod J. <rod...@in...> - 2003-12-16 11:51:26
|
Alef, I've fixed it--that is, your configuration, not Spring :-) The problem is that you expect the proxy to be of type Assembler, which is a class, not an interface, hence dynamic proxies can't work. Setting proxyTargetClass to be true in the two transactionFactoryProxies solves the problem. The reason it worked if it didn't implement the interface is that TransactionFactoryProxy bean realized that with no interfaces, it had to use CGLIB to proxy the class. I've checked in the changes. Regards, Rod ----- Original Message ----- From: "Alef Arendsen" <al...@jt...> To: <spr...@li...> Cc: <Jo...@jt...> Sent: Tuesday, December 16, 2003 11:21 AM Subject: RE: [Springframework-developer] Hibernate session and ApplicationContext > Ok, the story continues. > > Juergen, I've added a test to the context.support package, > ClasspathXmlApplicationContextTests. > > There are trhee contexts. B and C have to Logic beans in them. In A, > there are two Assembler beans, that both assemble a Service bean (also > defined in A) and a Logic bean (assemblerOne collaborates with logicOne, > assemblerTwo collaborates with logicTwo). Both Assembler beans are > wrapped by a TxProxyFactory (resulting in wrappedAssemblerOne and > wrappedAssemblerTwo). These are also defined in A. > > Then - and that's the issue - logicOne depends on wrappedAssemblerTwo, > logicTwo depends on wrappedAssemblerOne. This all goes well - until I > let Assembler implement _any_ interface. Right now, I've commented out > the implementation in Assembler of TestIF. Just uncomment it, run the > test, and it'll fail. As it is located in the CVS, it'll succeed! It > seems like the transactionmanager proxy does not implement all interface > or something a like. > > Exception: > > Can't resolve reference to bean 'logicOne' while setting property > 'logic' on bean 'assemblerOne'; nested exception is: > org.springframework.beans.FatalBeanException: Can't resolve > reference to bean 'wrappedAssemblerTwo' while setting property > 'assembler' on bean 'logicOne'; nested exception is: > org.springframework.beans.FatalBeanException: Can't resolve > reference to bean 'assemblerTwo' while setting property 'target' on bean > 'wrappedAssemblerTwo'; nested exception is: > org.springframework.beans.FatalBeanException: Can't resolve > reference to bean 'logicTwo' while setting property 'logic' on bean > 'assemblerTwo'; nested exception is: > PropertyVetoExceptionsException: 1 errors:-- > ErrorCodedPropertyVetoException: message=[Failed to convert property > value of type [$Proxy0] to required type > [org.springframework.context.support.Assembler] for property named > 'assembler'; nested exception is: > java.lang.IllegalArgumentException: argument type mismatch]; > errorCode=[typeMismatch] > > Hope this provides more info on the issue? > > Alef > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Alef A. <al...@jt...> - 2003-12-16 11:22:26
|
Ok, the story continues. Juergen, I've added a test to the context.support package, ClasspathXmlApplicationContextTests. There are trhee contexts. B and C have to Logic beans in them. In A, there are two Assembler beans, that both assemble a Service bean (also defined in A) and a Logic bean (assemblerOne collaborates with logicOne, assemblerTwo collaborates with logicTwo). Both Assembler beans are wrapped by a TxProxyFactory (resulting in wrappedAssemblerOne and wrappedAssemblerTwo). These are also defined in A. Then - and that's the issue - logicOne depends on wrappedAssemblerTwo, logicTwo depends on wrappedAssemblerOne. This all goes well - until I let Assembler implement _any_ interface. Right now, I've commented out the implementation in Assembler of TestIF. Just uncomment it, run the test, and it'll fail. As it is located in the CVS, it'll succeed! It seems like the transactionmanager proxy does not implement all interface or something a like. Exception: Can't resolve reference to bean 'logicOne' while setting property 'logic' on bean 'assemblerOne'; nested exception is: org.springframework.beans.FatalBeanException: Can't resolve reference to bean 'wrappedAssemblerTwo' while setting property 'assembler' on bean 'logicOne'; nested exception is: org.springframework.beans.FatalBeanException: Can't resolve reference to bean 'assemblerTwo' while setting property 'target' on bean 'wrappedAssemblerTwo'; nested exception is: org.springframework.beans.FatalBeanException: Can't resolve reference to bean 'logicTwo' while setting property 'logic' on bean 'assemblerTwo'; nested exception is: PropertyVetoExceptionsException: 1 errors:-- ErrorCodedPropertyVetoException: message=[Failed to convert property value of type [$Proxy0] to required type [org.springframework.context.support.Assembler] for property named 'assembler'; nested exception is: java.lang.IllegalArgumentException: argument type mismatch]; errorCode=[typeMismatch] Hope this provides more info on the issue? Alef |
|
From: Andreas R. <ar...@gm...> - 2003-12-16 09:49:32
|
Hi, setApplicationContext() of an ApplicationContextAware bean is called behind of afterPropertiesSet. So it is not possible to load the referenced bean from within afterPropertiesSet. See AbstractBeanFactory line 518 - 520 Best regards Andy > Ah ok, so the afterPropertiesSet() is called *after* all the beans are > loaded and the setters are called, and the setApplicationContext() has > been called (in case my bean is ApplicationContextAware) so I can load the > referenced bean in the afterPropertiesSet() and do my initialization there? > > This will fix my issue i guess, thanx > > Joost > ----- Original Message ----- > From: Alef Arendsen > To: spr...@li... > Cc: Jo...@jt... > Sent: Tuesday, December 16, 2003 12:48 AM > Subject: RE: [Springframework-developer] Hibernate session and > ApplicationContext > > > > Suppose there's two app contexts, A and B. In A there's bean 1 > > > depending > > > > on bean 2 in B. In B, there's bean 3, depending on bean 4 in > > A. This is circular, however, I still want to somehow be able > > to do this. Basically the BeanFactory stops processing bean > > definitions if it can't find a bean reference that might be > > located in a sibbling context. I tend to state that the bean > > definition creation should postponed until all > > sibbling-contexts are resolved and maybe then try it again? > > Any suggestions (or just 'no not possible' will do as well :) > > > > This should be possible already. In case of multiple context > > definition files, all the bean definitions from all files get > > loaded first - *then* context initialization and bean > > pre-instantiation begins. The only thing that doesn't work, > > because it arguably can't work, is two FactoryBeans > > referencing each other. Can you give some details on what > > doesn't work in your scenario? > > I'll ask joost if I can't more details... He's probably got a couple of > example context files lying around... > > Alef -- |
|
From: Joost v. de W. \(JTeam\) <jo...@jt...> - 2003-12-16 09:38:09
|
QWggb2ssIHNvIHRoZSBhZnRlclByb3BlcnRpZXNTZXQoKSBpcyBjYWxsZWQgKmFmdGVyKiBhbGwg dGhlIGJlYW5zIGFyZSBsb2FkZWQNCmFuZCB0aGUgc2V0dGVycyBhcmUgY2FsbGVkLCBhbmQgdGhl IHNldEFwcGxpY2F0aW9uQ29udGV4dCgpIGhhcyAgYmVlbiBjYWxsZWQNCihpbiBjYXNlIG15IGJl YW4gaXMgQXBwbGljYXRpb25Db250ZXh0QXdhcmUpIHNvIEkgY2FuIGxvYWQgdGhlIHJlZmVyZW5j ZWQNCmJlYW4gaW4gdGhlIGFmdGVyUHJvcGVydGllc1NldCgpIGFuZCBkbyBteSBpbml0aWFsaXph dGlvbiB0aGVyZT8NCg0KVGhpcyB3aWxsIGZpeCBteSBpc3N1ZSBpIGd1ZXNzLCB0aGFueA0KDQpK b29zdA0KICAtLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KICBGcm9tOiBBbGVmIEFyZW5k c2VuIA0KICBUbzogc3ByaW5nZnJhbWV3b3JrLWRldmVsb3BlckBsaXN0cy5zb3VyY2Vmb3JnZS5u ZXQgDQogIENjOiBKb29zdEBqdGVhbS5ubCANCiAgU2VudDogVHVlc2RheSwgRGVjZW1iZXIgMTYs IDIwMDMgMTI6NDggQU0NCiAgU3ViamVjdDogUkU6IFtTcHJpbmdmcmFtZXdvcmstZGV2ZWxvcGVy XSBIaWJlcm5hdGUgc2Vzc2lvbiBhbmQgQXBwbGljYXRpb25Db250ZXh0DQoNCg0KICA+ID4gU3Vw cG9zZSB0aGVyZSdzIHR3byBhcHAgY29udGV4dHMsIEEgYW5kIEIuIEluIEEgdGhlcmUncyBiZWFu IDEgDQogID4gPiBkZXBlbmRpbmcNCiAgPiBvbiBiZWFuIDIgaW4gQi4gSW4gQiwgdGhlcmUncyBi ZWFuIDMsIGRlcGVuZGluZyBvbiBiZWFuIDQgaW4gDQogID4gQS4gVGhpcyBpcyBjaXJjdWxhciwg aG93ZXZlciwgSSBzdGlsbCB3YW50IHRvIHNvbWVob3cgYmUgYWJsZSANCiAgPiB0byBkbyB0aGlz LiBCYXNpY2FsbHkgdGhlIEJlYW5GYWN0b3J5IHN0b3BzIHByb2Nlc3NpbmcgYmVhbiANCiAgPiBk ZWZpbml0aW9ucyBpZiBpdCBjYW4ndCBmaW5kIGEgYmVhbiByZWZlcmVuY2UgdGhhdCBtaWdodCBi ZSANCiAgPiBsb2NhdGVkIGluIGEgc2liYmxpbmcgY29udGV4dC4gSSB0ZW5kIHRvIHN0YXRlIHRo YXQgdGhlIGJlYW4gDQogID4gZGVmaW5pdGlvbiBjcmVhdGlvbiBzaG91bGQgcG9zdHBvbmVkIHVu dGlsIGFsbCANCiAgPiBzaWJibGluZy1jb250ZXh0cyBhcmUgcmVzb2x2ZWQgYW5kIG1heWJlIHRo ZW4gdHJ5IGl0IGFnYWluPyANCiAgPiBBbnkgc3VnZ2VzdGlvbnMgKG9yIGp1c3QgJ25vIG5vdCBw b3NzaWJsZScgd2lsbCBkbyBhcyB3ZWxsIDopDQogID4gDQogID4gVGhpcyBzaG91bGQgYmUgcG9z c2libGUgYWxyZWFkeS4gSW4gY2FzZSBvZiBtdWx0aXBsZSBjb250ZXh0IA0KICA+IGRlZmluaXRp b24gZmlsZXMsIGFsbCB0aGUgYmVhbiBkZWZpbml0aW9ucyBmcm9tIGFsbCBmaWxlcyBnZXQgDQog ID4gbG9hZGVkIGZpcnN0IC0gKnRoZW4qIGNvbnRleHQgaW5pdGlhbGl6YXRpb24gYW5kIGJlYW4g DQogID4gcHJlLWluc3RhbnRpYXRpb24gYmVnaW5zLiBUaGUgb25seSB0aGluZyB0aGF0IGRvZXNu J3Qgd29yaywgDQogID4gYmVjYXVzZSBpdCBhcmd1YWJseSBjYW4ndCB3b3JrLCBpcyB0d28gRmFj dG9yeUJlYW5zIA0KICA+IHJlZmVyZW5jaW5nIGVhY2ggb3RoZXIuIENhbiB5b3UgZ2l2ZSBzb21l IGRldGFpbHMgb24gd2hhdCANCiAgPiBkb2Vzbid0IHdvcmsgaW4geW91ciBzY2VuYXJpbz8NCg0K ICBJJ2xsIGFzayBqb29zdCBpZiBJIGNhbid0IG1vcmUgZGV0YWlscy4uLiBIZSdzIHByb2JhYmx5 IGdvdCBhIGNvdXBsZSBvZg0KICBleGFtcGxlIGNvbnRleHQgZmlsZXMgbHlpbmcgYXJvdW5kLi4u DQoNCiAgQWxlZg0K |
|
From: Rod J. <rod...@in...> - 2003-12-16 09:28:52
|
I can update the CGLIB stuff whenever we choose to update. I guess that means now... I'll try to have a look at it this evening. ----- Original Message -----=20 From: "j=FCrgen h=F6ller [werk3AT]" <jue...@we...> To: <spr...@li...> Sent: Tuesday, December 16, 2003 9:15 AM Subject: Re: [Springframework-developer] Jar versions for m4 Currently, Hibernate 2.0.3 and CGLIB 1.0. We will switch to Hibernate 2.1 and CGLIB 2.0 for the official M4 release, to be released in the next cou= ple of days. BTW, Rod, what's the status on migrating our CglibAopProxy to CGLIB2? Juergen ________________________________ Von: spr...@li... im Auftrag von Ross Mason Gesendet: Di 16.12.2003 06:41 An: spr...@li... Betreff: [Springframework-developer] Jar versions for m4 Hi, What are the jar versions of hibernate and cglib being used to test spring M4? Cheers, Ross ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=3Dick _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: <jue...@we...> - 2003-12-16 09:18:31
|
Currently, Hibernate 2.0.3 and CGLIB 1.0. We will switch to Hibernate = 2.1 and CGLIB 2.0 for the official M4 release, to be released in the = next couple of days. =20 BTW, Rod, what's the status on migrating our CglibAopProxy to CGLIB2? =20 Juergen=20 =20 ________________________________ Von: spr...@li... im Auftrag = von Ross Mason Gesendet: Di 16.12.2003 06:41 An: spr...@li... Betreff: [Springframework-developer] Jar versions for m4 Hi, What are the jar versions of hibernate and cglib being used to test spring M4? Cheers, Ross ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's Free Linux Tutorials. Learn everything from the bash shell to sys = admin. Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Mike M. <mik...@ma...> - 2003-12-16 09:07:34
|
On Monday, December 15, 2003, at 09:09 pm, tri...@tr... wrote: > Quoting Mike Moran <mik...@ma...>: > >> 1 - Postgres 7.4 now claims to support status codes and the like on >> SQLException. Can Spring use these out-of-the-box or would a specific >> mapping hierarchy have to be written? > > Mike, > > I recently installed this version, so next step is obviously for me to > connect > and force an error to get a look at the error codes. Have you seen a > list of > what error codes they are using? [ ... ] I couldn't find any addressable javadoc for 7.4 online, but if you downloaded the 7.4 source tar.gz then it is in: src/interfaces/jdbc/org/postgresql/util/PSQLState.java src/interfaces/jdbc/org/postgresql/util/PSQLException.java I think the latest JDBC driver supports old databases as well as the 7.4 version so you'd have to allow for no SQLState in JDBC calls to them. Also, I've not checked whether the 1.3.1 compatible jdbc driver supports state, but from the jdbc.postgresql.org page it looks like it is works with 7.4, so it should. -- Mike |
|
From: Chris N. <ch...@si...> - 2003-12-16 06:18:37
|
jürgen höller [werk3AT] wrote: > That's good news! I didn't know that a CGLIB 1.1 release based on ASM 1.4 > was planned: That will indeed resolve the issues. I guess we can migrate > our AOP framework to CGLIB 2.0 now without any hassle! FYI CGLIB 1.1-RC1 and 2.0-RC2 are both available for download now. The new 2.0 release fixes some important bugs that exist in the jar currently shipping with Hibernate 2.1-Final, so I would not hesitate to update. Since you will for the time being be using CGLIB 1.1 and 2.0 together, I would also recommend that you include asm.jar separately. Here are download links for the three jars: http://prdownloads.sourceforge.net/cglib/cglib-2.0-RC2.jar?download http://prdownloads.sourceforge.net/cglib/cglib-1.1-RC1.jar?download http://forge.objectweb.org/project/download.php?group_id=23&file_id=1349 Even if you do not upgrade to Hibernate 2.1 I would still recommend using CGLIB 1.1 instead of 1.0, since it will allow your users to use CGLIB 2.0 for their own code. Chris |
|
From: <tri...@tr...> - 2003-12-16 05:50:56
|
Quoting Mike Moran <mik...@ma...>:
> 1 - Postgres 7.4 now claims to support status codes and the like on
> SQLException. Can Spring use these out-of-the-box or would a specific
> mapping hierarchy have to be written?
Mike,
I recently installed this version, so next step is obviously for me to connect
and force an error to get a look at the error codes. Have you seen a list of
what error codes they are using? We should be able to map their codes to our
exception hierarchy the way we do it for other databases. This is something we
should do before RC1 - doubt we will have time before M4.
Now for something completely different:
I have recently added support for updatable result sets in a class called
org.springframework.jdbc.object.UpdatableSqlQuery. It is used the same way as
the MappingSqlQuery, except that you override updateRow() instead of mapRow()
and in the query.execute you pass in a Map that can be used to look up values
for the update. My example uses the primary key as the lookup value in a HashMap.
Example:
class CustomerUpdateQuery extends UpdatableSqlQuery {
public CustomerUpdateQuery(DataSource ds) {
super(ds, "SELECT ID, NAME WHERE ID < ?");
declareParameter(new SqlParameter(Types.NUMERIC));
compile();
}
protected Object updateRow(ResultSet rs, int rownum, Map context)
throws SQLException {
rs.updateString(2, (String) context.get(new Integer(rs.getInt("ID"))));
return null; // we can create an object if we want to return something
}
};
CustomerUpdateQuery query = new CustomerUpdateQuery(dataSource);
Map values = new HashMap(2);
values.put(new Integer(1), "Rod");
values.put(new Integer(2), "Thomas");
query.execute(2, values);
Thomas
|
|
From: Ross M. <ro...@at...> - 2003-12-16 05:41:43
|
Hi, What are the jar versions of hibernate and cglib being used to test spring M4? Cheers, Ross |
|
From: Ross M. <ro...@at...> - 2003-12-16 04:59:29
|
Hi, I'm working with a a spring jar built from the latest source and I keep getting the following exception - java.lang.VerifyError: (class: org/springframework/orm/hibernate/SessionFactoryUtils, method: convertHibernateAccessException signature: (Lnet/sf/hibernate/HibernateException;)Lorg/springframework/dao/DataAccessException;) Incompatible object argument for function call at org.springframework.orm.hibernate.support.OpenSessionInViewFilter.getSession(OpenSessionInViewFilter.java:118) at org.springframework.orm.hibernate.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:80) at com.atlassian.confluence.setup.SessionInViewFilter.doFilterInternal(SessionInViewFilter.java:26) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:39) at com.caucho.server.http.FilterChainFilter.doFilter(FilterChainFilter.java:88) at com.atlassian.util.profiling.filters.ProfilingFilter.doFilter(ProfilingFilter.java:148) at com.caucho.server.http.FilterChainFilter.doFilter(FilterChainFilter.java:88) at com.atlassian.core.filters.AbstractEncodingFilter.doFilter(AbstractEncodingFilter.java:38) at com.caucho.server.http.FilterChainFilter.doFilter(FilterChainFilter.java:88) at com.caucho.server.http.Invocation.service(Invocation.java:315) at com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:246) at com.caucho.server.http.HttpRequest.handleConnection(HttpRequest.java:164) at com.caucho.server.TcpConnection.run(TcpConnection.java:139) at java.lang.Thread.run(Thread.java:534) I've rebuilt the jar a couple of times but always get the same problem. Is anyone else doing this? Does anyone have a 'happy' spring-1.0-m4-dev.jar I could get hold of? Cheers, Ross |
|
From: Ross M. <ro...@at...> - 2003-12-16 02:39:03
|
Ok mate, sounds like it's time for you to hit the sack. BTW What's the book? you can tell me in the morning ;-) Cheers, Ross j=FCrgen h=F6ller [werk3AT] wrote: > I could have thought of that if it wasn't already so late (3:20 in the = morning now). Yes, that's a known limitation: If you proxy an object, bot= h the proxy and the target object will match the type. You need to resort= to explicit references for such beans - as I said, this will even work f= or specific references if you apply autowire-by-type in general. > =20 > BTW, have I mentioned that writing a book is *damn hard work*? ;-) > =20 > Juergen > =20 >=20 > ________________________________ >=20 > Von: spr...@li... im Auftrag v= on Ross Mason > Gesendet: Di 16.12.2003 02:23 > An: spr...@li... > Betreff: Re: [Springframework-developer] Refreshing the ApplicationCont= ext... >=20 >=20 >=20 > Hi j=FCrgen, >=20 > When I run getBeansOfType() on our config (turning off autowireByType) = I > do get two beans returned: > - I get the emialTemplateManager as expected (this is a proxy > org.springframework.transaction.interceptor.TransactionProxyFactoryBean= ). > - I also get back our emailTemplateManagerTarget which is our proxied > object. >=20 > This suggests you can't use autowireByType when using > TransactionProxyFactoryBean or any other ProxyFactoryBean. Is this > intended behaviour? >=20 > Cheers, >=20 > Ross >=20 >=20 > j=FCrgen h=F6ller [werk3AT] wrote: >=20 >=20 >>Ross, >> >>If you build a single context from multiple files, autowiring will auto= matically scan all the bean definitions in those files. In your case, I a= ssume that you do have multiple definitions of type EmailTemplateManager,= possibly in two different context files. You could check that programmat= ically by examining the result of ApplicationContext.getBeansOfType(Email= TemplateManager.class, true, true). >> >>In any case, even if you apply autowiring in general, you can always ov= erride a specific dependency, like an explicit bean reference from proper= ty "emailTemplateManager" of bean "notifierCreatePage" to a specific bean= of type EmailTemplateManager: >> >><bean id=3D"notifierCreatePage" class=3D"..." autowire=3D"byType"> >> <property name=3D"emailTemplateManager"><ref bean=3D"myEmailTemplateM= anager"/></property> >> ... >></bean> >> >>Juergen >> >> >>________________________________ >> >>Von: spr...@li... im Auftrag v= on Ross Mason >>Gesendet: Di 16.12.2003 01:00 >>An: spr...@li... >>Betreff: Re: [Springframework-developer] Refreshing the ApplicationCont= ext... >> >> >> >>Hi j=FCrgen, >> >>We were using refresh as we needed to defer the initialisation of the >>String container the first time our app is run until the user has setup >>their db settings, at which point we initialise the container. After >>that, if/when the server is restarted we use your ContextLoaderListener >>is used to initialise the container. >> >>I think I've just realised what the problem is. We have 3 >>applicationContexts and the bean causing the error is defined in a >>different context. Is there a way to autowire over multiple contexts? >> >>If this is the case, the exception for this scenario is a bit misleadin= g >>as it tells me there is more than one satifiable dependency. >> >>The exception we get is - >>org.springframework.beans.FatalBeanException: Can't resolve reference t= o >>bean 'notifierCreatePage' while setting property 'listeners[0]' on bean >>'producerCreatePage'; nested exception is: >>org.springframework.beans.factory.UnsatisfiedDependencyException: Bean >>with name 'notifierCreatePage' has an unsatisfied dependency expressed >>through property 'emailTemplateManager': set this property value or >>disable dependency checking for this bean; detail message =3D [There ar= e 2 >>beans of type [interface >>com.atlassian.confluence.mail.template.EmailTemplateManager] for >>autowire by type. There should have been 1 to be able to autowire >>property 'emailTemplateManager' of bean 'notifierCreatePage'.] >>(This is very informative excetion BTW ;-)) >> >>Cheers, >> >>Ross >> >> >>j=FCrgen h=F6ller [werk3AT] wrote: >> >> >> >>>Hi Ross, >>> >>>"refresh" is now in ConfigurableApplicationContext, but you shouldn't = need that for typical usages anyway. I guess what you're trying to do is = custom initialization of the root WebApplicationContext, storing it in a = custom place via the setApplicationContext call. That should be fine: I s= uppose that the error you're getting has other origins. Autowiring has be= en significantly reworked; could you check for which components you get m= ore than one matching bean? The reason could be that you actually *have* = multiple matching beans, which just weren't found by M2's autowire implem= entation, maybe due to being created by FactoryBeans. Could you quote rel= evant parts of your configuration? >>> >>>Juergen >>> >>> >>>________________________________ >>> >>>Von: spr...@li... im Auftrag = von Ross Mason >>>Gesendet: Mo 15.12.2003 07:50 >>>An: spr...@li... >>>Betreff: [Springframework-developer] Refreshing the ApplicationContext= ... >>> >>> >>> >>>Hi, >>> >>>In the latest source the ApplicationContext.refresh() method has been >>>removed. What is the recommended way of refreshing an >>>applicationContext now. I'm trying - >>> >>> ContextLoader loader =3D new ContextLoader(); >>> setApplicationContext( >>>loader.initWebApplicationContext(servletContext) ); >>> >>>But I am getting an error saying that there is more than one matching >>>bean on some components when autoWiring by type. Our code and cofig >>>works fine with M2 release, but we're mored to the latest source to ma= ke >>>use of the OpenSessionInViewFilter. >>> >>>Any ideas? >>> >>> >>>Cheers, >>> >>>Ross >>> >>> >>> >>>------------------------------------------------------- >>>This SF.net email is sponsored by: IBM Linux Tutorials. >>>Become an expert in LINUX or just sharpen your skills. Sign up for IB= M's >>>Free Linux Tutorials. Learn everything from the bash shell to sys adm= in. >>>Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclic= 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. >>>Become an expert in LINUX or just sharpen your skills. Sign up for IB= M's >>>Free Linux Tutorials. Learn everything from the bash shell to sys adm= in. >>>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&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. >>Become an expert in LINUX or just sharpen your skills. Sign up for IBM= 's >>Free Linux Tutorials. Learn everything from the bash shell to sys admi= n. >>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&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. >>Become an expert in LINUX or just sharpen your skills. Sign up for IBM= 's >>Free Linux Tutorials. Learn everything from the bash shell to sys admi= n. >>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=CCk >>_______________________________________________ >>Springframework-developer mailing list >>Spr...@li... >>https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM= 's > Free Linux Tutorials. Learn everything from the bash shell to sys admi= n. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=3Dick > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM= 's > Free Linux Tutorials. Learn everything from the bash shell to sys admi= n. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=CCk > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer >=20 |
|
From: <jue...@we...> - 2003-12-16 02:26:04
|
I could have thought of that if it wasn't already so late (3:20 in the = morning now). Yes, that's a known limitation: If you proxy an object, = both the proxy and the target object will match the type. You need to = resort to explicit references for such beans - as I said, this will even = work for specific references if you apply autowire-by-type in general. =20 BTW, have I mentioned that writing a book is *damn hard work*? ;-) =20 Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von Ross Mason Gesendet: Di 16.12.2003 02:23 An: spr...@li... Betreff: Re: [Springframework-developer] Refreshing the = ApplicationContext... Hi j=FCrgen, When I run getBeansOfType() on our config (turning off autowireByType) I do get two beans returned: - I get the emialTemplateManager as expected (this is a proxy org.springframework.transaction.interceptor.TransactionProxyFactoryBean).= - I also get back our emailTemplateManagerTarget which is our proxied object. This suggests you can't use autowireByType when using TransactionProxyFactoryBean or any other ProxyFactoryBean. Is this intended behaviour? Cheers, Ross j=FCrgen h=F6ller [werk3AT] wrote: > Ross, >=20 > If you build a single context from multiple files, autowiring will = automatically scan all the bean definitions in those files. In your = case, I assume that you do have multiple definitions of type = EmailTemplateManager, possibly in two different context files. You could = check that programmatically by examining the result of = ApplicationContext.getBeansOfType(EmailTemplateManager.class, true, = true). >=20 > In any case, even if you apply autowiring in general, you can always = override a specific dependency, like an explicit bean reference from = property "emailTemplateManager" of bean "notifierCreatePage" to a = specific bean of type EmailTemplateManager: >=20 > <bean id=3D"notifierCreatePage" class=3D"..." autowire=3D"byType"> > <property name=3D"emailTemplateManager"><ref = bean=3D"myEmailTemplateManager"/></property> > ... > </bean> >=20 > Juergen >=20 > > ________________________________ > > Von: spr...@li... im Auftrag = von Ross Mason > Gesendet: Di 16.12.2003 01:00 > An: spr...@li... > Betreff: Re: [Springframework-developer] Refreshing the = ApplicationContext... > > > > Hi j=FCrgen, > > We were using refresh as we needed to defer the initialisation of the > String container the first time our app is run until the user has = setup > their db settings, at which point we initialise the container. After > that, if/when the server is restarted we use your = ContextLoaderListener > is used to initialise the container. > > I think I've just realised what the problem is. We have 3 > applicationContexts and the bean causing the error is defined in a > different context. Is there a way to autowire over multiple contexts? > > If this is the case, the exception for this scenario is a bit = misleading > as it tells me there is more than one satifiable dependency. > > The exception we get is - > org.springframework.beans.FatalBeanException: Can't resolve reference = to > bean 'notifierCreatePage' while setting property 'listeners[0]' on = bean > 'producerCreatePage'; nested exception is: > org.springframework.beans.factory.UnsatisfiedDependencyException: Bean > with name 'notifierCreatePage' has an unsatisfied dependency expressed > through property 'emailTemplateManager': set this property value or > disable dependency checking for this bean; detail message =3D [There = are 2 > beans of type [interface > com.atlassian.confluence.mail.template.EmailTemplateManager] for > autowire by type. There should have been 1 to be able to autowire > property 'emailTemplateManager' of bean 'notifierCreatePage'.] > (This is very informative excetion BTW ;-)) > > Cheers, > > Ross > > > j=FCrgen h=F6ller [werk3AT] wrote: > > >>Hi Ross, >> >>"refresh" is now in ConfigurableApplicationContext, but you shouldn't = need that for typical usages anyway. I guess what you're trying to do is = custom initialization of the root WebApplicationContext, storing it in a = custom place via the setApplicationContext call. That should be fine: I = suppose that the error you're getting has other origins. Autowiring has = been significantly reworked; could you check for which components you = get more than one matching bean? The reason could be that you actually = *have* multiple matching beans, which just weren't found by M2's = autowire implementation, maybe due to being created by FactoryBeans. = Could you quote relevant parts of your configuration? >> >>Juergen >> >> >>________________________________ >> >>Von: spr...@li... im Auftrag = von Ross Mason >>Gesendet: Mo 15.12.2003 07:50 >>An: spr...@li... >>Betreff: [Springframework-developer] Refreshing the = ApplicationContext... >> >> >> >>Hi, >> >>In the latest source the ApplicationContext.refresh() method has been >>removed. What is the recommended way of refreshing an >>applicationContext now. I'm trying - >> >> ContextLoader loader =3D new ContextLoader(); >> setApplicationContext( >>loader.initWebApplicationContext(servletContext) ); >> >>But I am getting an error saying that there is more than one matching >>bean on some components when autoWiring by type. Our code and cofig >>works fine with M2 release, but we're mored to the latest source to = make >>use of the OpenSessionInViewFilter. >> >>Any ideas? >> >> >>Cheers, >> >>Ross >> >> >> >>------------------------------------------------------- >>This SF.net email is sponsored by: IBM Linux Tutorials. >>Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's >>Free Linux Tutorials. Learn everything from the bash shell to sys = admin. >>Click now! = http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick >>_______________________________________________ >>Springframework-developer mailing list >>Spr...@li... >>https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> >> >> >>------------------------------------------------------- >>This SF.net email is sponsored by: IBM Linux Tutorials. >>Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's >>Free Linux Tutorials. Learn everything from the bash shell to sys = admin. >>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&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. > Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys = admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&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. > Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys = admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&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. Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's Free Linux Tutorials. Learn everything from the bash shell to sys = admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=3Dick _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Ross M. <ro...@at...> - 2003-12-16 01:23:06
|
Hi j=FCrgen, When I run getBeansOfType() on our config (turning off autowireByType) I=20 do get two beans returned: - I get the emialTemplateManager as expected (this is a proxy=20 org.springframework.transaction.interceptor.TransactionProxyFactoryBean). - I also get back our emailTemplateManagerTarget which is our proxied=20 object. This suggests you can't use autowireByType when using=20 TransactionProxyFactoryBean or any other ProxyFactoryBean. Is this=20 intended behaviour? Cheers, Ross j=FCrgen h=F6ller [werk3AT] wrote: > Ross, > =20 > If you build a single context from multiple files, autowiring will auto= matically scan all the bean definitions in those files. In your case, I a= ssume that you do have multiple definitions of type EmailTemplateManager,= possibly in two different context files. You could check that programmat= ically by examining the result of ApplicationContext.getBeansOfType(Email= TemplateManager.class, true, true). > =20 > In any case, even if you apply autowiring in general, you can always ov= erride a specific dependency, like an explicit bean reference from proper= ty "emailTemplateManager" of bean "notifierCreatePage" to a specific bean= of type EmailTemplateManager: > =20 > <bean id=3D"notifierCreatePage" class=3D"..." autowire=3D"byType"> > <property name=3D"emailTemplateManager"><ref bean=3D"myEmailTemplateM= anager"/></property> > ... > </bean> > =20 > Juergen > =20 >=20 > ________________________________ >=20 > Von: spr...@li... im Auftrag v= on Ross Mason > Gesendet: Di 16.12.2003 01:00 > An: spr...@li... > Betreff: Re: [Springframework-developer] Refreshing the ApplicationCont= ext... >=20 >=20 >=20 > Hi j=FCrgen, >=20 > We were using refresh as we needed to defer the initialisation of the > String container the first time our app is run until the user has setup > their db settings, at which point we initialise the container. After > that, if/when the server is restarted we use your ContextLoaderListener > is used to initialise the container. >=20 > I think I've just realised what the problem is. We have 3 > applicationContexts and the bean causing the error is defined in a > different context. Is there a way to autowire over multiple contexts? >=20 > If this is the case, the exception for this scenario is a bit misleadin= g > as it tells me there is more than one satifiable dependency. >=20 > The exception we get is - > org.springframework.beans.FatalBeanException: Can't resolve reference t= o > bean 'notifierCreatePage' while setting property 'listeners[0]' on bean > 'producerCreatePage'; nested exception is: > org.springframework.beans.factory.UnsatisfiedDependencyException: Bean > with name 'notifierCreatePage' has an unsatisfied dependency expressed > through property 'emailTemplateManager': set this property value or > disable dependency checking for this bean; detail message =3D [There ar= e 2 > beans of type [interface > com.atlassian.confluence.mail.template.EmailTemplateManager] for > autowire by type. There should have been 1 to be able to autowire > property 'emailTemplateManager' of bean 'notifierCreatePage'.] > (This is very informative excetion BTW ;-)) >=20 > Cheers, >=20 > Ross >=20 >=20 > j=FCrgen h=F6ller [werk3AT] wrote: >=20 >=20 >>Hi Ross, >> >>"refresh" is now in ConfigurableApplicationContext, but you shouldn't n= eed that for typical usages anyway. I guess what you're trying to do is c= ustom initialization of the root WebApplicationContext, storing it in a c= ustom place via the setApplicationContext call. That should be fine: I su= ppose that the error you're getting has other origins. Autowiring has bee= n significantly reworked; could you check for which components you get mo= re than one matching bean? The reason could be that you actually *have* m= ultiple matching beans, which just weren't found by M2's autowire impleme= ntation, maybe due to being created by FactoryBeans. Could you quote rele= vant parts of your configuration? >> >>Juergen >> >> >>________________________________ >> >>Von: spr...@li... im Auftrag v= on Ross Mason >>Gesendet: Mo 15.12.2003 07:50 >>An: spr...@li... >>Betreff: [Springframework-developer] Refreshing the ApplicationContext.= .. >> >> >> >>Hi, >> >>In the latest source the ApplicationContext.refresh() method has been >>removed. What is the recommended way of refreshing an >>applicationContext now. I'm trying - >> >> ContextLoader loader =3D new ContextLoader(); >> setApplicationContext( >>loader.initWebApplicationContext(servletContext) ); >> >>But I am getting an error saying that there is more than one matching >>bean on some components when autoWiring by type. Our code and cofig >>works fine with M2 release, but we're mored to the latest source to mak= e >>use of the OpenSessionInViewFilter. >> >>Any ideas? >> >> >>Cheers, >> >>Ross >> >> >> >>------------------------------------------------------- >>This SF.net email is sponsored by: IBM Linux Tutorials. >>Become an expert in LINUX or just sharpen your skills. Sign up for IBM= 's >>Free Linux Tutorials. Learn everything from the bash shell to sys admi= n. >>Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick >>_______________________________________________ >>Springframework-developer mailing list >>Spr...@li... >>https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> >> >> >>------------------------------------------------------- >>This SF.net email is sponsored by: IBM Linux Tutorials. >>Become an expert in LINUX or just sharpen your skills. Sign up for IBM= 's >>Free Linux Tutorials. Learn everything from the bash shell to sys admi= n. >>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=CCk >>_______________________________________________ >>Springframework-developer mailing list >>Spr...@li... >>https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM= 's > Free Linux Tutorials. Learn everything from the bash shell to sys admi= n. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=3Dick > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM= 's > Free Linux Tutorials. Learn everything from the bash shell to sys admi= n. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=CCk > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer >=20 |
|
From: <jue...@we...> - 2003-12-16 00:49:32
|
Ross, =20 If you build a single context from multiple files, autowiring will = automatically scan all the bean definitions in those files. In your = case, I assume that you do have multiple definitions of type = EmailTemplateManager, possibly in two different context files. You could = check that programmatically by examining the result of = ApplicationContext.getBeansOfType(EmailTemplateManager.class, true, = true). =20 In any case, even if you apply autowiring in general, you can always = override a specific dependency, like an explicit bean reference from = property "emailTemplateManager" of bean "notifierCreatePage" to a = specific bean of type EmailTemplateManager: =20 <bean id=3D"notifierCreatePage" class=3D"..." autowire=3D"byType"> <property name=3D"emailTemplateManager"><ref = bean=3D"myEmailTemplateManager"/></property> ... </bean> =20 Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von Ross Mason Gesendet: Di 16.12.2003 01:00 An: spr...@li... Betreff: Re: [Springframework-developer] Refreshing the = ApplicationContext... Hi j=FCrgen, We were using refresh as we needed to defer the initialisation of the String container the first time our app is run until the user has setup their db settings, at which point we initialise the container. After that, if/when the server is restarted we use your ContextLoaderListener is used to initialise the container. I think I've just realised what the problem is. We have 3 applicationContexts and the bean causing the error is defined in a different context. Is there a way to autowire over multiple contexts? If this is the case, the exception for this scenario is a bit misleading as it tells me there is more than one satifiable dependency. The exception we get is - org.springframework.beans.FatalBeanException: Can't resolve reference to bean 'notifierCreatePage' while setting property 'listeners[0]' on bean 'producerCreatePage'; nested exception is: org.springframework.beans.factory.UnsatisfiedDependencyException: Bean with name 'notifierCreatePage' has an unsatisfied dependency expressed through property 'emailTemplateManager': set this property value or disable dependency checking for this bean; detail message =3D [There are = 2 beans of type [interface com.atlassian.confluence.mail.template.EmailTemplateManager] for autowire by type. There should have been 1 to be able to autowire property 'emailTemplateManager' of bean 'notifierCreatePage'.] (This is very informative excetion BTW ;-)) Cheers, Ross j=FCrgen h=F6ller [werk3AT] wrote: > Hi Ross, >=20 > "refresh" is now in ConfigurableApplicationContext, but you shouldn't = need that for typical usages anyway. I guess what you're trying to do is = custom initialization of the root WebApplicationContext, storing it in a = custom place via the setApplicationContext call. That should be fine: I = suppose that the error you're getting has other origins. Autowiring has = been significantly reworked; could you check for which components you = get more than one matching bean? The reason could be that you actually = *have* multiple matching beans, which just weren't found by M2's = autowire implementation, maybe due to being created by FactoryBeans. = Could you quote relevant parts of your configuration? >=20 > Juergen >=20 > > ________________________________ > > Von: spr...@li... im Auftrag = von Ross Mason > Gesendet: Mo 15.12.2003 07:50 > An: spr...@li... > Betreff: [Springframework-developer] Refreshing the = ApplicationContext... > > > > Hi, > > In the latest source the ApplicationContext.refresh() method has been > removed. What is the recommended way of refreshing an > applicationContext now. I'm trying - > > ContextLoader loader =3D new ContextLoader(); > setApplicationContext( > loader.initWebApplicationContext(servletContext) ); > > But I am getting an error saying that there is more than one matching > bean on some components when autoWiring by type. Our code and cofig > works fine with M2 release, but we're mored to the latest source to = make > use of the OpenSessionInViewFilter. > > Any ideas? > > > Cheers, > > Ross > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys = admin. > Click now! = http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys = admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&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. Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's Free Linux Tutorials. Learn everything from the bash shell to sys = admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=3Dick _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Ross M. <ro...@at...> - 2003-12-16 00:00:14
|
Hi j=FCrgen, We were using refresh as we needed to defer the initialisation of the=20 String container the first time our app is run until the user has setup=20 their db settings, at which point we initialise the container. After=20 that, if/when the server is restarted we use your ContextLoaderListener=20 is used to initialise the container. I think I've just realised what the problem is. We have 3=20 applicationContexts and the bean causing the error is defined in a=20 different context. Is there a way to autowire over multiple contexts? If this is the case, the exception for this scenario is a bit misleading=20 as it tells me there is more than one satifiable dependency. The exception we get is - org.springframework.beans.FatalBeanException: Can't resolve reference to=20 bean 'notifierCreatePage' while setting property 'listeners[0]' on bean=20 'producerCreatePage'; nested exception is:=20 org.springframework.beans.factory.UnsatisfiedDependencyException: Bean=20 with name 'notifierCreatePage' has an unsatisfied dependency expressed=20 through property 'emailTemplateManager': set this property value or=20 disable dependency checking for this bean; detail message =3D [There are = 2=20 beans of type [interface=20 com.atlassian.confluence.mail.template.EmailTemplateManager] for=20 autowire by type. There should have been 1 to be able to autowire=20 property 'emailTemplateManager' of bean 'notifierCreatePage'.] (This is very informative excetion BTW ;-)) Cheers, Ross j=FCrgen h=F6ller [werk3AT] wrote: > Hi Ross, > =20 > "refresh" is now in ConfigurableApplicationContext, but you shouldn't n= eed that for typical usages anyway. I guess what you're trying to do is c= ustom initialization of the root WebApplicationContext, storing it in a c= ustom place via the setApplicationContext call. That should be fine: I su= ppose that the error you're getting has other origins. Autowiring has bee= n significantly reworked; could you check for which components you get mo= re than one matching bean? The reason could be that you actually *have* m= ultiple matching beans, which just weren't found by M2's autowire impleme= ntation, maybe due to being created by FactoryBeans. Could you quote rele= vant parts of your configuration? > =20 > Juergen > =20 >=20 > ________________________________ >=20 > Von: spr...@li... im Auftrag v= on Ross Mason > Gesendet: Mo 15.12.2003 07:50 > An: spr...@li... > Betreff: [Springframework-developer] Refreshing the ApplicationContext.= .. >=20 >=20 >=20 > Hi, >=20 > In the latest source the ApplicationContext.refresh() method has been > removed. What is the recommended way of refreshing an > applicationContext now. I'm trying - >=20 > ContextLoader loader =3D new ContextLoader(); > setApplicationContext( > loader.initWebApplicationContext(servletContext) ); >=20 > But I am getting an error saying that there is more than one matching > bean on some components when autoWiring by type. Our code and cofig > works fine with M2 release, but we're mored to the latest source to mak= e > use of the OpenSessionInViewFilter. >=20 > Any ideas? >=20 >=20 > Cheers, >=20 > Ross >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM= 's > Free Linux Tutorials. Learn everything from the bash shell to sys admi= n. > Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM= 's > Free Linux Tutorials. Learn everything from the bash shell to sys admi= n. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=CCk > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer >=20 |
|
From: Alef A. <al...@jt...> - 2003-12-15 23:49:00
|
> > Suppose there's two app contexts, A and B. In A there's bean 1 > > depending > on bean 2 in B. In B, there's bean 3, depending on bean 4 in > A. This is circular, however, I still want to somehow be able > to do this. Basically the BeanFactory stops processing bean > definitions if it can't find a bean reference that might be > located in a sibbling context. I tend to state that the bean > definition creation should postponed until all > sibbling-contexts are resolved and maybe then try it again? > Any suggestions (or just 'no not possible' will do as well :) > > This should be possible already. In case of multiple context > definition files, all the bean definitions from all files get > loaded first - *then* context initialization and bean > pre-instantiation begins. The only thing that doesn't work, > because it arguably can't work, is two FactoryBeans > referencing each other. Can you give some details on what > doesn't work in your scenario? I'll ask joost if I can't more details... He's probably got a couple of example context files lying around... Alef |
|
From: <jue...@we...> - 2003-12-15 23:43:08
|
Alef, =20 > Suppose there's two app contexts, A and B. In A there's bean 1 = depending on bean 2 in B. In B, there's bean 3, depending on bean 4 in A. This is circular, however, I still want to somehow be able to do this. Basically the BeanFactory stops processing bean definitions if it can't find a bean reference that might be located in a sibbling context. I tend to state that the bean definition creation should postponed until all sibbling-contexts are resolved and maybe then try it again? Any suggestions (or just 'no not possible' will do as well :) This should be possible already. In case of multiple context definition = files, all the bean definitions from all files get loaded first - *then* = context initialization and bean pre-instantiation begins. The only thing = that doesn't work, because it arguably can't work, is two FactoryBeans = referencing each other. Can you give some details on what doesn't work = in your scenario? =20 Juergen =20 |
|
From: Alef A. <al...@jt...> - 2003-12-15 23:09:19
|
All, Two questions. First of all, we're having an app here based on some proprietary tech that we've wrapped in Spring. It's transparently using either POJOs or EJBs (when using EJBs the POJOs are just wrapped by en EJB, thus enabling easy clustering and more stuff like that). However, we're using the HibernateSessionFactory and don't know when to close the session when using an EJBs instead of POJOs. I found this solution on hibernate website in the documentation about spring combined with hibernate (having a ThreadLocal threadcounter that you're increasing and decreasing everytime a different EJB is entered or left). But it doesn't sounds like a decent approach (Chris Bauer - I guess - also advised against it). I could use long transactions, but that's a hassle as well. So anybody has any opinions on how to keep track of when to close the session when doing for one web-call that does an ejb-call that does another ejb-call (both of which do something hibsession related)? Ok, the second one involves the ApplicationContext. I've divided my beans across a lot of files (in order to keep them modular) and I'm loading them in all different kinds of places using the for example the ClasspathAppCtx (and providing it with an array of context locations). However, it's difficult avoiding circular references! Suppose there's two app contexts, A and B. In A there's bean 1 depending on bean 2 in B. In B, there's bean 3, depending on bean 4 in A. This is circular, however, I still want to somehow be able to do this. Basically the BeanFactory stops processing bean definitions if it can't find a bean reference that might be located in a sibbling context. I tend to state that the bean definition creation should postponed until all sibbling-contexts are resolved and maybe then try it again? Any suggestions (or just 'no not possible' will do as well :) Alef |
|
From: Rod J. <rod...@in...> - 2003-12-15 15:48:18
|
It must be. The current Commons Attributes code in CVS--which I had to check out to figure out how it works in the absence of decent documentation--uses XJavadoc. ----- Original Message ----- From: "Colin Sampaleanu" <col...@ex...> To: <spr...@li...> Sent: Monday, December 15, 2003 3:38 PM Subject: Re: [Springframework-developer] Attributes > Rod, > > Is this an older version of the attributes code? The dep info at Apache > lists qdox: > http://jakarta.apache.org/commons/sandbox/attributes/dependencies.html > > > Rod Johnson wrote: > > >The tests now depend on a Commons Attributes precompile step. However, this > >doesn't take very long at all as it applies only to one package. > > > >However, you will need to put the following files in your $ANT_HOME/lib to > >get the tests to run: > > > >- Commons Attributes compiler Jar (in CVS) > >- commons-collections.jar (in CVS) > >- xjavadoc.jar (from XDoclet project). I'm not sure whether to put this in > >CVS as none of our code uses it. Thoughts? > > > >For now, I've named the attributes-dependent test case so that Eclipse won't > >pick up. I'll change this when I get time so that the build is also > >triggered under Eclipse. > > > >Regards, > >Rod > > > > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer |