Spring 2.5 and the runtime paradigm shift
I just finished reading up on the new features of Spring 2.5 and I have to say I'm pretty excited. One thing that bothered me from the start of the Spring project has always been the need for xml wiring of components. No matter what you do in Spring land, you will have to create at least a minimal stub of xml in your config files to make your component known to Spring. And now, the freshly released 2.5 version of Spring is reaping the benefits of annotation driven development and completely does away with that.
Never mix Spring transactional aop:advice and TransactionProxy
...just don't do it. I used to work with TransactionProxyFactoryBean quite a lot, back then when Spring 1.x was out and it worked quite nicely - especially when dealing with HibernateInterceptor as a preInterceptor it was quite useful. So imagine my surprise when I tried to mix out the new, shiny Spring 2.0 <aop:advice></aop:advice> anotation based @Transactional support: All session management code stopped working.
Fixing crashy Eclipse installations
I've been suffering permanent Eclipse crashes. Especially when developing with the WTP on Tomcat. I found that it just takes some tweakage on the eclipse.ini file to get rid of this noisy little OutOfMemoryException permGen fucker. Here it is, my eclipse.ini. It works like a charm for me.
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256M
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx512m
-XX:PermSize=64m
-XX:MaxPermSize=128m
Powered by FireStats