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.
My flight leaves Denver around 3:00 and is supposed to arrive at SFO at 7:15. If I'm good, I can grab a taxi and make it to Moscone before registration closes at 8. I doubt it, but it's worth a try. If it's closed, I'll head to my hotel and try to hook up with Bruce, Bill or Simon. Leave a comment or shoot me an e-mail if you are around and want to hook up tonight.
Igor Polyakov is the winner of the AppFuse Logo Contest! I didn't get many votes from the mailing list - but of the 7 votes I received, 5 were for Igor's logo. Since it was my favorite too - I can't complain. Congratulations Igor - we dig your design!
I have a feeling that Maven and I will never quite get along. I live on the bleeding edge, because you have to if you want to keep up with open source. I'm using Hibernate, Spring and JSTL in my Maven sample app. Hibernate is pretty up to date - ibiblio has 2.1.3 and 2.1.4 is the latest. Spring's JARs aren't too bad - 1.0.1 vs. 1.0.2 being the latest release. So much for getting spring-mock.jar quick and easy - since it's part of 1.0.2. JSTL is one version behind too.
Lesson learned: if you want to stay on the bleeding edge, don't use Maven. I suppose another option is to become the guy who uploads these new versions. That job looks rather complicated though. I'm guessing that most folks are simply maintaining their own repositories (or staying away from the bleeding edge).
One of Maven's best features is its ability to generate websites with project documentation. In most cases, it'll motivate developers to improve the documentation for their project. At least it has for me with Struts Menu. However, Maven makes the worst mistake in the history of web development - it doesn't set a default background color. A lot of idiots do this these days, so do me a favor folks - change the default background color on your browser to something obnoxious. Mine is set to bright orange right now. Try changing yours to orange and then visiting the Maven site - its fugly.
This issue isn't as bad as it used to be. Most people don't notice it, but "back in the day" when browser's used gray as their default - it was an issue. Maybe I'm just old fashioned.
Anyway, back to Maven. Yesterday, I was responsible for upgrading some Maven sample apps to the latest RC3, which makes the mistake mentioned above (RC1 did not). Usually when you encounter these issues in Mavenland, you click 5 times (Google with Firefox makes it 1 click) to find the plugins site and then look for its properties. In this case it's xdoc, which has a horrendous number of UI Color Settings.
These settings have two major problems. First of all, they don't work with RC3, and secondly - it's an awful way to define the colors and such for your site. Especially since its mostly related to colors. A better way that I've found is to put a maven-theme.css file in your xdocs/stylesheets directory. This will override Maven's default stylesheet and you get a lot more control over the look and feel of your Mavenized project site. The easiest way to get a template to start with is to generate your site and then copy target/docs/style/maven-theme.css into this directory. Hope this helps make Maven a little bit easier. 
Java One Blogger Meetup on Monday. Be there or be square. I'll be around Sunday night if anyone wants to do a little pre-party before Monday. My goals for the week are to attend at least 5 sessions and meet some folks that I've never meet before. Who's bringing the chasers? ;-)
EJB Solutions has changed their name to Open Logic and Out-of-the-Box has become Blue Glue. Why do I care? Because I start working for them (as a contractor) tomorrow! It'll be cool to work for a company that's just changed their whole website and released a new version of their product. Sounds like my kind of environment. It's kinda strange that their press releases have next Monday on them - I guess to coincide with JavaOne?
I've never been to JavaOne before, but this year I'm attending thanks to SourceBeat. I was planning on attending this conference as I do most - show up, look at the sessions and attend the ones that sound interesting. If it's anything like the MySQL Conference I attended in April, I won't be attending many. There were a lot of PHP and clustering sessions that just didn't interest me, so I only attended a few sessions each day. Compare that to NFJS, where there were many interesting sessions that same time and I hated choosing one over the other.
JavaOne is approaching fast and we'll all be there in 10 days. There seems to be a lot of folks planning what they're going to see each day. Is this a good idea, or can I get away with wingin' it? What about the parties - I've heard about them, but I have no idea what they entail? Are they corporate sponsored - or just a bunch of guys going out drinking together?
An interesting post titled "Project and Build Structure" showed up on javablogs.com today. As I began reading the project structure layout, I thought, "that looks good." It wasn't until I viewed the build.xml file that I realized that Seyed had copied AppFuse and modified it to his needs. This is fine and the license allows you to do this. However, Seyed's post seem to indicate that he is coming up with all of this stuff on his own. It seems, to me, that Seyed is (so far) in violation of AppFuse's license. Of course, if he'd merely give credit to AppFuse, he'd be free and clear! ;-)
I need a logo for AppFuse. I don't care if it has the name "AppFuse" in it or if it's just an icon sort-of-thing. I'm primarily looking to replace the default icon on java.net - but good project logos are always cool. Hopefully it will imply what AppFuse is (a jumpstart kit for java webapps), but I'm more keen on a good-looking design that anything. I'll buy the winner an iPod mini. If you have a logo you'd like to submit, please upload it to my wiki using the "Attach File..." link at the bottom of the page.
Update: Wow - there's already 8 entries in 24 hours! Sweet! I think I'll end the contest next Thursday, (the 24th) and announce a winner on Friday evening.
SiteMesh is a kick-ass tool. It's much easier to use and configure than Tiles, although I don't know if its as powerful. Tiles has Controllers that you can assign to a definition and it supports easy i18n. I've been using Tiles for over 3 years and I've only used SiteMesh for a few months. However, SiteMesh already seems to suite all my needs. I'm guessing that most people use Tiles over SiteMesh because they haven't given SiteMesh the 10 minute test.
Anyway, back to the point of this post. Rick Reumann has put together a nice tutorial titled Use SiteMesh instead of Tiles.
I think you will quickly see the benefits after going through this brief example. In summary, the main reason I like SiteMesh more than Tiles is that SiteMesh is much easier to configure and use (less typing and easier to understand).
Good stuff - thanks Rick! As part of the WebWork integration into AppFuse, I was planning on using SiteMesh. I'm already using it in Spring Live sample app and it's pretty slick. I haven't had to touch it since I integrate it. Compare this with Tiles where you have to add a new definition (or JSP) everytime you want a new page. If nothing else, I think Tiles needs to learn from SiteMesh and add a Filter that can be used to decorate pages.
