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.

[ANN] AppFuse 1.8.1 Released

This release is mostly a bug fix release with no new features. It also includes many upgrades to the core libraries (Hibernate, Spring, iBATIS, MyFaces). Thanks to all the sponsors who have contributed products and free hosting to the AppFuse project. You guys rock!

To see how AppFuse works, please see the following demos:

Comments and issues can be sent to the mailing list or posted to the AppFuse Issue Tracker.

Posted in Java at Jun 15 2005, 11:00:42 PM MDT 8 Comments

Hi, Matt. I would say that you have done a good work. What's next in your plans??? Do you planning to plug Wicket Framework to appfuse frameworks garden?? I have already working with it 2 month and from my side I would say that Wicket is *really* intresting framework and worth a stare. You should definetely dig into it.

Posted by Anatol Pomozov on June 16, 2005 at 08:07 AM MDT #

Matt, Could you integrate it with as well ;)

Posted by on June 16, 2005 at 01:37 PM MDT #

I don't have any plans to add Wicket, or any other frameworks for that matter. This is mostly because folks don't want another framework. In addition, Wicket doesn't seem <em>enterprise ready</em>, as it's got pretty low numbers in the following categories:

<ul class="glassList">
  • results for "wicket java": 0
  • Books on 0
  • Resumes on 1
  • If the Wicket team can make those results competitive with the rest of the frameworks, I'll consider it.

    Posted by Matt Raible on June 16, 2005 at 04:35 PM MDT #

    -- begin rant --

    I can't conclude from that article that folks don't want another framework. Some of them don't. Others do.

    I can tell you why I wanted another framework (and ended up being active for one). model 2 web frameworks suck!. I am saying this as an architect, who sees developers struggle with 'model 2' frameworks every day. They do not encourage good coding, no matter how well you try to manage that (and unfortunately, JSF is not going to help here either). They do not help with reusability, giving us problems with projects that have slightly different versions. Code duplication all over. And I could go on like this for ages. When I joined Wicket (as a user), I wasn't looking for fun, fame, or whatever. I was looking for a solution to the many problems we encounter on a daily basis when working with Java to build web applications.

    The last three projects that were started at the shop where I work were .NET projects. And they are doing good. Sure the devs complain that they like Eclipse better etc, but the end of the day, they deliver faster and more focussed on customer needs. Now, the shop that I work for still believes Java is superiour for most of our projects, but we need to get better development performance and maintainability etc when building java webapps.

    Your idea of enterprise ready sure is not mine. You base it on the idea that something has to be popular to be good, and that companies will only use technology that they have heard of. In many cases they don't care. And they shouldn't, as long as the job gets done properly. And as for the developers... when we hire people (and we do that on a regular basis), we are solely interested in whether they are smart, fit the team, and for experienced people, whether they can handle OO right. As for the frameworks... we just expect a developer to learn one within a couple of days or maybe a week or two. Period.

    -- end rant --

    I regret that I didn't give Tapestry a chance a couple of years ago. The learning curve is high (the major reason for the existence of Wicket), but if we were a Tapestry oriented instead of a Struts/Webwork/Maverick oriented shop now, we wouldn't have had a lot of the problems we experience today.

    Now that I've said this all, I don't think you should put Wicket in AppFuse. If you would, you should also put in Echo for sure. What I do think you should do, is to protect the world and throw out the model 2 frameworks :) Just have Tapestry and JSF, and add Wicket and Echo when they are popular enough.

    Posted by Eelco on June 16, 2005 at 06:31 PM MDT #

    Eelco, can you tell me how to run .NET on Unix, Linux and Windows at the same time? Many of our customers are moving to Linux servers at the moment. I've been forced to do development on Windows for the last 15 days and it dies once every day with the same hardware and software I use with Linux (haven't seen this for years on Linux). I doesn't matter how good .NET is (I think it's just a bad copy of Java, MS never ever invented anything in their whole history), it does not work on decent operating systems.

    Posted by Lars Fischer on June 16, 2005 at 10:14 PM MDT #

    Oh, well. Don't get me wrong, I'm on your side. I mean, I absolutely hate any vendor lock-in, and MS is king at that. But let's be real. I have seen allmost just as many Linux boxes die. As long as you don't run more than 10 programs on it, you can get by on a MS box (though you should NEVER put exchange on it). The only really stable machines I ever worked on are AS/400s (which are pretty good at doing Java stuff btw). It is funny that you think MS copies from Java. VS copies refactoring etc for sure, but the Java world copies just as much, the most famous being ASP - JSP. But JSF is supposed to be an answer to .NET (aspx) as well.

    Posted by Eelco on June 16, 2005 at 11:24 PM MDT #

    I'm curious to know how you would work security into jboss now. I know that on the wiki the jboss documentation discusses using the jboss frameworks, but I believe this is prior to integrating Acegi Security. Would you recommend using Acegi Security for JBoss deployment? I'm assuming so since the main reason you switched to acegi was for cross platform deployments. I'm just not sure what changes need to be made to have acegi work for jboss. Are there any changes for that?

    Posted by Mark Johnson on June 24, 2005 at 08:30 PM MDT #


    Acegi does a lot to simplify deployment of AppFuse - in any app server. You shouldn't need to configure any authentication settings anymore - just the JNDI DataSource. If you do want to customize the login query or something similar, you can modify web/WEB-INF/applicationContext-security.xml.

    Posted by Matt Raible on June 27, 2005 at 04:25 AM MDT #

    Post a Comment:
    • HTML Syntax: Allowed