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 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.
For those folks looking for pretty HTML when doing a "view-source", they might want to check out the JTidy Filter. I tried to integrate this into AppFuse, but no dice. It never prettied up the HTML - maybe it's a SiteMesh conflict or something, who knows. I doubt I'll add this to AppFuse. Mostly because no customer/project has ever asked for this and because I couldn't get it to work (failed the 10 minute test, but I actually spent an hour on it).
Adrian Sutton hits the nail on the head:
...for seasoned veterans who understand (its) technologies well, AppFuse should be a big time saver. I can see a lot of beginners getting into very deep water with it though.
AppFuse can help you get started quickly, but it won't help you really learn how to use the different technologies. Its tutorials are designed to show you how to CRUD a simple object, but that's about it. For learning the different frameworks, that's what books are for. Technical authors put a lot of time and energy into writing. A good way to show your appreciation is to buy their books. 
My Recommendations:
Technology blogs are boring for the most part. Sure it's cool to read about someone configuring or trying something out for the first time. However, if you run a technology blog and you read through your archives, chances are there's not much in there that peaks your interest anymore. Part of the reason I started this blog is so I could look back over the years and see what was going on in my life. This is one of those posts. One of those posts that I'll look back on and appreciate.
2005 has been a pretty good year so far. This is largely in part to the fact that I don't work from home anymore, and therefore get some interaction other Java junkies. Another thing that's made it really nice is riding to work. I've ridden my bike to work every day since I started doing it. My goal is to ride everyday but those when it's raining in the morning, or when I have one of those "Oh shit!" mornings and I'm late for a meeting. I think I can ride all but 5 days this year. The past couple of weeks, it's been pretty cold (20-30°F), but it's actually been quite nice. It's a lot like skiing - you just have to dress for it.
Another reason I've been enjoying myself a lot is b/c I haven't been working on the weekends or late nights. I've been sleeping in, going to bed before midnight, and having a good time with Jack and Abbie. Last weekend, Abbie I went to Ocean Journey and the Colorado Crush game. Apparently she had a good time b/c when I asked her if she was excited about the DU Hockey Game this weekend, she said "Football!". Looks like we might be going again.
Jack is growing up fast and is already in 9-month outfits and he's only 5 months old. Since Holly moved in, he's been "Happy Jack", which is nice considering he cried 12 hours/day for the first couple of months. He's smiling a lot, squirming like a madman and even rolled over a couple of days ago. Before we know it, he'll probably be crawling and chasing after his big sister.
Last, but not least, I'm learning that I need to take advantage of my contracter status more. Today I took the day off to work on Spring Live. I hope to start doing it more often, as well as taking days off to work on AppFuse. My strategy for that is: go in early and work 4 10-hour days per week. If I'm in the office by 6, I can be home by 6 and hardly anyone notices.
Speaking of AppFuse, it continues to be popular and has the most mail traffic on java.net. While that's great, it's tough to keep up with the mailing list. I've started to not reply b/c I need to get other things done. The last two weeks of this month, I plan on pumping out new AppFuse and Equinox releases, so I'll likely get back into it then. Developing open-source projects is a lot of work, but it's a nice way to show clients your knowledge.
That's pretty much it. Julie continues to be the woman of my dreams and it's awesome living in a new/big house in the heart of Denver. I don't know how much I'll update this blog in the next few weeks - sometimes it's just better to quit e-mailing and blogging and get some work done. 
If you've heard of iBATIS, but never had the time to look into it, there's a good intro article on ONJava.com: Object-Relational Mapping with SQLMaps. iBATIS continues to be my persistence framework-of-choice when Hibernate doesn't mesh with the database schema. Now if we could just get someone to write a Middlegen Plugin to generate POJOs and SQL Maps from database schemas.
From the WebWork Mailing List, I learned that the Eclipse Plugin for WebWork has released its first version - and it looks pretty nice (demos). To install using Eclipse Update Manager, use http://eclipsework.sourceforge.net/install/site.xml.
Larry Williams points out how to monitor Tomcat 5.5.x with JMX.
To monitor your Tomcat instance with JMX start Tomcat with the following JVM parameters.
-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9000 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false
I'm posting this hear so it's easier to find when I get time to try this out.
From the iBATIS mailing list:
Hi everyone, I just wanted to remind everyone of Alex Egorov's sql2iBatis tool. I've recently had the chance to try it. If you have a database that's already created, this will save you a lot of time. It will kickstart your project. Given DDL, it generates the SQL Mapping files and the JavaBeans. It's super simple and extremely fast. You may want to tweak the Perl to generate bean field naming conventions to your liking, or just refactor it afterwards. You might also want to run the source through Jalopy or your favorite IDE formatter to achieve the formatting you want. However you cut it, this tool will save you tons of time (even if you don't use everything it generates...deleting is faster than writing). http://alxeg.narod.ru/ibatis/index.html Cheers, Clinton
Too bad it's a perl script. It would be nice to add something like this to AppFuse so you could get the same generate-mapping-files thing like Hibernate has with XDoclet.
So most folks think Struts is Dead, huh? I've got news for you folks. Struts has been dead since 2002. For that matter, most Java frameworks have been dead for the last year. Most folks think Struts is dead because there won't be any new and whiz-bang features added in future releases. I'm willing to bet the other Java Web Frameworks won't add any whiz-bang features in the next few years either. Sure, WebWork might get a little XMLHttpRequest lovin' for client-side validation, and Tapestry might get pretty URLs - but both of these are features that these frameworks should've had in the first place. So what's the big deal? At least the Struts Developers have the guts to stand up and say "we're in maintenance mode". Shouldn't all framework developer's be able to say this? It's really quite an accomplishment.
IMO, the only developers that shouldn't be saying this are Tapestry and JSF folks. Both of these teams should be saying - "we're going to make our frameworks easier." If these frameworks are going to be the future of Java web development, there's some work to do. The JSF folks should be saying, "we're going to fix all the stuff that's broken". This "stuff" includes POST for everything, lack of bookmarkability, and bad validation messages (the good news is the validation messages should be fixed in JSF 1.2). I think Tapestry needs some simplification too. In my experience, most Tapestry pages (by design) require 4 files. One for the Java class, one of the HTML template, one for the page specification and one for the i18n keys. This should be easier. It'd like to see two required files (template and Java class) and the others are optional. Maybe annotations could eliminate the page specification? I think there's a lot to be learned from frameworks like Ruby on Rails: default everything, allow overriding.
I think that Shale will be good, but only if it learns from the other MVC frameworks available. If I were on the team, I'd take the good things from all the others: IoC, Interceptors, HTML templates, etc. I wouldn't stop there either - there needs to be good examples of how to integrate it with middle-tier frameworks like Spring, Hivemind and EJBs. Often developers will take examples as recipes - so the more detailed and simple, the better. The Struts developers have quite an opportunity to make something great, let's hope they don't just create another framework.
This has been a good month for Raible Designs. Not only did I manage to land a new gig, but I've also had a couple of 1-day contracts. The first one was an architectural review (at the beginning of the month), and yesterday I delivered a presentation on TDD and Spring for a client. These short-n-sweet gigs are a lot of fun. It's a good way to get out and meet members of the Java Community and see what tools they're developing with. The first client is using Struts, Spring and Hibernate. The second client wanted to use Struts, but after my talk, they're thinking about Spring MVC. They plan on using Spring to make EJBs easier, and they're using TopLink on the backend.
The only bad part about yesterday's experience is I developed a full-body ache as soon as I left the client's site. I managed to catch a cold from Abbie this weekend, and that turned into a cold+fever last night. I've had the fever ever since and didn't go into work today. It's really shitty timing for getting sick - we have a deadline on Thursday and we're heading to Oregon to see my parents this weekend. Last I checked, my fever was at 102°F. Hopefully, I'll wake up tomorrow and it'll be gone.
Apparently, the Dallas JUG will have the pleasure of listening to a presentation on AppFuse this Wednesday. I can't seem to find any information on their site, but someone forwarded me an e-mail that looks genuine. You know a project is getting popular when other people are giving presentations on it!
