[House Project] First Wall
Bob the Builder told us they'd have all the framing done this week. Now we're starting to believe him!
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.
Bob the Builder told us they'd have all the framing done this week. Now we're starting to believe him!
The app I've been developing over the last 6 months is going live next week. As part of that process, my client decided they wanted to put the production database on their AS400, rather than their JDE/WebSphere/DB2 Server. Hibernate and AppFuse made this super-easy. Add the JDBC Driver, specify a new dialect/jdbc url/driver name, and voila - we're talking to DB2400! After creating the initial tables using Ant we noticed that the table names were too long since the 400 has a limit of 10 characters. To fix this, I simply modified my XDoclet @hibernate.class table="..." to have shorter table names. After that, I simply had to re-arrange a few tables in my sample-data.xml file (for DBUnit) to avoid referential integrity issues. All-in-all, we migrated from MySQL to DB2 on an AS400 in a little under an hour this morning. Hibernate makes my development life soooo much easier.
There's some discussions taking place on the Struts Developer Mailing List about what to do with Tiles. Tiles is gaining popularity in frameworks other than Struts - i.e. Spring and JSF. Personally, I don't mind that Tiles is buried deep inside struts.jar b/c it's basically the difference between a 500 KB JAR and a 100 KB JAR - and disc space is cheap! However, an advantage of extracting Tiles from Struts is that it then has the opportunity to become friendlier to other web frameworks. I'd even like to see a Sitemesh-like Filter so you could do Sitemesh stuff with Tiles. Or maybe just bundle Sitemesh with Tiles as a kick-ass templating engine.
So the question is: What should we do with it? Should it become a Jakarta Commons project or a Jakarta Project? Or even a java.net project? Tiles Users - we need your feedback!
Cameron has posted a comment on my Performance Tuning MySQL article. The reason I'm highlighting this because it's something I wasn't are of:
From the article:
-Xms128m -Xmx256m
The Sun JVM will run significantly faster with the following config instead:
-Xms256m -Xmx256m
That's because the Sun implementation acquires and releases memory from / to the OS way too aggresively if the "ms != mx". Furthermore, either your server has the 256MB available or it doesn't. If you don't have it available, don't set the max that high. If you do have it available, you gain nothing from setting the min lower. This isn't a desktop system, it's a server -- make sure you have the necessary resources and if you do then use them!
Time to change all my heap size setting since I've been using the first setting (128/256) for quite some time. Thanks Cameron! The real question is: will changing "-Xms256m -Xmx512m" to "-Xms512m -Xmx512m" speed up my slow-ass PowerBook? ;-)