Slashdot Mirror

← Back to Stories (view on slashdot.org)

DWR Makes Interportlet Messaging With AJAX Easy

Posted by ryuzaki0 on from the hiding-it-all-away dept.

An anonymous reader writes "You can use the sample code in this article as a starting point for developing your own applications; the code also shows how DWR extends the Java programming model to Web browsers. With DWR, it's almost as if JavaBeans were available in the browser. DWR simplifies your work by hiding almost all the details of Ajax and allows you to concentrate on the task at hand instead of the nuts and bolts of Ajax development."

3 of 39 comments (clear)

  1. Nuts and bolts? by The+MAZZTer · · Score: 3, Insightful

    "'...allows you to concentrate on the task at hand instead of the nuts and bolts of Ajax development.'"

    Last time I checked the "nuts and bolts" of AJAX was only a few dozen lines of code... all it is is sending a server request in the background.

  2. Re:What the hell? by Reverend528 · · Score: 2, Insightful

    Clearly you've never read the JSR-168 spec or you'd know that portlets are little web applications that adhere to standards so crippling that the easiest way to communicate between two portlets on the same server is to utilize the clients' web browser in a convoluted AJAX hack.

    --
    Badass Resumes
  3. Problems by brunes69 · · Score: 2, Insightful

    This DMR *seems* cool at first, but the fact that I have to inline the Javascript code insid ethe JSP with this stupid cusotm tag kills it for me. JSP's are supposed to be the presentation layer *only* - if you have JS code it should be in external .js files as much as humanly possible. THis also helps download times a lot since the .js files can be cached.

    Personally I think that JSON-RPC is far superior to this "DMR" stuff. It's also been around much longer, so it's tried and tested. It also has non-Java backend implementations.