Getting DWR to work on Tomcat 6.0
I’ve been trying to get the simple “ajax validation” with Direct Web Remoting (DWR) example working from the Struts 2 site.
I kept getting a severe error on startup. I finally waded through a number of theories and I think it was basically just versionitis. The jsf-impl-1.2_04.jar, jsf-api-1.2_04, and jstl-1.2.jar seem to do the trick. They are available at this maven repository: https://maven-repository.dev.java.net/nonav/repository/
In the end, I’m using little bits of an unnervingly large number of java web frameworks. I definitely see why the java approach has put off a lot of web developers. I really like the java language, but if this is the side of it that people see, I understand why they flock to php, perl, python, and ruby.
Posted by Adam Pingel @ April 27th, 2007 under Software Engineering.
Comments: 3
Comments
Comment from Joe Walker
Time: May 1, 2007, 7:01 am
To be fair on DWR, this isn’t DWR’s fault. All versions of DWR up to 2.0 have no mandatory dependencies on other libraries what-so-ever. So I’d be surprised if the errors came from DWR.
Comment from Adam
Time: May 1, 2007, 7:59 am
Hi, Joe! Thanks for the comment. (I’m still a little shocked that any of these posts are actually being read!)
No, this problem wasn’t DWR’s fault — I don’t want to suggest that.
My problems were mostly with some of the related Struts 2 documentation. Primarily incomplete details. To DWR’s credit: it’s functionality is compelling enough to work through these problems.
Comment from Adam
Time: May 1, 2007, 8:28 am
To add to that: As far as I can tell, DWR’s approach is right on.
It does such a good job of mapping the two languages, in fact, that it highlights the need for development environments to understand that link — and to be able to refactor all the way from the backend database column names to the javascript DWR references in the case of a simple “variable/column/field name change” refactoring, for instance.
I hope to make this clear in subsequent posts soon.
Write a comment