Matt RaibleMatt Raible is a Java Champion and Developer Advocate at Okta.

The Angular Mini-Book The Angular Mini-Book is a guide to getting started with Angular. You'll learn how to develop a bare-bones application, test it, and deploy it. Then you'll move on to adding Bootstrap, Angular Material, continuous integration, and authentication.

Spring Boot is a popular framework for building REST APIs. You'll learn how to integrate Angular with Spring Boot and use security best practices like HTTPS and a content security policy.

For book updates, follow @angular_book on Twitter.

The JHipster Mini-Book The JHipster Mini-Book is a guide to getting started with hip technologies today: Angular, Bootstrap, and Spring Boot. All of these frameworks are wrapped up in an easy-to-use project called JHipster.

This book shows you how to build an app with JHipster, and guides you through the plethora of tools, techniques and options you can use. Furthermore, it explains the UI and API building blocks so you understand the underpinnings of your great application.

For book updates, follow @jhipster-book on Twitter.


Over 10 years ago, I wrote my first blog post. Since then, I've authored books, had kids, traveled the world, found Trish and blogged about it all.

Spring MVC's Conventions get even better

Spring 2.5.3 was released this morning and contains a new feature I really like. When I first started working with Spring MVC's annotations (way back in November of last year), I found it awkward that I had to hard-code the URLs for my controllers into @RequestMappings on methods. Previous to annotations, I was using Spring's ControllerClassNameHandlerMapping which allows for more conventions-based URL-mappings.

With 2.5.3, @Controller and ControllerClassNameHandlerMapping have been synced up so you don't have to specify URLs in your annotations anymore. Thanks guys!

Posted in Java at Apr 07 2008, 09:43:42 AM MDT 4 Comments

I saw the release news form this post. Thanks. I tested 2.5.3's ControllerClassNameHandlerMapping(CCNHM) on my sample application. And I found that CCNHM just find classes that have a @Controller and extended MultiActionController(MAC). And It recornise request handling method only have HttpServletRequest and HttpServletResponse parameter.(This is MAC's requierment not @Controller's) Is this right purpose of CCNHM's change? I thought CCNHM can recornise No-Servlet API used methods. :0

Posted by whiteship on April 07, 2008 at 01:12 PM MDT #

its weird. mine doesn't work. I used the 'ControllerClassNameHandlerMapping' with the same exact 'basePackage' declared in 'context:component-scan'. But when I called the path to the controller, it couldn't find the mapping, so i ended up using the @RequestMapping last night.

Posted by dodol on April 08, 2008 at 06:49 PM MDT #

okay i found out why the ControllerClassNameHandlerMapping didn't work for me... It was like whiteship said, the ControllerClassNameHandlerMapping only found the path to MultiActionController... not to the Form-Based Controller.

Posted by dodol on April 08, 2008 at 08:06 PM MDT #

I agree, this doesn't seem to work like I expected.

Posted by Matt Raible on April 11, 2008 at 09:03 AM MDT #

Post a Comment:
  • HTML Syntax: Allowed