Comments on: Re: Getting Sprung with Spring http://agylen.com/2005/07/05/re-getting-sprung-with-spring/ Ugo Cei's Weblog Tue, 07 Oct 2008 09:16:31 +0000 http://wordpress.org/?v=2.3.3 By: Agylen » Home office addition http://agylen.com/2005/07/05/re-getting-sprung-with-spring/#comment-159 Agylen » Home office addition Tue, 12 Jul 2005 13:59:07 +0000 http://agylen.com/2005/07/05/re-getting-sprung-with-spring/#comment-159 [...] n Posted by ugo under personal(bookmark this)   It’s been a while, since my latest blog post. The problem is I had a very busy week in Rome, with no Internet [...] […] n
Posted by ugo under personal(bookmark this)
 

It’s been a while, since my latest blog post. The problem is I had a very busy week in Rome, with no Internet […]

]]> By: Andy http://agylen.com/2005/07/05/re-getting-sprung-with-spring/#comment-156 Andy Wed, 06 Jul 2005 18:33:01 +0000 http://agylen.com/2005/07/05/re-getting-sprung-with-spring/#comment-156 I suggest that it complicates H3 use on recent versions of WebSphere as in my experience it is much simpler to get H3+Spring to work on WS 5.1-6.0 rather than H3. -- uh strike that, reverse it (H3 works fine on 5.1/6.0 H3+Spring is a pain on 5.1/6.0) I suggest that it complicates H3 use on recent versions of WebSphere as in my experience it is much simpler to get H3+Spring to work on WS 5.1-6.0 rather than H3. — uh strike that, reverse it (H3 works fine on 5.1/6.0 H3+Spring is a pain on 5.1/6.0)

]]> By: Andy http://agylen.com/2005/07/05/re-getting-sprung-with-spring/#comment-155 Andy Tue, 05 Jul 2005 10:22:12 +0000 http://agylen.com/2005/07/05/re-getting-sprung-with-spring/#comment-155 You can accomplish the same thing RE: Hibernate 3 upgrade by doing the equivilent of "g/net\.sf\.hibernate/s//org\.hibernate\.classic/g" regardless of Spring. Thus Spring offers no real advantage in the Hibernate space. I was saying JDK 1.5 meaning, you can use the EJB3/annotations stuff with JDK 1.5 (god I hate Sun's stupid fascination with bizzarre numberology). Since for Hibernate this is really just about a different API not actual new functionality, it is a pretty safe bet so far as production stability. Its also no longer a moving target really. I stand by my notation that Spring offers very little to Hibernate3. I suggest that it complicates H3 use on recent versions of WebSphere as in my experience it is much simpler to get H3+Spring to work on WS 5.1-6.0 rather than H3. I did not suggest one way or another whether non-ORM based Spring should be used as that would be somewhat outside my experience. It might not be my choice because I dislike XML configuration particularly hierarchial embedded XML configuration, but I suppose if there was something I needed in Spring's library of functionality, why not? I should note that JDK 1.5 (or JDK 5 if you care about Sun's weird number fascination/marketing) indeed seems to be more stable in high capacity environmnets than is 1.4 due to the rewritten GC (1.42 parallel GC is actually a bit buggy) even if 1.5 introduced some odd new Hotspot issues. Organizations are likely to notice performance increases from JDK 1.5 and thus could consider beginning to use JDK 1.5 features such as annotations. You can accomplish the same thing RE: Hibernate 3 upgrade by doing the equivilent of “g/net\.sf\.hibernate/s//org\.hibernate\.classic/g” regardless of Spring. Thus Spring offers no real advantage in the Hibernate space. I was saying JDK 1.5 meaning, you can use the EJB3/annotations stuff with JDK 1.5 (god I hate Sun’s stupid fascination with bizzarre numberology). Since for Hibernate this is really just about a different API not actual new functionality, it is a pretty safe bet so far as production stability. Its also no longer a moving target really. I stand by my notation that Spring offers very little to Hibernate3. I suggest that it complicates H3 use on recent versions of WebSphere as in my experience it is much simpler to get H3+Spring to work on WS 5.1-6.0 rather than H3. I did not suggest one way or another whether non-ORM based Spring should be used as that would be somewhat outside my experience. It might not be my choice because I dislike XML configuration particularly hierarchial embedded XML configuration, but I suppose if there was something I needed in Spring’s library of functionality, why not? I should note that JDK 1.5 (or JDK 5 if you care about Sun’s weird number fascination/marketing) indeed seems to be more stable in high capacity environmnets than is 1.4 due to the rewritten GC (1.42 parallel GC is actually a bit buggy) even if 1.5 introduced some odd new Hotspot issues. Organizations are likely to notice performance increases from JDK 1.5 and thus could consider beginning to use JDK 1.5 features such as annotations.

]]>