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.
We've all make it home safe and sound. This birth was pretty easy compared to Abbie's. We left for the hospital at 8:15 pm and Jack was born shortly after midnight. Julie was a champ - two pushes and he was out! Julie's mom and sister flew in so we've been having a great time with all the family around. Life is great in Denver right now.
The Whole Family
Wayne Parrott, the VP of Product Management at Genuitec (makers of MyEclipse) has started a blog.
For the past 3 years I have been involved with a great team at Genuitec (www.genuitec.com) of which I am a founder. While my title at Genuitec is VP, Product Management, I think of myself more as an Eclipse technologist and product delivery specialist. These days I spend most of my professional time working on Genuitec's MyEclipse Enterprise Workbench product. A quick fly by of my resume looks something like this: several startup failures, numerous consulting engagements, and some really cool work on the Human Genome Project and NASA's AI Section that dates back to the '80s.
Very cool! I love it when companies get closer to their customers via weblogs. Now we just need to get Wayne to start blogging some tips and tricks.
By default, Eclipse expects all its plugins to be in $ECLIPSE_HOME/plugins. This doesn't work too well for upgrading since you have to copy all of your installed plugins to Eclipse everytime you upgrade. To solve this, you can place all your plugins in an external direct and point to them using a link file. To do this, create a links directory in $ECLIPSE_HOME and create a file inside it that points to an alternate location. The name of this file doesn't seem to matter, but it must end with a ".link" extension. In this file, put a path:
path=C:\\Tools\\myplugins
Then in c:\Tools\myplugins, create an Eclipse-like directory structure so you end up with c:\Tools\myplugins\eclipse\plugins. Then drop your plugins in that directory. If you choose to use an alternate workspace as well, upgrading Eclipse will be as easy as copying in your links folder. BTW, here's more information
on upgrading Eclipse.
We recently switched from AT&T to T-Mobile for our cell phone service. There were two reasons for this - the primary one being that AT&T's customer service sucks. Every time we'd call them to get simple issues resolved, it would take upwards of 20 minutes to talk to someone. The 2nd reason we switched is because I ended up paying over $200/month in June and July. This was because I kept using my phone for dial-up while at NFJS and JavaOne. I shoulda had more data (I was at 4MB), but their max is only 12MB, and every time I'd try to change it, I'd get fed up with waiting to talk with someone.
Julie made the switch a few weeks ago.
After spending a 1/2 hour on hold (with Abbie crying the whole time) and then AT&T transferring her after she finally talked with someone - she'd had enough. A week later we received new T-Mobile phones. The phones are crap b/c they're the free ones, but they do work and we do have the same numbers. Now my problem is that I'd like to use my T637 with T-Mobile - but everyone seems to be giving me the run-around. I need to "unlock" the phone b/c the T-Mobile SIM causes my phone to display "Invalid SIM".
T-Mobile stores say to take it to AT&T, and AT&T stores say to call customer service. I've called customer service, and after waiting 20 minutes, they said to call Sony Ericsson. Now I come to you my mobile friends - Julie said she saw something on the web were you can send your phones in to get them unlocked. I don't know if it's legal, but I'm willing to do it if I can get my T637 working again. Any advice is appreciated.
The Java Community certainly does care about JSF. Regardless of whether folks like it or hate it - there's definitely a lot of opinions! Who woulda thunk a simple blog entry would get so much traffic? Wierd.
You know it's a late night when Erik posts before you go to bed...
I ran FindBugs on AppFuse last night and found/fixed a number of issues as a result. I'm now down to only a handful left - most of them being "Class is Serializable, but doesn't define serialVersionUID". I tried to generate one using serialver, but I couldn't it to work after numerous attempts. My issues seemed to be classpath related: it wanted the servlet api in my classpath, and once I'd add that, it could find my class. I'll have to try the SerialVer Ant Tasks. Fixing this issue would be nice, but I doubt it's really affecting appfuse-based applications. The other bug is "Inconsistent synchronization" in UserCounterListener.contextInitialized() method. Any tips on solving this one are appreciated.
I've haven't been developing applications with AppFuse since May. Instead, I've been using Equinox. One of the main things in Equinox I've grown to love is SiteMesh. It's worked in all the webapps I've written, which utilize frameworks like Struts, Spring MVC, WebWork, Tapestry and JSF. Tiles will only work in 3 of those.
I think it's time to make an executive decision on AppFuse and ditch Tiles in place of SiteMesh. It's faster and easier to develop with, and it doesn't get in your way. In fact, I didn't have to change a single line of SiteMesh-related code to support any of the aforementioned frameworks. Furthermore, using SiteMesh would also greatly reduce the duplicate between frameworks. I've thought about keeping Tiles around, but it's a pain in the ass to maintain parallel sets of documentation.
Whaddya think - any reason you can think of to keep Tiles? I can't. In fact, I think I'd cringe if I had to start my next AppFuse-based project w/o SiteMesh.
I just noticed tonight that the DJUG website got another makeover - and it looks great. Nice work Renee! Not only that, but the line-up of speakers and topics for the coming months is awesome: Dion, Mike, Bruce and yours truly. I actually enjoy DJUG meetings more than I do conference sessions. The speaker is not fixed to a certain time (though they are encouraged to be under an hour) and you get to have beers with them afterwards.
Which type of developer are you - Asshole or Moron? I'm a moron as far as I can tell. 
I got a free copy of Mark's Dive into Python at OSCON. Apress said they'd give it to me if I agreed to post a review on Amazon. I hope Mark's writing is as good as his blog.
I've seen OmniGraffle diagrams show up in a blog entry and and an article in the last week. Both diagrams show how OmniGraffle can produce high-quality, professional looking diagrams. The best part is that (I believe) it comes out-of-the-box with OS X. I seem to remember deleting it off my hard drive a while back b/c I didn't know what it was for. After seeing these sites, and realizing what OmniGraffle can do - I'll be searching through my Panther CDs in hopes of finding it. Anyone know where it's at and what version it is?
