Really appreciate the comment. Wordpress is a bear with respect to getting code into posts. I am still using the generic hosted wordpress and as far as I can tell am not allowed to install the plugins that make it easier.

I’ve been using some Javascript converter that wraps the stuff in a code tag and then converts symbols to their html entity equivalents. It is less than ideal. I need to just setup a box a home and host wordpress myself.

With that said, I apologize for not mentioning the @DataTransferObject in my post. That is a pretty important part of getting it to work. On our particular project after a handful of custom converters and enum converters in dwr.xml we had a lazy (and potentially dangerous) line that looked like this:

<convert converter="bean" match="com.ourproject.*"/>

We had probably 100 different classes that would have needed @DataTransferObject annotations and I just wasn’t up to the task. So we are running DWR in a bit of a hybrid mode - the exposed controllers are configured through annotations and the objects we send over the wire are configured in dwr.xml through that messy wildcard converter line.

Thanks again for the comment,

Joe

It took a while to get things working, though. Here are some issues that wasn’t obvious at first. Here is my story:

1. web.xml, as pertaining to dwr, now looks like this:

dwr

org.springframework.web.servlet.DispatcherServlet

2

dwr
/dwr/*

2. When having a @RemoteMethod that takes class instance Foo and returns Foo, not only should class Foo be annotated with @DataTransferObject (import org.directwebremoting.annotations.DataTransferObject;). Foo must also be appended to the “classes” property (see DwrServlet’s initParameters above). So basically, ALL classes having dwr annotations MUST be in the “classes” parameter.

3. To enable debug pages to be reachable from http://whatever.com/dwr, another property must be appended to DwrServlet’s initParameters:
true

It took a while to get things working, though. Here are some issues that wasn’t obvious at first. Here is my story:

1. web.xml, as pertaining to dwr, now looks like this:

2. When having a @RemoteMethod that takes class instance Foo and returns Foo, not only should class Foo be annotated with @DataTransferObject (import org.directwebremoting.annotations.DataTransferObject;). Foo must also be appended to the “classes” property (see DwrServlet’s initParameters above). So basically, ALL classes having dwr annotations MUST be in the “classes” parameter.

3. To enable debug pages to be reachable from http://whatever.com/dwr, another property must be appended to DwrServlet’s initParameters:


true


It looks roughly like this is our application, I will try to make a legitimate post in the future with more details. We started out with version 1.0 of DWR and I believe there may be easier ways to do this initialization now and this excludes some custom properties and subclasses we use and thus may not work without tweaking:


<bean id="dwrController" class="org.springframework.web.servlet.mvc.ServletWrappingController">
    <property name="servletClass" value="org.directwebremoting.servlet.DwrServlet"/>
    <property name="initParameters">
        <props>
            <prop key="classes">
                com.sample.Class1,
                com.sample.Class2,
                ...
            </prop>
        </props>
    </property>
</bean>


The comma-delimited classes parameter is where you list classes annotated for DWR configuration. If you are using dwr.xml for configuration this won’t be necessary.

Bram Smeets has many very helpful posts about Spring and DWR. Here is his blog. The DWR mailing is also very responsive and helpful - I’d give that a shot if you get stuck.