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.
Remember when I thought Sun/java.net was trying to make GlassFish look more popular than it is? It looks like they took it up a notch in August. Not only do they have the top spot in "most accesses", but they have the top 2 spots!
Isn't it possible to automate these stats instead of using a spreadsheet? 
I spent some time this past weekend getting automated builds setup for AppFuse 2. Since the project now uses Maven 2, I figured I'd give Continuum a try. I pointed it at my pom.xml in SVN and expected everything to work out-of-the-box. No dice. It seems that Continuum reads the artifactIds instead of the module names for sub-project resolution. To workaround this issue, I'd basically have to rename all my sub-projects to have an "appfuse-" prefix. Doesn't that violate the whole DRY principle? Sure, there's projects that do this, but there's others that don't.
Since I didn't feel like renaming the modules/directories in SVN, I gave CruiseControl a try instead. It took a bit of elbow grease on my part, but I ended up with a config.xml file that works splendidly. It seems somewhat ironic to me that the CruiseControl works better with Maven 2 than Continuum does.
Last week I managed to get AppFuse to compile with Maven 2, this week I got all the tests passing. This week, I struggled with Maven's WAR dependencies and how AppFuse will be used by end-users. It was frustrating, but I think I got most everything figured out. Unfortunately, there's still many issues to be sorted out.[Read More]
Steven Haines appears to be gearing up for a showdown among Java web frameworks. In his Web Frameworks article (found via dzone), Steven notes the following:
There are many factors that you need to consider when choosing an application framework, including but not limited to:
He goes on to say that he's planning on comparing a number of web frameworks, and his study will give special attention to how these frameworks perform. He'll be comparing Struts 1.x, Struts 2.x, Shale and Spring MVC. If you think your framework can compete, Steven invites you to send him an e-mail.
If anyone has a compelling reason why we should add an additional framework, please contact me and I will be glad to consider it in this endeavor.
I'm looking forward to reading Steven's articles, I just hope I can find them again when they're published.
I managed to get most of AppFuse's code moved over to a Maven 2 structure
this week. I have tests working in the hibernate/ibatis projects, as
well as the service project, but not in the web tier projects yet. I
do have everything compiling though.
[INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] ------------------------------------------------------------------------ [INFO] AppFuse ............................................... SUCCESS [2.228s] [INFO] AppFuse Common Data Module ............................ SUCCESS [1.681s] [INFO] AppFuse Hibernate Module .............................. SUCCESS [0.809s] [INFO] AppFuse iBATIS Module ................................. SUCCESS [0.630s] [INFO] AppFuse Data Modules .................................. SUCCESS [0.008s] [INFO] AppFuse Service Module ................................ SUCCESS [0.696s] [INFO] AppFuse Common Web Module ............................. SUCCESS [2.817s] [INFO] AppFuse JSF Module .................................... SUCCESS [4.410s] [INFO] AppFuse Spring MVC Module ............................. SUCCESS [4.038s] [INFO] AppFuse Struts 2 Module ............................... SUCCESS [4.954s] [INFO] AppFuse Tapestry Module ............................... SUCCESS [4.042s] [INFO] AppFuse Web Modules ................................... SUCCESS [0.007s] [INFO] ------------------------------------------------------------------------ [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: 26 seconds [INFO] Finished at: Fri Aug 18 15:06:54 MDT 2006 [INFO] Final Memory: 11M/26M [INFO] ------------------------------------------------------------------------
If you'd like to review any of the work done thus far, I've uploaded my latest work to:
http://static.appfuse.org/downloads/appfuse2-20060817.zip
The major issue I've encountered to date can be reviewed on the Maven user mailing list. If you happen to try things out, the best thing to do is post feedback to the dev list. I'm considering another device-free weekend, so I may not respond until Monday.
With all the recent hubbub about GlassFish, I decided to do a quick performance test this morning. I downloaded all the most recent versions of the various open source application servers, deployed AppFuse 1.9.3 (Struts version) on them, and ran "ant test-canoo" to see if any of them were faster than the other. This was by no means a scientific, isolated test. It also didn't take into account any performance tuning you should do on these servers, I just used the out-of-the-box settings.
I ran these tests on my MacBook Pro (2.16 GHz Intel Core Duo, 2 GB DDR2 SDRAM) with my JAVA_OPTS set to:
-Xms768M -Xmx768M -XX:MaxPermSize=512m -Djava.awt.headless=true
When typing "java -version" at the command line, I got:
java version "1.5.0_06" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-103) Java HotSpot(TM) Client VM (build 1.5.0_06-57, mixed mode, sharing)
Servers tested (in no particular order):
I'm pleased to note that all servers allowed me to deploy appfuse.war without using a console or command-line tool. They all support dropping the WAR in some sort of auto-deploy directory. Very cool! Secondly, I was able to successfully deploy AppFuse on all of them with no changes to AppFuse nor the server. Quite impressive.
My test consisted of the following:
Here's what I found:
| Server Name | 1st run (seconds) | 2nd run | 3rd run | Average |
|---|---|---|---|---|
| JBoss 4.0.4 | 24 | 23 | 23 | 23.33 |
| GlassFish B48 | 25 | 24 | 24 | 24.33 |
| JOnAS 4.7.6 | 25 | 25 | 27 | 25.66 |
| Resin 3.0.21 | 23 | 23 | 23 | 23 |
| Geronimo 1.1 | 28 | 23 | 23 | 24.66 |
Since I know you're going to ask about Jetty and Tomcat (the two main servlet-only containers), I ran the numbers on those too. First off, I tried Jetty 6 RC0. No dice - I got the following error when trying to start the server.
java.lang.IllegalStateException: Cannot initialize context because there is already a root application
context present - check whether you have multiple ContextLoader* definitions in your web.xml!
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:173)
Since AppFuse deploys on all the above app servers, as well as Jetty 5.1.x, I'll chalk this up to a bug in Jetty 6. I used Jetty 5.1.11 for this test because I already had it installed on my machine.
| Server Name | 1st run (seconds) | 2nd run | 3rd run | Average |
|---|---|---|---|---|
| Jetty 5.1.11 | 24 | 25 | 24 | 24.33 |
| Tomcat 5.5.17 | 23 | 23 | 22 | 22.66 |
I don't know that these numbers mean anything, but it was a fun experiment. For those of you who think these numbers might mean something, here's the rankings:
Of course, the better test would be hammering each server with 1000 concurrent users (or a number higher than that) and comparing how each server holds up.
I've updated the AppFuse Roadmap for the upcoming 2.0 version. The current plan is to have a few milestone releases before the final 2.0 release. I can't promise any specific release date because of developer's schedules and current commitments. However, my hope is we can have it done by the end of this year.
Milestone 1
Milestone 2
Milestone 3
2.0 Nice to haves
Let me know if there's anything that seems to be missing from this list.
If you can't wait until the end of this year, you may take a look at Patrick Lightbody's newly announced Project Able. He has a lot of good ideas in there that I hope to learn from.
Helge Tesgaard has written a nice tutorial on How to Create an AJAX-based file upload progress bar with AppFuse 1.9.3. Check it out if you have a need for such a thing. I especially like Helge's comment on productivity towards the end.
Yesterday, java.net updated their Top Ranked Projects page to reflect the top projects for July 2006. I've always thought these were fairly accurate. However, a couple of weeks ago, I did a bit of investigating (since GlassFish always seems to top all categories) and I found some interesting information. First of all, when last month's stats were first published, I noticed that DWR was on top of the "mailing list traffic" category. I did some investigating, and found the following:
DWR: 62 + 522 + 1 + 3 + 1 = 589 AppFuse: 65 + 134 + 542 + 21 = 762
So I thought, am I missing something? Why does AppFuse rank lower. I posted a question to the java.net forums, and got the following response:
I have a typo in my spreadsheet where I ran the numbers. Let me recheck and fix.
Thanks to Helen for her honesty, but isn't this something that could easily be automated? This would eliminate any calculation errors? Especially since there seems to be issues with the previous month's statistics.
For June 2006 (excluding AppFuse's issues and cvs lists):
GlassFish: 184 + 204 + 28 + 80 + 2 + 36 + 4 + 11 + 17 = 566 AppFuse: 684 + 19 = 703
AppFuse had more mailing list traffic, yet GlassFish is #1 and AppFuse is #3. Is java.net trying to make GlassFish look more popular than it is?
Looks to be a good show at tonight's DJUG: Justin Lee will be talking about Wicket and Tom Poindexter is presenting on Echo2.
BTW, did you know that Wicket may become an Apache project? I consider the main web frameworks in Java to be: JSF, Spring MVC, Struts 2 and Tapestry. RIFE, Stripes and Wicket follow close behind, but are generally very unheard of in the Java community at large. It's kinda wierd to see most of the Java web frameworks (save Spring MVC) end up at Apache, isn't it?
Update: This was a good meeting, mostly because both speakers were excellent. Relaxed, comfortable and good humored. Justin has a recap (and downloadable presentation) on his blog.