DWR version 1.0 released


News: DWR version 1.0 released

  1. DWR version 1.0 released (14 messages)

    DWR 1.0 has been released and is available for download. DWR makes it easy to do Ajax in Java. DWR provides remoting of Javascript calls into Java, automatic generation of Javascript stubs from Java, easy test pages, security for remoted calls, automatic conversions of types, some Spring integration, and more.

    The feature list for 1.0 looks like this:
    • AJAX remoting of JavaScript calls to Java
    • Automatic generation of JavaScript stubs to match Java code.
    • Test pages allowing you to test and debug your server code.
    • Access controls through:
      • J2EE security including role based authorization
      • Declarative access rights at a method and parameter level
    • Automatic conversion of the following types:
      • All primitive types, String, Date (including SQL variants)
      • Arrays, Collections, Maps, Iterators
      • Document, Element etc from DOM, DOM4J, JDOM, and XOM
      • JavaBeans (nested and recursive trees supported) including beans from Hibernate
    • A large array of remoting options:
      • Batch sending of remote calls
      • Support for XMLHttpRequest & iframe with POST & GET
      • Optional call ordering guarantees
    • JavaScript library for HTML manipulation including:
      • Tables, ul, ol and select lists
      • Form fields including automatic form / JavaBean mapping
      • All general content types like p, h*, div, span, etc.
    • Spring integration:
      • Remote Spring beans
      • Configure DWR using Spring config files
    • Open Source (ASL Version 2)
    We're working on a number of things for the next version including conversion of any Java object (not just beans), tighter integration with Spring (with Bram Smeets, from Interface21), and a number of enhancements to the Javascript library that helps you build pages with remoted data.

    What features would you like to see in the next version?

    Threaded Messages (14)

  2. Experiences..[ Go to top ]

    Does anybody have any experiences they would like to share about this or other similar AJAX libraries/toolkits? Pros and Cons, or other feedback?

  3. Experiences..[ Go to top ]

    I'm using it on a project now. I have to say I like it a lot for what it is, although I haven't used much of it yet. It's easy to use, works as advertised, and doesn't add a lot of overhead to page load. That's the good...

    The bad, well... I'm not sure how fair it is to criticize it when it could just be Pilot Error. The thing I'm struggling with at the moment is that it's up to me to interpret the content of my messages. Presumably I can fix that by sending Java Beans back and forth, but I haven't figure that out yet, since I'm a little reluctant to add yet another DTO to my architecture. Still, it'd be better than the hack I have at the moment.

    There's another library I've seen (blanking on the name at the moment) which actually sends XML for you back and forth and then interprets that, but it's not clear to me how I'd wire that up to my DOM objects. The whole thing is a bit murky for me still, but that's why I'm doing a project with it after all, so no big surprise there. :)

  4. Experiences..[ Go to top ]

    I've been using it for a while for developing http://tudu.sf.net.

    It works very well, and it's rather easy to use.

    I've created a special "DWR" layer on top of my business layer, so that I only show the methods and objects I want.

    You can have a look at my beans here.
    Basically it's just Spring beans which are presented in JavaScript.


    Julien Dubois.
  5. DWR usage[ Go to top ]

    I am using it in my current project - works well
    there are some quirks when using complex spring
    objects that I need to figure (probably operator error)

    overall, would recommend it highly..

    Arun Rao
  6. Experiences..[ Go to top ]

    U may want to check the following trail of emails.
    It may answers to some of your questions

    I have being using DWR since 0.6 with success.
    If u're looking for a package allowing u to export your java/Spring beans methods to client side javascript methods(asynchronous call with callback,timeout,...)
    DWR is the way to go....There is no code required on the server side just configuration for filtering/declaring the method that u want to export.In addition,there is already a nice integration with Spring.

    Take a look DWR applied to demo Portal page.
  7. Experiences..[ Go to top ]

    I have also been using it for a while. Its been a great utility in our project and has suited our needs for google-type lookup boxes.

    We keep our methods as simple as possible to avoid (any potential) problems and has worked like a charm.

    We are also using it within the spring framework no problem. Although when we had to integrate it with spring it was before it came with this integration so we had to write our own factory class for it. Wasn't too hard though.
  8. Re: Experiences..[ Go to top ]

    DWR is a very nice framework and I am using it in several of my client's applications. So far I have only used it for "back office" applications so there is nothing I can point to publicly.

    I was so impressed with DWR that I wrote an article about it over on BEA's dev2dev: http://dev2dev.bea.com/pub/a/2005/08/ajax_introduction.html

  9. DWR version 1.0 released[ Go to top ]

    Could anyone show me how can I write an automated acceptance (blackbox) test for DWR-enabled app?

    I've just tried it with HttpUnit and actiWATE and both fail miserably on document.createElement(), because it seems like JS support in those frameworks isn't (yet?) that sophisticated.
  10. Rich UI[ Go to top ]

    What about support for advanced UI features like Drag/Drop, Sorting etc which some of the commercial AJAX implementaions provide.
  11. Rich UI[ Go to top ]

    You may want to look here as well. Great UI toolkit


  12. Security?[ Go to top ]

    Any experience on security?

    What did you guys use for security? Acegi or others?

    I would like to know current popular approaches.
  13. Re: Security?[ Go to top ]

    DWR is simply "Yet another way" of calling your web application's service layer; the only real distinction is you can call your app service programmatically using JavaScript instead of relying on the user to click a link. At the end of the day, it boils down to a HTTP request to your web application, and as such, you can use the standard servlet security model.

    In addition to that, you can configure DWR to only expose certain fields of your objects, since you may not have a need to call .toString() or setApplicationDao(null) on your service object in JavaScript :)

    See http://dev2dev.bea.com/pub/a/2005/08/ajax_introduction.html for details.
  14. Re: Rich UI[ Go to top ]

    DWR is orthogonal to rich UI's. The point of DWR is to allow you to call your application logic from JavaScript and not worry about serialization of your beans to JS and back.

    Use something like http://script.aculo.us/ and then call your service programatically.

  15. Reverse ajax[ Go to top ]

    Hi to All,

    i want to use java script call by dwr without request by browser.

    i want to call java script funcation from .java file without any request from clinet or browser.

    is this possible by dwr ???

    if yes then plz give me good example for the same.