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 jsf linkedin maven montana roller skiing softwaresummit spring springmvc struts2 travel trish vacation webframeworks wicket
« Hibern8 IDE | Main | StrutsCX Article »
Sunday March 30, 2003

WebWork Tutorial makes it look easy

I have to admit that this webwork tutorial makes WebWork look easy. In comparing this to Struts, it seems as if the Form and Action are the same thing. I wonder if I could use BeanUtils.copyProperties(wwAction, POJO) like I am with Hibernate/Struts currently.

The funny thing is that XDoclet has made it so easy (IMO) that I don't write ActionForm's anymore. All I really write is Actions, JSPs, DAOs and Services (a.k.a. Managers). So, with my current architecture I'm using, it actually looks like more work to use WebWork's Actions than Struts Actions. Especially since I have to write my validation in my Action. The XDoclet/Validator combo makes this super simple with Struts (and would with WW if they'd adopt it ;-). The only time I've been writing forms lately is when I have a form with indexed properties. Then I create a childForm that extends the generated form and has the appropriate accessors/mutators for the indexed properties.

The one thing the article does bring to light is how much cleaner Velocity is. JSP 2.0 will make JSP's a lot easier, but Velocity looks like it's already there. The one thing that worries me about using Velocity is that, according to their homepage, they haven't had a release in 8 months and their last release was a Release Candidate. What the?! Seems like someone might be dropping the ball on that project.

Posted in Java at Mar 30 2003, 11:26:58 AM MST 6 Comments
Comments:

Hey Matt,

You should definately check out webwork 2 (+ xwork). We're using (we'll they're, I'm trying to help out as much as possible :)) using Ognl, which is a lot quicker and more robust then what ww 1.x uses.

The new xwork (which webwork is built on) has an awesome validation framework built into it now, not too mention the ability to define and use you own interceptors.

The Tag library used Velocity to render its html elements, so it doesn't suffer from the JSP taglib performance hit.

It's been promoted out of the sandbox. An XDoclet module will be in the works soon. After its released, I think... Later!

Posted by Rick Salsa on March 30, 2003 at 01:53 PM MST #

In regard to Velocity and JSP, I agree Velocity is clean, and I used to think I should just forget about JSP and go with it. But, with JSTL (and soon JSP 2.0), JSP is actually not that bad. There are other issues, but one thing not to ignore is the wealth of information and knowledge that JSP has. Basically, I'd say that the JSP vs. Velocity battle is similar to Struts vs. WebWork, and/or Tiles vs. SiteMesh. They'are all good stuff. But, it depends on various issues. Patrick had some good writeups on this. For example, don't ignore available documentation and likelyhood of other engineers you may need to work with knowing it, or how fast they can get up to speed on it (which is a circular reference to documentation ;)

Posted by crb on March 30, 2003 at 09:48 PM MST #

44444444444

Posted by 219.94.111.118 on June 30, 2006 at 12:36 AM MDT #

Funny that I cannot find a single WebWork tutorial on the web which makes use of a database connection (even if as an example). Not even in the book Manning WebWork in Action, there was none, either. Can anyone point to any direction for a Webwork / jdbc primer ?

Posted by Gökhan on October 05, 2010 at 08:28 AM MDT #

Funny that I cannot find a single WebWork tutorial on the web which makes use of a database connection (even if as an example). Not even in the book Manning WebWork in Action, there was none, either. Can anyone point to any direction for a Webwork / jdbc primer ?

Posted by Gozzie on October 05, 2010 at 08:28 AM MDT #

Funny that I cannot find a single WebWork tutorial on the web which makes use of a database connection (even if as an example). Not even in the book Manning WebWork in Action, there was none, either. Can anyone point to any direction for a Webwork / jdbc primer ?

Posted by Gozzie on October 05, 2010 at 08:37 AM MDT #

Post a Comment:
  • HTML Syntax: Allowed