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.

Updated Presentations: Spring, AppFuse and Comparing Web Frameworks

As part of my trip to Norway last month, I had an opportunity to update many of the presentations I've delivered at JUG meetings and conferences. Of course, there's not a whole lot to these slides because I believe the real value is seeing them delivered. ;-)

The presentation on Test-Driven Development with Spring and Hibernate (a.k.a. AppFuse) will serve as the basis for my AppFuse Tutorial at OSCON. If you're planning on attending that tutorial and would like to see any enhancements, please let me know. All of these are downloadable in PDF format.


NOTE: I updated this site to the latest code from Roller's CVS this morning, so please let me know if you see any issues.

Posted in Java at Jun 07 2005, 12:36:43 PM MDT 4 Comments

I look only at presentation about framework comparison. It look nice and concise but one major topic is missing ? performance. This is very significant because it seams that JSF has serious issues with performance on larger load and complicated GUIs with many components.

Another very interesting topic is Ajax support as you mentioned on last page. It will be very interesting to define architectural position of Ajax. I.e. does it call business service layer directly or those calls are directed via presentation controller. I practically doesn't know anything about Ajax so please forgive me if this question is trivial.

Damir Murat

Posted by Damir Murat on June 07, 2005 at 04:30 PM MDT #


Matt blogged about web frameworks. Leaving a note about Ajax. So here's my take from a DWR point of view:

Posted by Joe Walker's Blog on June 08, 2005 at 03:31 AM MDT #

Hey Matt, Thanks for sharing this! I admire you tremendously, but I disagree slightly with your assessment of testability of Struts. I've been using Struts since 0.5 (really!) back when Craig answered questions on the list personally. I am also an XP Coach so I know from test-driven development. It's relatively simple to construct your Actions so that they're testable, even in the absence of a "real" HttpRequest/HttpResponce. You can write your app so that the interesting stuff is already in the Form, and that can be mocked quite easily. So with a mock form you can exercise your action's handling of business logic without any servlet container. The Action then has no dependency on the request, response, or session. So that leaves the JSP. That's a problem. If your JSP contains no Java (only tags) then that removes one area of difficulty. However, problems of what gets presented, the interface between the form tag and the Struts Form bean, and other similar issues are still an issue, and the only way I know of testing is manually :-(. But we could build some tools...

Posted by John Tangney on June 08, 2005 at 05:19 PM MDT #

Matt, I like the updated presentations. Your list of evaluation criteria is useful, but might be better presented as a features-benefits matrix. This is a trick I came across years ago when Microsoft first released the PocketPC. Their site was intended to present marketing material to both novices as well as established Palm users, and it did a very good job at presenting not only a list of features, but the benefit of the feature to the consumer as well. A features-benefits matrix would explain, for example, why Spring integration is important to a framework.

Posted by Sid Bala on June 14, 2005 at 09:00 AM MDT #

Post a Comment:
  • HTML Syntax: Allowed