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.
It's time to update my blogroll with the sites I'm actually reading now. I still click on the links on my blogroll every-so-often, but there are some that are hardly ever updated. See ya, it was fun reading when you provided regular content. ;-)
I've just noticed that a new version (1.0.3) of the JSTL reference implementation has been released containing some minor bug fixes. [Simon Brown]
Hmmm, no release notes eh? Makes you wonder if it's worth the upgrade/headache. I'll be in for it for quite some time with my struts-resume project. I'm using 17 different OSS packages - it'll be a maintenance nightmare to keep up. That is, until I break down and do some Maven integration.
I think we're going to have to upgrade our Tivo. This OS X - Tivo integration looks like a good enough reason for me. Not to mention controller the shows you want to record from a web browser.
Jason doesn't like my Validator that matches two fields. I was just trying to help the Struts Community out by solving a problem that many have asked for. Oh well, I guess those WebWork folks will take any opportunity to bash on Struts ;-).
This is just another example of Struts making the common things hard. I'm more and more glad we went with Webwork, and once Xwork 1.0 / Webwork 2.0 are here, I'll be in nerdvana. [Jason Carreira]
Personally, I still think the Commons Validator is easier - you don't have to write any .java files in most cases (except for my extension, which will hopefully soon be added). I do like the ExpressionValidator - that looks cool. All in all, I think I'd bash on WebWork a little more - but I don't know enough about it. Where's the book ;-)
BTW, this post was sent (and edited!) via NetNewsWire. Very cool - but no titles.
I knew this trick existed, but I couldn't remember it. If you to drill down through your directory structure all the time, this is a real time saver. In Windows Explorer, you can highlight a folder and full expand it (and it's children) using the * key on your far right keypad. Using the - key will contract all folders. Other good Windows tricks I know are using the Win Key (that's the one with the Windows logo on it). Win+r = run, Win+e = explorer and Win+d = desktop. And last but not least, in Win2K+ right-click >> Properties on My Computer will get you to System Properties. If you have other good tips for Red Hat 8, OS X or Windows - please share!
If you're using Oracle 9i and JDK 1.4, you might be interested to know the recommended JDBC Driver is no longer classes12.jar (I just discovered it from the tomcat-user mailing list). The Readme.txt (at least on Win2K) in $ORACLE_HOME/ora92/jdbc states the following:
New classes file name for JDK 1.4 and beyond
Beginning with this release the classes files for JDK 1.4 and
beyond will be named ojdbc<jdk ver>.jar. So, the classes file for
JDK 1.4 is named ojdbc14.jar. The names for the JDK 1.1
and 1.2 classes files will not be changed. We will not provide
.zip versions of the classes files beyond JDK 1.2.
I'm sure most of you Java Developers have a methodology for handling your "constant" values. I've seen a couple of different techniques, and I'd like to see what everyone else is doing. Currently, I use a Constants.java file that has a bunch of public final static String lines in it. I got this technique from the struts-example app when I first started working with Struts. I recently came across (can't remember where) a technique where the Constants.java file was an Interface and it was simply implemented. How are you handling this in your apps?
Secondly - do you ever use these Constants in your JSPs, or do you just use the actual values? I use the actual values - less typing.