You can subscribe to this list here.
| 2003 |
Jan
|
Feb
(55) |
Mar
(100) |
Apr
(203) |
May
(330) |
Jun
(190) |
Jul
(302) |
Aug
(323) |
Sep
(197) |
Oct
(245) |
Nov
(490) |
Dec
(330) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(194) |
Feb
(400) |
Mar
(416) |
Apr
(415) |
May
(359) |
Jun
(381) |
Jul
(491) |
Aug
(311) |
Sep
(291) |
Oct
(273) |
Nov
(355) |
Dec
(266) |
| 2005 |
Jan
(306) |
Feb
(303) |
Mar
(520) |
Apr
(346) |
May
(255) |
Jun
(221) |
Jul
(171) |
Aug
(247) |
Sep
(147) |
Oct
(125) |
Nov
(165) |
Dec
(65) |
| 2006 |
Jan
(90) |
Feb
(53) |
Mar
(121) |
Apr
(103) |
May
(113) |
Jun
(103) |
Jul
(104) |
Aug
(67) |
Sep
(78) |
Oct
(82) |
Nov
(78) |
Dec
(70) |
| 2007 |
Jan
(77) |
Feb
(76) |
Mar
(63) |
Apr
(30) |
May
(47) |
Jun
(41) |
Jul
(44) |
Aug
(44) |
Sep
(49) |
Oct
(33) |
Nov
(25) |
Dec
(21) |
| 2008 |
Jan
(45) |
Feb
(13) |
Mar
(15) |
Apr
(12) |
May
(9) |
Jun
(33) |
Jul
(30) |
Aug
(7) |
Sep
(20) |
Oct
(17) |
Nov
(20) |
Dec
(10) |
| 2009 |
Jan
(8) |
Feb
(5) |
Mar
(12) |
Apr
(17) |
May
(19) |
Jun
(97) |
Jul
(77) |
Aug
(33) |
Sep
(24) |
Oct
(41) |
Nov
(16) |
Dec
(32) |
| 2010 |
Jan
(24) |
Feb
(14) |
Mar
(50) |
Apr
(71) |
May
(70) |
Jun
(64) |
Jul
(45) |
Aug
(62) |
Sep
(32) |
Oct
(4) |
Nov
(12) |
Dec
(2) |
| 2011 |
Jan
(1) |
Feb
(3) |
Mar
(4) |
Apr
(3) |
May
(6) |
Jun
(1) |
Jul
(4) |
Aug
(3) |
Sep
(4) |
Oct
(6) |
Nov
(3) |
Dec
(3) |
| 2012 |
Jan
(4) |
Feb
(8) |
Mar
(6) |
Apr
(10) |
May
(2) |
Jun
(3) |
Jul
(11) |
Aug
(10) |
Sep
(4) |
Oct
|
Nov
(1) |
Dec
(1) |
| 2013 |
Jan
(4) |
Feb
(1) |
Mar
(9) |
Apr
(1) |
May
(8) |
Jun
(2) |
Jul
(5) |
Aug
(2) |
Sep
|
Oct
(3) |
Nov
(10) |
Dec
(8) |
| 2014 |
Jan
(3) |
Feb
(12) |
Mar
(9) |
Apr
(12) |
May
(2) |
Jun
|
Jul
(3) |
Aug
(1) |
Sep
(1) |
Oct
(4) |
Nov
|
Dec
(2) |
| 2015 |
Jan
(1) |
Feb
(3) |
Mar
(4) |
Apr
(9) |
May
(2) |
Jun
(2) |
Jul
|
Aug
(2) |
Sep
(7) |
Oct
(9) |
Nov
(7) |
Dec
(9) |
| 2016 |
Jan
(7) |
Feb
(5) |
Mar
(5) |
Apr
(5) |
May
(8) |
Jun
(4) |
Jul
(5) |
Aug
(4) |
Sep
(6) |
Oct
(7) |
Nov
(2) |
Dec
(3) |
| 2017 |
Jan
(7) |
Feb
(8) |
Mar
(7) |
Apr
(3) |
May
(4) |
Jun
(3) |
Jul
(5) |
Aug
(8) |
Sep
(4) |
Oct
(2) |
Nov
(3) |
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2019 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2021 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
(5) |
Sep
(2) |
Oct
|
Nov
|
Dec
(1) |
| 2026 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Darren D. <da...@sh...> - 2005-11-26 18:38:31
|
1133030272
FAILED
[junit] Testcase: testNaming took 0,006 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,016 sec
[junit] Testsuite: org.springframework.jmx.export.naming.PropertiesFileNamingStrategyTests
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,016 sec
[junit] Testcase: testNaming took 0,004 sec
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,018 sec
[junit] Testsuite: org.springframework.jmx.export.naming.PropertiesNamingStrategyTests
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,018 sec
[junit] Testcase: testNaming took 0,001 sec
[junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 0,127 sec
[junit] Testsuite: org.springframework.jmx.support.ConnectorServerFactoryBeanTests
[junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 0,127 sec
[junit] Testcase: testStartupWithLocatedServer took 0,067 sec
[junit] Testcase: testStartupWithSuppliedServer took 0,024 sec
[junit] Testcase: testRegisterWithMBeanServer took 0,014 sec
[junit] Caused an ERROR
[junit] Address already in use
[junit] java.net.BindException: Address already in use
[junit] at java.net.PlainSocketImpl.socketBind(Native Method)
[junit] at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
[junit] at java.net.ServerSocket.bind(ServerSocket.java:318)
[junit] at com.sun.jmx.remote.socket.SocketConnectionServer.start(SocketConnectionServer.java:128)
[junit] at com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.start(SynchroMessageConnectionServerImpl.java:39)
[junit] at javax.management.remote.generic.GenericConnectorServer.start(GenericConnectorServer.java:235)
[junit] at org.springframework.jmx.support.ConnectorServerFactoryBean.afterPropertiesSet(ConnectorServerFactoryBean.java:183)
[junit] at org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testRegisterWithMBeanServer(ConnectorServerFactoryBeanTests.java:78)
Last CVS updates prior to this build were:
1133028782
? ?
? junit423465713.properties
? junittestcases2136842450.properties
? sandbox/src/org/springframework/core/closure/ElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java
? sandbox/src/org/springframework/core/closure/support/IfBlock.java
? sandbox/src/org/springframework/jms/listener
? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
P autobuilds/apps/common-build/common-targets.xml
P src/org/springframework/beans/factory/support/AbstractAutowireCapableBeanFactory.java
P src/org/springframework/beans/factory/support/AbstractBeanDefinition.java
P src/org/springframework/beans/factory/support/AbstractBeanFactory.java
P src/org/springframework/beans/factory/xml/DefaultXmlBeanDefinitionParser.java
P src/org/springframework/beans/factory/xml/spring-beans.dtd
P test/org/springframework/beans/factory/xml/DefaultLifecycleMethodsTests.java
U test/org/springframework/beans/factory/xml/defaultLifecycleMethods.xml
C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
This is an automated mail from one of the SF Compile Farm machines.
The machine name noted in the subject encountered a failure building
or running the Spring test suite. The last few lines of the output
were included for info.
NB: No further mail will be sent from this machine until a
successful build occurs on the machine in question.
See http://springframework.sourceforge.net/test/ for further
information.
|
|
From: Colin S. <col...@ex...> - 2005-11-26 17:33:37
|
The 'ejbtest' integration test sample in autobuilds had been broken by developments in recent months (in the Spring codebase, mainly jars and the like moved around), without me or anybody else picking this up. I've gone through and fixed the sample so it works again. Originally this sample had been tested with JBoss 3.2. I've made it work with JBoss 4.0.2 and 4.0.3SP1, which required some rework of the local EJB handling, as JBoss 4.0 is more compliant with the (EJB 2.1) spec and no longer binds local bean homes in a globally known JNDI location, where the sample was trying to use them from. Instead, they must be accessed only via the Environmental Naming Context (ENC) JNDI tree, which required adding <ejb-local-ref> elements in the web.xml or ejb.xml files of components that need to access them. More EJB XML, ughh! Anyway, it's working now. I will at some point relatively soon try to go into this app again to make sure it works with WebLogic and WebSphere too. One issue is that right now it relies on a unified classloader being used for all jars and ejbs loaded at the ear (applicaiton.xml) level. This is probably not the default in WebLogic and WebSphere. Colin |
|
From: <al...@in...> - 2005-11-25 23:19:54
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051126001628 |
|
From: Bram S. <br...@in...> - 2005-11-25 18:38:10
|
Alright, thanks. Greetings, Bram -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf Of Juergen Hoeller Sent: donderdag 24 november 2005 23:19 To: spr...@li... Subject: Re: [Springframework-developer] Trimming values in PropertiesBeanDefinitionReader Hi Bram, Sounds appropriate. I've refined PropertiesBeanDefinitionReader to trim String values that it encounters, for all special keys (that is, everything other than values for actual bean properties). Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf Of Bram Smeets Sent: Wednesday, November 23, 2005 11:59 PM To: spr...@li... Subject: [Springframework-developer] Trimming values in PropertiesBeanDefinitionReader Hi All, This week, at a customer, I encountered some annoying behavior with the ResourceBundleViewResolver. When the view class, specified in the properties file, contains a trailing whitespace in the class name, you get a ClassNotFoundException with the message: java.lang.ClassNotFoundException: org.springframework.web.servlet.view.InternalResourceView This proved to be very confusing to developers (as I reckon it is, as the whitespace is not visible in the error message). The problem lies in the fact that the PropertiesBeanDefinitionReader does not trim the values obtained from the resource bundle. Is it possible to add trimming of the values in the resource bundles, or do I miss some implications this might have? It is fairly simple to test, I just added another test to the ResourceBundleViewResolverTests that checks for an additional view (with a trailing whitespace in the class name). Greetings, Bram Smeets -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.5/178 - Release Date: 22-11-2005 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.7/182 - Release Date: 24-11-2005 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.7/182 - Release Date: 24-11-2005 |
|
From: <al...@in...> - 2005-11-24 23:31:19
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051125001625Lbuild.379 |
|
From: Juergen H. <ju...@in...> - 2005-11-24 22:19:21
|
Hi Bram, Sounds appropriate. I've refined PropertiesBeanDefinitionReader to trim String values that it encounters, for all special keys (that is, everything other than values for actual bean properties). Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf Of Bram Smeets Sent: Wednesday, November 23, 2005 11:59 PM To: spr...@li... Subject: [Springframework-developer] Trimming values in PropertiesBeanDefinitionReader Hi All, This week, at a customer, I encountered some annoying behavior with the ResourceBundleViewResolver. When the view class, specified in the properties file, contains a trailing whitespace in the class name, you get a ClassNotFoundException with the message: java.lang.ClassNotFoundException: org.springframework.web.servlet.view.InternalResourceView This proved to be very confusing to developers (as I reckon it is, as the whitespace is not visible in the error message). The problem lies in the fact that the PropertiesBeanDefinitionReader does not trim the values obtained from the resource bundle. Is it possible to add trimming of the values in the resource bundles, or do I miss some implications this might have? It is fairly simple to test, I just added another test to the ResourceBundleViewResolverTests that checks for an additional view (with a trailing whitespace in the class name). Greetings, Bram Smeets -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.5/178 - Release Date: 22-11-2005 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Rob H. <rob...@in...> - 2005-11-24 13:11:07
|
It is indeed very cool. What is also interesting is the support for bootstrapping Spring inside a J2SE environment using AspectJ. Not really thought about field injection that much, because I'm not really a fan. It makes testing a class a real pain in my experience. Of course, if there is real community interest in having field level injection then it is a trivial feature to add. Rob Magnus Heino wrote: >2005/11/23, Rob Harrop <rob...@in...>: > > >>The code from the blog entry you suggested will make it into the 1.3 >>release in time for RC1. Also, I am hoping to release DIIFactoryBean in >>RC2 which should give you plenty of options. >> >>The AspectJ solution is certainly my preference. >> >> > >This is very cool! :-) > >So, using this stuff and some implementation of SPR-1047, I can >configure all beans using just a @Bean annotation and be sure that my >dependencies are setup ok? > >Are there any thoughts on not needing the setter method for required >properties? I mean, if you have a @RequiredProperty or simular set on >a property that should be validated, why also have a setter? Something >like the EJB3 @Resource annotation I guess. > >/Magnus > > >------------------------------------------------------- >This SF.net email is sponsored by: Splunk Inc. Do you grep through log files >for problems? Stop! Download the new AJAX search engine that makes >searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >http://ads.osdn.com/?ad_idv37&alloc_id865&op=click >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > -- Rob Harrop Principal Consultant Interface21 - Spring Services from the Source http://www.springframework.com |
|
From: Magnus H. <ma...@fi...> - 2005-11-24 07:37:02
|
2005/11/23, Rob Harrop <rob...@in...>: > The code from the blog entry you suggested will make it into the 1.3 > release in time for RC1. Also, I am hoping to release DIIFactoryBean in > RC2 which should give you plenty of options. > > The AspectJ solution is certainly my preference. This is very cool! :-) So, using this stuff and some implementation of SPR-1047, I can configure all beans using just a @Bean annotation and be sure that my dependencies are setup ok? Are there any thoughts on not needing the setter method for required properties? I mean, if you have a @RequiredProperty or simular set on a property that should be validated, why also have a setter? Something like the EJB3 @Resource annotation I guess. /Magnus |
|
From: Artem P. <bla...@ca...> - 2005-11-23 23:51:06
|
I am sorry, but I was not subscribed to the mailing list when I posted = my original message regarding the OpenSessionInViewFilter implementation = in Spring. The main reason why I want to store the Hibernate session in the HTTP = session is that in my application, the lifetime of a business objects = exceeds an HTTP request. Furthermore, the application is layered, and = re-attaching all business objects to a new session for every request = would require leaking some Hibernate-specific code into the presentation = layer and/or implementing "reattachment" mechanisms in my business logic = layer. The time it takes to create session objects is immaterial, and I = am not currently concerned about performance at that level. I'm more = concerned about proper layering. I don't want to replace the original filter with the one I'm = proposing... It's just an alternative for applications that require = long-running sessions. Applications that do not use session management = will work just fine with the original filter. The main problem is that = even though Hibernate entities are "just POJOs", they will most likely = contain proxies, and if the original session is closed, they need to be = merge()d with a new session or else they will start throwing exceptions. = Thank you, Artem Ploujnikov |
|
From: <al...@in...> - 2005-11-23 23:30:26
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051124001628Lbuild.378 |
|
From: Bram S. <br...@in...> - 2005-11-23 23:00:12
|
Hi All, This week, at a customer, I encountered some annoying behavior with the ResourceBundleViewResolver. When the view class, specified in the properties file, contains a trailing whitespace in the class name, you get a ClassNotFoundException with the message: java.lang.ClassNotFoundException: org.springframework.web.servlet.view.InternalResourceView This proved to be very confusing to developers (as I reckon it is, as the whitespace is not visible in the error message). The problem lies in the fact that the PropertiesBeanDefinitionReader does not trim the values obtained from the resource bundle. Is it possible to add trimming of the values in the resource bundles, or do I miss some implications this might have? It is fairly simple to test, I just added another test to the ResourceBundleViewResolverTests that checks for an additional view (with a trailing whitespace in the class name). Greetings, Bram Smeets -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.5/178 - Release Date: 22-11-2005 |
|
From: Rob H. <rob...@in...> - 2005-11-23 20:52:44
|
The code from the blog entry you suggested will make it into the 1.3 release in time for RC1. Also, I am hoping to release DIIFactoryBean in RC2 which should give you plenty of options. The AspectJ solution is certainly my preference. Rob Magnus Heino wrote: >Hi. > >I am looking into domain objects and DI. Objects loaded by hibernate >or created pragmatically. > >Google and the spring forms comes up with many solutions and code >examples. I also remember Rod mention something about this in some >mailinglist a while back? > >Searching JIRA for DependencyInjectionInterceptorFactoryBean.java >comes up with SPR-431 set for 1.4RC1 and SPR-1163 in 1.3RC1. Is this >the path that I should choose that will be incrementally more and more >supported by spring? > >Other blogs are suggesting more AspectJ integrated solutions: >http://www.aspectprogrammer.org/blogs/adrian/2005/03/hacking_with_ha.html >is this also an alternative to consider? > >-- > > /Magnus Heino > > >------------------------------------------------------- >This SF.Net email is sponsored by the JBoss Inc. Get Certified Today >Register for a JBoss Training Course. Free Certification Exam >for All Training Attendees Through End of 2005. For more info visit: >http://ads.osdn.com/?ad_idv28&alloc_id845&op=click >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > -- Rob Harrop Principal Consultant Interface21 - Spring Services from the Source http://www.springframework.com |
|
From: Michael E. M. <mm...@re...> - 2005-11-23 17:35:18
|
I can't attend the Spring Experience conference, very depressed about it. Will we be able to watch the sessions on-line anywhere? Will video of the sessions be archived? --Michael |
|
From: Eugene K. <eu...@md...> - 2005-11-23 14:47:56
|
There is nothing wrong to use MDB as a listener. You can delegate all the processing to Spring-based classes same way as from Spring-based listener. regards, Eugene shifei luo wrote: > My dear Spring Community, As far as I know, Spring 1.3 will provide JMS > Listener support asynchronously. > But in WebSphere 6.0 Web Container, this isn't possible for the > following reason. > Can't Use MessageListeners in J2EE > > posted by Bobby Woolf > Permalink > > Here's an interesting conflict between JMS and J2EE that I just > rediscovered: > > You can't run an implementor of MessageListener in a J2EE container. > J2EE 1.3 says not to do it in the EJB container. J2EE 1.4 says not to do > it in the Web container either. Basically, you can't use it in any > container that controls thread creation, which is any container except > an application client container. > > WAS 5 and 6 don't allow MessageListeners to be used in either container. > When you try, you get an error like this: > > > > javax.jms.IllegalStateException: Method setMessageListener not permitted > at > com.ibm.ejs.jms.JMSCMUtils.methodNotPermittedException(JMSCMUtils.java:202) > at > com.ibm.ejs.jms.JMSMessageConsumerHandle.setMessageListener(JMSMessageConsumerHandle.java:193) > at MyMessageListenerImpl.connect(MyMessageListenerImpl.java:39) > . . . > > > So WAS doesn't actually prevent you from deploying a class that > implements MessageListener, but when you try to run your code, WAS > prevents the MessageConsumer.setMessageListener(MessageListener) method > from running by throwing an IllegalStateException. For details, see IBM > WMQ FAQ answer #92 and IBM Technote #1114239. > > So when you get this error, the problem isn't a bug in your code, it's > your entire approach. In a nutshell, if you want to run a > MessageListener in J2EE, don't implement a MessageListener, implement a > (can you guess?) messsage-driven bean (the JMS kind, which implements > MessageListener). And if you don't like using EJBs? Get used to it. MDBs > work in J2EE; MessageListeners don't. > > (from Bobby Woolf Blog) > > http://www-128.ibm.com/developerworks/blogs/dw_blog_comments.jspa?blog=392&entry=71861 > <http://www-128.ibm.com/developerworks/blogs/dw_blog_comments.jspa?blog=392&entry=71861> > > Because my current project may use WebSphere 6.0,and it must listener > messages from Web Container asynchronously, So the > answer is urgent to me. By the way, we have not use MDB to listener > messages. > > Do Spring 1.3 plan providing workaround for this or some other solutions? > > thx. |
|
From: shifei l. <j2e...@ya...> - 2005-11-23 14:19:15
|
TXkgZGVhciBTcHJpbmcgQ29tbXVuaXR5LCBBcyBmYXIgYXMgSSBrbm93LCBTcHJpbmcgMS4zIHdp bGwgcHJvdmlkZSBKTVMgTGlzdGVuZXIgc3VwcG9ydCBhc3luY2hyb25vdXNseS4NCkJ1dCBpbiBX ZWJTcGhlcmUgNi4wIFdlYiBDb250YWluZXIsIHRoaXMgaXNuJ3QgcG9zc2libGUgZm9yIHRoZSBm b2xsb3dpbmcgcmVhc29uLg0KDQpDYW4ndCBVc2UgTWVzc2FnZUxpc3RlbmVycyBpbiBKMkVFDQoN CnBvc3RlZCBieSBCb2JieSBXb29sZiANClBlcm1hbGluayANCg0KSGVyZSdzIGFuIGludGVyZXN0 aW5nIGNvbmZsaWN0IGJldHdlZW4gSk1TIGFuZCBKMkVFIHRoYXQgSSBqdXN0IHJlZGlzY292ZXJl ZDoNCg0KWW91IGNhbid0IHJ1biBhbiBpbXBsZW1lbnRvciBvZiBNZXNzYWdlTGlzdGVuZXIgaW4g YSBKMkVFIGNvbnRhaW5lci4gSjJFRSAxLjMgc2F5cyBub3QgdG8gZG8gaXQgaW4gdGhlIEVKQiBj b250YWluZXIuIEoyRUUgMS40IHNheXMgbm90IHRvIGRvIGl0IGluIHRoZSBXZWIgY29udGFpbmVy IGVpdGhlci4gQmFzaWNhbGx5LCB5b3UgY2FuJ3QgdXNlIGl0IGluIGFueSBjb250YWluZXIgdGhh dCBjb250cm9scyB0aHJlYWQgY3JlYXRpb24sIHdoaWNoIGlzIGFueSBjb250YWluZXIgZXhjZXB0 IGFuIGFwcGxpY2F0aW9uIGNsaWVudCBjb250YWluZXIuDQoNCldBUyA1IGFuZCA2IGRvbid0IGFs bG93IE1lc3NhZ2VMaXN0ZW5lcnMgdG8gYmUgdXNlZCBpbiBlaXRoZXIgY29udGFpbmVyLiBXaGVu IHlvdSB0cnksIHlvdSBnZXQgYW4gZXJyb3IgbGlrZSB0aGlzOg0KDQoNCg0KICBqYXZheC5qbXMu SWxsZWdhbFN0YXRlRXhjZXB0aW9uOiBNZXRob2Qgc2V0TWVzc2FnZUxpc3RlbmVyIG5vdCBwZXJt aXR0ZWQNCiAgYXQgY29tLmlibS5lanMuam1zLkpNU0NNVXRpbHMubWV0aG9kTm90UGVybWl0dGVk RXhjZXB0aW9uKEpNU0NNVXRpbHMuamF2YToyMDIpDQogIGF0IGNvbS5pYm0uZWpzLmptcy5KTVNN ZXNzYWdlQ29uc3VtZXJIYW5kbGUuc2V0TWVzc2FnZUxpc3RlbmVyKEpNU01lc3NhZ2VDb25zdW1l ckhhbmRsZS5qYXZhOjE5MykNCiAgYXQgTXlNZXNzYWdlTGlzdGVuZXJJbXBsLmNvbm5lY3QoTXlN ZXNzYWdlTGlzdGVuZXJJbXBsLmphdmE6MzkpDQogIC4gLiAuDQoNCg0KU28gV0FTIGRvZXNuJ3Qg YWN0dWFsbHkgcHJldmVudCB5b3UgZnJvbSBkZXBsb3lpbmcgYSBjbGFzcyB0aGF0IGltcGxlbWVu dHMgTWVzc2FnZUxpc3RlbmVyLCBidXQgd2hlbiB5b3UgdHJ5IHRvIHJ1biB5b3VyIGNvZGUsIFdB UyBwcmV2ZW50cyB0aGUgTWVzc2FnZUNvbnN1bWVyLnNldE1lc3NhZ2VMaXN0ZW5lcihNZXNzYWdl TGlzdGVuZXIpIG1ldGhvZCBmcm9tIHJ1bm5pbmcgYnkgdGhyb3dpbmcgYW4gSWxsZWdhbFN0YXRl RXhjZXB0aW9uLiBGb3IgZGV0YWlscywgc2VlIElCTSBXTVEgRkFRIGFuc3dlciAjOTIgYW5kIElC TSBUZWNobm90ZSAjMTExNDIzOS4NCg0KU28gd2hlbiB5b3UgZ2V0IHRoaXMgZXJyb3IsIHRoZSBw cm9ibGVtIGlzbid0IGEgYnVnIGluIHlvdXIgY29kZSwgaXQncyB5b3VyIGVudGlyZSBhcHByb2Fj aC4gSW4gYSBudXRzaGVsbCwgaWYgeW91IHdhbnQgdG8gcnVuIGEgTWVzc2FnZUxpc3RlbmVyIGlu IEoyRUUsIGRvbid0IGltcGxlbWVudCBhIE1lc3NhZ2VMaXN0ZW5lciwgaW1wbGVtZW50IGEgKGNh biB5b3UgZ3Vlc3M/KSBtZXNzc2FnZS1kcml2ZW4gYmVhbiAodGhlIEpNUyBraW5kLCB3aGljaCBp bXBsZW1lbnRzIE1lc3NhZ2VMaXN0ZW5lcikuIEFuZCBpZiB5b3UgZG9uJ3QgbGlrZSB1c2luZyBF SkJzPyBHZXQgdXNlZCB0byBpdC4gTURCcyB3b3JrIGluIEoyRUU7IE1lc3NhZ2VMaXN0ZW5lcnMg ZG9uJ3QuDQoNCihmcm9tIEJvYmJ5IFdvb2xmIEJsb2cpDQoNCmh0dHA6Ly93d3ctMTI4LmlibS5j b20vZGV2ZWxvcGVyd29ya3MvYmxvZ3MvZHdfYmxvZ19jb21tZW50cy5qc3BhP2Jsb2c9MzkyJmVu dHJ5PTcxODYxDQoNCkJlY2F1c2UgbXkgY3VycmVudCBwcm9qZWN0IG1heSB1c2UgV2ViU3BoZXJl IDYuMCxhbmQgaXQgbXVzdCBsaXN0ZW5lciBtZXNzYWdlcyBmcm9tIFdlYiBDb250YWluZXIgYXN5 bmNocm9ub3VzbHksIFNvIHRoZSANCmFuc3dlciBpcyB1cmdlbnQgdG8gbWUuIEJ5IHRoZSB3YXks IHdlIGhhdmUgbm90IHVzZSBNREIgdG8gbGlzdGVuZXIgbWVzc2FnZXMuDQoNCkRvIFNwcmluZyAx LjMgcGxhbiBwcm92aWRpbmcgd29ya2Fyb3VuZCBmb3IgdGhpcyBvciBzb21lIG90aGVyIHNvbHV0 aW9ucz8NCg0KdGh4Lg== |
|
From: <al...@in...> - 2005-11-22 23:19:10
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051123001635 |
|
From: Seth L. <set...@gm...> - 2005-11-22 18:58:35
|
> Searching JIRA for DependencyInjectionInterceptorFactoryBean.java > comes up with SPR-431 set for 1.4RC1 and SPR-1163 in 1.3RC1. Is this > the path that I should choose that will be incrementally more and more > supported by spring? That code, found in the sandbox, is quite solid. I've used it in our app for a long time, with great results. I'm hoping it'll get moved up to the formal code base in Spring 1.3. Seth |
|
From: Magnus H. <ma...@fi...> - 2005-11-22 12:12:20
|
Hi. I am looking into domain objects and DI. Objects loaded by hibernate or created pragmatically. Google and the spring forms comes up with many solutions and code examples. I also remember Rod mention something about this in some mailinglist a while back? Searching JIRA for DependencyInjectionInterceptorFactoryBean.java comes up with SPR-431 set for 1.4RC1 and SPR-1163 in 1.3RC1. Is this the path that I should choose that will be incrementally more and more supported by spring? Other blogs are suggesting more AspectJ integrated solutions: http://www.aspectprogrammer.org/blogs/adrian/2005/03/hacking_with_ha.html is this also an alternative to consider? -- /Magnus Heino |
|
From: Darren D. <da...@sh...> - 2005-11-22 02:35:05
|
1132626906
FAILED
[javac] ConfigurableJasperReportsView view = new ConfigurableJasperReportsView();
[javac] ^
[javac] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/web/servlet/view/jasperreports/AbstractConfigurableJasperReportsViewTests.java:21: cannot resolve symbol
[javac] symbol : class ConfigurableJasperReportsView
[javac] location: class org.springframework.web.servlet.view.jasperreports.AbstractConfigurableJasperReportsViewTests
[javac] ConfigurableJasperReportsView view = new ConfigurableJasperReportsView();
[javac] ^
[javac] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/web/servlet/view/jasperreports/ConfigurableJasperReportsViewWithStreamTests.java:11: cannot resolve symbol
[javac] symbol : class ConfigurableJasperReportsView
[javac] location: class org.springframework.web.servlet.view.jasperreports.ConfigurableJasperReportsViewWithStreamTests
[javac] ConfigurableJasperReportsView view = new ConfigurableJasperReportsView();
[javac] ^
[javac] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/web/servlet/view/jasperreports/ConfigurableJasperReportsViewWithStreamTests.java:11: cannot resolve symbol
[javac] symbol : class ConfigurableJasperReportsView
[javac] location: class org.springframework.web.servlet.view.jasperreports.ConfigurableJasperReportsViewWithStreamTests
[javac] ConfigurableJasperReportsView view = new ConfigurableJasperReportsView();
[javac] ^
[javac] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/web/servlet/view/jasperreports/ConfigurableJasperReportsViewWithWriterTests.java:11: cannot resolve symbol
[javac] symbol : class ConfigurableJasperReportsView
[javac] location: class org.springframework.web.servlet.view.jasperreports.ConfigurableJasperReportsViewWithWriterTests
[javac] ConfigurableJasperReportsView view = new ConfigurableJasperReportsView();
[javac] ^
[javac] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/web/servlet/view/jasperreports/ConfigurableJasperReportsViewWithWriterTests.java:11: cannot resolve symbol
[javac] symbol : class ConfigurableJasperReportsView
[javac] location: class org.springframework.web.servlet.view.jasperreports.ConfigurableJasperReportsViewWithWriterTests
[javac] ConfigurableJasperReportsView view = new ConfigurableJasperReportsView();
[javac] ^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -deprecation for details.
[javac] 7 errors
Last CVS updates prior to this build were:
1132625581
? ?
? junit423465713.properties
? junittestcases2136842450.properties
? sandbox/src/org/springframework/core/closure/ElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java
? sandbox/src/org/springframework/core/closure/support/IfBlock.java
? sandbox/src/org/springframework/jms/listener
? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
This is an automated mail from one of the SF Compile Farm machines.
The machine name noted in the subject encountered a failure building
or running the Spring test suite. The last few lines of the output
were included for info.
NB: No further mail will be sent from this machine until a
successful build occurs on the machine in question.
See http://springframework.sourceforge.net/test/ for further
information.
|
|
From: Darren D. <da...@sh...> - 2005-11-22 01:33:03
|
1132623181 FAILED Last CVS updates prior to this build were: 1132621981 ? ? ? junit423465713.properties ? junittestcases2136842450.properties ? sandbox/src/org/springframework/core/closure/ElementGenerator.java ? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java ? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java ? sandbox/src/org/springframework/core/closure/support/IfBlock.java ? sandbox/src/org/springframework/jms/listener ? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml This is an automated mail from one of the SF Compile Farm machines. The machine name noted in the subject encountered a failure building or running the Spring test suite. The last few lines of the output were included for info. NB: No further mail will be sent from this machine until a successful build occurs on the machine in question. See http://springframework.sourceforge.net/test/ for further information. |
|
From: Darren D. <da...@sh...> - 2005-11-21 21:33:08
|
1132608787 FAILED Last CVS updates prior to this build were: 1132607581 ? ? ? junit423465713.properties ? junittestcases2136842450.properties ? sandbox/src/org/springframework/core/closure/ElementGenerator.java ? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java ? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java ? sandbox/src/org/springframework/core/closure/support/IfBlock.java ? sandbox/src/org/springframework/jms/listener ? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml This is an automated mail from one of the SF Compile Farm machines. The machine name noted in the subject encountered a failure building or running the Spring test suite. The last few lines of the output were included for info. NB: No further mail will be sent from this machine until a successful build occurs on the machine in question. See http://springframework.sourceforge.net/test/ for further information. |
|
From: Darren D. <da...@sh...> - 2005-11-21 20:33:04
|
1132605187 FAILED Last CVS updates prior to this build were: 1132603981 ? ? ? junit423465713.properties ? junittestcases2136842450.properties ? sandbox/src/org/springframework/core/closure/ElementGenerator.java ? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java ? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java ? sandbox/src/org/springframework/core/closure/support/IfBlock.java ? sandbox/src/org/springframework/jms/listener ? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml This is an automated mail from one of the SF Compile Farm machines. The machine name noted in the subject encountered a failure building or running the Spring test suite. The last few lines of the output were included for info. NB: No further mail will be sent from this machine until a successful build occurs on the machine in question. See http://springframework.sourceforge.net/test/ for further information. |
|
From: Darren D. <da...@sh...> - 2005-11-21 19:33:19
|
1132601587 FAILED Last CVS updates prior to this build were: 1132600381 ? ? ? junit423465713.properties ? junittestcases2136842450.properties ? sandbox/src/org/springframework/core/closure/ElementGenerator.java ? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java ? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java ? sandbox/src/org/springframework/core/closure/support/IfBlock.java ? sandbox/src/org/springframework/jms/listener ? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml This is an automated mail from one of the SF Compile Farm machines. The machine name noted in the subject encountered a failure building or running the Spring test suite. The last few lines of the output were included for info. NB: No further mail will be sent from this machine until a successful build occurs on the machine in question. See http://springframework.sourceforge.net/test/ for further information. |
|
From: Earhart, K. <Kim...@co...> - 2005-11-21 16:24:13
|
I have five openings for Developers with Hibernate/Spring experience in Dallas, TX ESSENTIAL RESPONSIBILITIES:=20 Will code and configure diverse and complex programs from technical=20 specifications. Incorporates development practices such as refactoring,=20 iterative development, and unit testing. Work with all aspects of the=20 development life cycle from writing functional specification documents=20 and use cases to working with the Quality Assurance team in the final=20 testing process.=20 Develop Use Case Models for the functional requirement and performs=20 technical design and implementation. Documents code, architecture,=20 enhancements and bug fixes.=20 Develop and executes automation of unit test scripts on all code=20 developed. Provides testing mechanisms and communications to facilitate=20 the release of a quality product.=20 TECHNICAL KNOWLEDGE / SKILLS / EDUCATION REQUIRED:=20 At least 3 years experience with J2EE programming=20 Experience with Spring framework, Stateless-Session EJB, and JMS=20 Experience with various data access strategies including Hibernate=20 Experience with web services=20 Experience with XML, JAX-RPC, XML schema, SOAP, WSDL, Java XML=20 processing with SAX/DOM=20 Prefer experience with Eclipse, Ant, CVS, Unix/Linux=20 Requires knowledge and understanding of SOA principles and architecture=20 Requires understanding of programming concepts such as AOP, Dependency=20 Injection and Inversion of Control=20 Requires excellent written and verbal English communication skills=20 Typically requires a bachelor's degree in computer science/engineering=20 or equivalent computer-related experience=20 =20 =20 Kim Earhart Comsys Information Technology Services, Inc. 15455 Dallas Parkway Ste 300 Addison, TX 75001 972-892-9092 fax: 972-892-9002 cell 469-387-9469 =20 "The ultimate measure of a man is not where he stands in moments of comfort and convenience but, where he stands at time of challenge and controversy." Martin Luther King Jr. =20 =20 |
|
From: Les A. H. <le...@ha...> - 2005-11-21 13:37:25
|
Sorry, I didn't get to finish my previous email (hit shortcut key for
'send' by accident).
It is not recommended to implement this type of behavior in a Hibernate
application. An application-transaction is scoped to a few connected
request/response cycles and shouldn't be used across a user's entire
interaction with the system - doing otherwise creates much greater
conflict for stale data and versioning conflicts.
Also, I'm not sure why you'd want to do this in the first place -
sessions are extremely lightweight objects that are meant to be created
and destroyed at the beginning and end of a single request,
respectively. They are only meant to be disconnected/reconnected across
multiple requests when those requests are related to what Hibernate
calls an "application transaction": when visiting multiple pages in
succession build up data context and that accumulated data should be
commited or rolled back at the same instant of time - think of a
web-based wizard, where at the end of step 4, only then should
everything be committed to the database.
If you're trying to enhance performance of the application (and
Hibernate is the only process accessing the database), it is more
efficient and better form to enable a 2nd-level cache (instead of using
the Session itself for that purpose).
From the Hibernate documentation:
"This pattern [long-lived session] is problematic if the Session is too
big to be stored during user think time, e.g. an HttpSession should be
kept as small as possible. As the Session is also the (mandatory)
first-level cache and contains all loaded objects, we can probably use
this strategy only for a few request/response cycles. This is indeed
recommended, as the Session will soon also have stale data."
Regards,
Les
P.S. I should also note that storing a Hibernate Session in an
HttpSession will cause problems in a clustered environment - its usually
better to maintain a stateless programming paradigm across the entire
application and enable the second cache if you ever envision software
being run in a clustered and/or striped deployment.
On Sun, 20 Nov 2005 20:29:21 -0500, "Artem Ploujnikov"
<bla...@ca...> said:
> Some Web application frameworks like JSF might require you to extend
> the
> lifetime of a persistent entity beyond a single HTTP request. What I am
> proposing is an alternative implementation of OpenSessionInViewFilter
> that
> opens one Hibernate session per HTTP session instead of one session per
> request. JDBC connection management should not be a problem because it is
> possible to disconnect and reconnect Hibernate sessions without closing
> them.
>
> Here is the filter that I'm using in my application... I think it would
> be a
> good idea to include something similar in a future release of Spring.
> Please
> note that it hasn't been well tested, and it requires a session filter
> that
> closes orphaned sessions.
>
> public class HibernateSessionFilter extends OncePerRequestFilter {
> public static final String DEFAULT_SESSION_FACTORY_BEAN_NAME =
> "sessionFactory";
> public static final String SESSION_KEY = "org.foo.web.hibernateSession";
>
> private String sessionFactoryBeanName =
> DEFAULT_SESSION_FACTORY_BEAN_NAME;
>
> /**
> * @return Returns the sessionFactoryBeanName.
> */
> protected String getSessionFactoryBeanName() {
> return sessionFactoryBeanName;
> }
>
>
> /**
> * @param sessionFactoryBeanName The sessionFactoryBeanName to set.
> */
> public void setSessionFactoryBeanName(String sessionFactoryBeanName) {
> this.sessionFactoryBeanName = sessionFactoryBeanName;
> }
>
>
> protected SessionFactory lookupSessionFactory() {
> if (logger.isDebugEnabled()) {
> logger.debug("Using SessionFactory '" + getSessionFactoryBeanName() +
> "'
> for OpenSessionInViewFilter");
> }
> WebApplicationContext wac =
> WebApplicationContextUtils.getRequiredWebApplicationContext(getServletContext());
> return (SessionFactory) wac.getBean(getSessionFactoryBeanName(),
> SessionFactory.class);
> }
>
> protected void doFilterInternal(
> HttpServletRequest request, HttpServletResponse response, FilterChain
> filterChain)
> throws ServletException, IOException {
> SessionFactory sessionFactory = lookupSessionFactory();
> HttpSession httpSession = request.getSession();
> Session session =
> (Session) httpSession.getAttribute(SESSION_KEY);
> if (session == null) {
> session = sessionFactory.openSession();
> httpSession.setAttribute(SESSION_KEY, session);
> }
> if (!session.isConnected()) {
> session.reconnect();
> }
> TransactionSynchronizationManager.bindResource(sessionFactory, new
> SessionHolder(session));
> try {
> filterChain.doFilter(request, response);
> } finally {
> TransactionSynchronizationManager.unbindResource(sessionFactory);
> session.disconnect();
> }
>
> }
>
> }
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
> Register for a JBoss Training Course. Free Certification Exam
> for All Training Attendees Through End of 2005. For more info visit:
> http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
|