VMware offers training and certification to turbo-charge your progress.Learn more
Welcome to another installment of This Week in Spring! As usual, we've got a lot to cover, so let's get to it.
</a> <LI> The ZeroTurnaround blog has a <EM> really</EM> cool little blog on rapid development with Spring and Hibernate. Of course, Zero Turnaround has a handy little software agent that lets you reload Java classes on the fly. So that's a <EM>huge</EM> gain in productivity right there. That, coupled with XML-free Spring 3.1 and Hibernate 4.1, and you have yourself a <Em>really</EM> awesome combination. To learn more, check out the blog! The example he illustrates are also well <a href = "http://github.com/cloudfoundry-samples/springmvc-hibernate-template">represented in this sample project on GitHub</A>. The example even includes <CODE>web.xml</CODE>, even though it isn't required, just as was done in that blog post, specifically because it's more reliable on the buggy versions of JBoss 7 and Servlet 3 environments aren't ubiquitous, yet. This is a seriously cool blog post, be sure to read the followups! </LI>
ApplicationContext, including some tidbits about it that I'd long since forgotten! Very nicely done, Joseph!
is the one I've been waiting for! It's a very nice read, and I'm glad they've shared it with us, complete with working code and a blow-by-blow breakdown of the pieces. OAuth is complex, Spring Security OAuth (not yet GA!) makes it much simpler, but it's still nice to have guidance. </LI>
UserDetailsobject backed by Hibernate entities (of your own design).
<a href = "http://biju-allandsundry.blogspot.hk/2012/08/spring-configuration-and-factorybean.html"> some of the nuances of using Java-based configuration </a>. Specifically, he reminds us to let Spring provide the lifecycle callbacks by routing things through @Bean methods, instead of instatiating the objects directly. </LI>
importstatements. Normally, these statements are not able to see the property placeholders of the current application context, but nested contexts can see the property placeholders of the parent contexts. Solution? Simply instantiate everything in a child context so that the
importstatement can use the parent context's properties! This trick's kind of sneaky! I like it.
Remember, child contexts provide scoping - beans defined in one child can't see beans defined in another. This makes it very useful for things like Spring Batch Admin, which lets you upload and launch new Spring Batch jobs (which themselves are based on Spring configuration) on the fly.
<LI> The Middleware magic blog has a nice, complete post on configuring <A href = "http://middlewaremagic.com/weblogic/?p=8092"> Spring to talk to a JBoss AS 7-managed JMS instance</A>. The example is particularly involved because of all the work required to setup JBoss and to build up a client connection to it. </LI>