Matt RaibleMatt Raible is a Web Developer and Java Champion. Connect with him on LinkedIn.

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 1.0 will support iBATIS 2.0

According to this post on the Spring forums, Juergen has just added support for iBATIS SQL Maps 2.0. Very nice!

Posted in Java at Feb 24 2004, 05:49:41 PM MST 6 Comments

Ok, what is very nice about SQL Maps? You're writing most of the SQL in XML format. What's nice is something like OJB, where you simply map the relationship of the bean to the DB table and go on from there. To store an object you're doing a simple store(Object) and you're done, it's even less work than SQLMaps claims. Of course this is just my stance on this. There is always something for everyone out there. R

Posted by Robert S. Sfeir on February 25, 2004 at 01:10 AM MST #

Robert - Personally, I don't use iBATIS, but I have in the past. It's very useful when you have to talk to a convoluted database and/or SQL already exists. I used it on a project last fall where they already had JDBC/SQL with 4 or 5 table joins in the SQL. It was cleaner to put the SQL in XML files and use its caching support. Personally, I use Hibernate, which is definitely easier.

Posted by Matt Raible on February 25, 2004 at 02:24 AM MST #

BTW, with my <em>very nice</em> statement, I was merely trying to say that I dig Spring is supporting the latest version of iBATIS.

Posted by Matt Raible on February 25, 2004 at 02:25 AM MST #

Thanks for clarifying that :-) Now Hibernate v/s OJB, that's an interesting discussion :-)... kidding. Thanks R

Posted by Robert S. Sfeir on February 25, 2004 at 02:31 AM MST #

I have been trying to take a look at spring. Anyone know where I can find some very simple examples that are not web baseds apps. I would like to use a simple example that shows off interception. I would like to also like to use its hibernate some junit tests without having to worry about closing the session. Thanks

Posted by Matt Payne on February 25, 2004 at 01:23 PM MST #

Spring-based Hibernate interceptor code isn't dependant on a j2ee container (unless you are using jndi datasources, and those can be easily changed to non-jndi datasources in the Spring config). Just create a classpath or file-based xml application context in your unit test, and the same Spring-based classes should run. The Spring jpetstore example in CVS, borrowed from ibatis, along with Juergen's Spring/Hibernate paper, was my original starting point for persistence/transaction interception. As for closing sessions, I'm not sure what you mean by that. Spring handles the opening and closing of Hibernate sessions internally, without regard to environment (web or otherwise).

Posted by Jason on February 25, 2004 at 04:42 PM MST #

Post a Comment:
  • HTML Syntax: Allowed