Matt RaibleMatt Raible is a Web Developer and Java Champion. Connect with him on LinkedIn.

The Angular Mini-Book 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 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.

10+ YEARS


Over 10 years ago, I wrote my first blog post. Since then, I've authored books, had kids, traveled the world, found Trish and blogged about it all.

RECENT ENTRIES


Tag Cloud


abbie appfuse birthday denver family grails gwt jack java javascript jhipster jsf linkedin maven roller skiing softwaresummit spring springmvc struts2 travel trish vacation webframeworks wicket
« Hibernate's AdminApp... | Main | Interested in Java... »
Thursday December 18, 2003

Struts 2.0

There's a flurry of e-mails about Struts 2.0 dancing around on the Struts Developers Mailing List. Looking at the Overview or the ReadMe, you can see that there's some major (revolutionary) changes being discussed. The Struts Bandwagon is alive and well. The proposal is called Jericho (since it tries to tear-down the walls within the Struts architecture) and proposes to open-up Struts by:

  • Declaring interfaces for all core components.
  • Providing working base implementations for all core components.
  • Encapsulating alll path references within "Location" objects (fka ActionForwards) and referring only to Locations from all other objects.
  • Providing additional extension points from core components so that the "Inversion of Control" pattern is fully realized. (e.g., a populate method for the FormHandler.)
  • Providing "POJO" signatures that encapsulate servlet/portlet behavior so that applications can be freed of servlet/portlet semantics, if so desired. This strategy would also be applied to optional packages like Validator and Tiles.
  • Retain optional access to servlet/portlet objects so that applications can be free to do whatever they need to do.

Also under consideration - adding Struts Menu to the core. Good stuff my friends, good stuff.

Also noticed on the mailing list - Tomcat is not the Servlet/JSP reference implementation (news to me):

There is a (mis)conception, for example, that Tomcat is the RI for the servlet and JSP APIs. That is not the case -- the official RI is the "J2EE SDK" available at http://java.sun.com/j2ee/1.4/download-dr.html. It happens to *include* code from Tomcat, but this is the real RI.

Posted in Java at Dec 18 2003, 11:24:32 AM MST 4 Comments
Comments:

Wow, that's news to me as well... I just posted about how Tomcat was the reference implementation just last night. Interesting... did that change recently or sometime ages ago and I wasn't paying attention or was it never the case? But I did just notice that the quote from the Tomcat home page is: "Tomcat is the servlet container that is used in the official Reference Implementation for the Java Servlet and JavaServer Pages technologies. " Ahh. Very interesting... But if it's the servlet container used *in* the RI, then it has to be the RI? No? My mind hurts... -Russ

Posted by Russ on December 18, 2003 at 08:48 PM MST #

where is Jason the webwork troll. I should expect a post from him anytime commenting on how we should use webwork now and not wait for struts 2.0 blah, blah blah .Seriously struts+jsf is going to become the de facto standard and this just proves that. Webwork guys either have to put their act together and become less than a troll or just save their time and energy. Webwork offers few minors improvement at a very high price.

Posted by Michel on December 18, 2003 at 09:46 PM MST #

Puhleaze... You should be thanking us for coming up with the new ideas that Struts people are just figuring out would be nice... Maybe someday Struts 2 will be almost as nice as WebWork2... But we'll have kept moving. Use what you want, it's your head that will hurt trying to make crap work.

Posted by Jason Carreira on December 19, 2003 at 04:46 AM MST #

how i can deploy struts in portal

Posted by yerrapareddy on August 06, 2007 at 11:55 AM MDT #

Post a Comment:
  • HTML Syntax: Allowed