advertisement

Weblog:   AJAX and Java: Toolbox
Subject:   DWR invasive??
Date:   2005-11-29 10:13:52
From:   debradley
How are you defining invasive? I can add a jar and a little bit of config to my app and suddenly I have full access to the service-level classes that already exist in my class? I was thrilled to find out how easily I could add those capabilities without changing any existing code. To me that's the opposite of invasive.
Full Threads Oldest First

Showing messages 1 through 4 of 4.

  • DWR invasive??
    2005-11-29 10:14:32  debradley [Reply | View]

    "service-level classes that already exist in my class" should (maybe) obviously be "service-level classes that already exist in my app"
    • Robert Cooper photo DWR invasive??
      2005-11-29 10:20:25  Robert Cooper | O'Reilly Blogger [Reply | View]

      Sorry, perhaps I was a little unclear there.

      It is definitely not invasive w/r/t your service beans. However, working with your services directly from the client implies (at more than one level) that you are actually building a whole fat-client-style functionality into the HTML/JavaScript. As opposed to AJAXTags or Taconite where even your presentation layer can remain mosty unchanged from a vanilla HTML/Struts app.

      DWR is might cool, but if you are attempting to retrofit an application with AJAX functionality, extensive used of DWR does require a rethinking of your presentation layer.
      • Robert Cooper photo DWR invasive??
        2005-11-29 10:21:17  Robert Cooper | O'Reilly Blogger [Reply | View]

        /used of/use of/g
        • DWR invasive??
          2005-11-30 10:19:34  debradley [Reply | View]

          O/T, but wouldn't it be nice if you could edit your comments here?
Showing messages 1 through 4 of 4.