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.
The good folks from JavaZone have published a video of the Comparing Java Web Frameworks presentation I did in Oslo in September. Enjoy!
Update: In this presentation, I say we've chosen Struts 2 at LinkedIn. Even though it solved most of our problems, I'm also now prototyping with Spring MVC. I wish JSP/JSTL had a way to call methods with arguments like Struts' OGNL supports.
Posted by Stephan on November 24, 2007 at 03:39 AM MST #
Posted by Jorge Diaz Tambley on November 24, 2007 at 06:47 AM MST #
Posted by Matt Raible on November 24, 2007 at 08:07 AM MST #
Posted by Sonny Gill on November 24, 2007 at 12:22 PM MST #
Posted by Magnus Heino on November 24, 2007 at 03:40 PM MST #
Posted by Matt Raible on November 24, 2007 at 04:24 PM MST #
Posted by David Whitehurst on November 24, 2007 at 07:59 PM MST #
Posted by reddeagle on November 26, 2007 at 09:46 AM MST #
Shouldn't be too difficult to create EL functions based on java.beans.Expression and/or java.beans.Statement.
Posted by Kris Schneider on November 27, 2007 at 09:10 AM MST #
> What is making you now look at Spring MVC for your prototype.
The reasons are more strategy and politics related than technical. They're already using Spring MVC in some applications and using Spring heavily on the backend, so they'd prefer to unify. Also, the fact that they're writing some Grails applications further supports Spring MVC.
Posted by Matt Raible on November 27, 2007 at 04:47 PM MST #
Good luck with Struts 2.
After the Struts2 tags mess with OGNL, and some strange behaviour with poor validation, and short comings with things like nested loops with struts tags I'm about to migrate my projects over to SpringMVC.
I understand the security concerns for removing the OGNL stuff, but seriously, a bug comes along and after a minor revision each JSP has to be updated to not use OGNL?!?! And this is the solution? That was the straw on the camels back.
Struts 2 is wonderful conceptual, and feels clean and elegant - then you use it.
You mention in your presentation (which I dug) about "you know, you make all these changes and implementations and you've basically written your own framework".
Thats where I'm at. Having to patch and reimplement base functionality so that it works without bugs. (An example of this is unselecting all items in a checkbox list - https://issues.apache.org/struts/browse/WW-992. The issue still exists, but its marked as resolved).
I dont have the luxury of time to patch this kind of thing - or investigate why its not working. (and i dont profess to be smart enough to figure it out either).
My experience with SpringMVC was that it works, the controller is slightly less elegant, but it WORKS.
I hope you are:
Posted by Ned on November 27, 2007 at 07:02 PM MST #
Posted by Ned on November 27, 2007 at 11:40 PM MST #
Posted by Ted Husted on November 28, 2007 at 06:42 AM MST #
Posted by Ned on November 28, 2007 at 04:38 PM MST #