@ResponseBody not producing XML in Java 6

Question

I have a Spring MVC 3/J2EE Project. The jsp rendering controllers are working fine, but the one controller that renders XML for Ajax is not working. I am using JDK 1.6 in RAD 7.5 so JAXB should be on the classpath, and I've even tried adding the latest JAXB jars to the lib file to make sure. I still get a 406 error when I make the call. My DOJO call has handleAs: "xml", and I've confirmed that application/xml is on the Accept header via FireBug. I have the <mvc:annotation-driven /> line in my spring servlet xml file. I can see the method being invoked and returning without error. I'm not sure what I should try next to debug.

//Country is a class with only primative types which implements Serializable.
public @ResponseBody List<Country> getCountries(){
    return addressService.getCountries();
}

function loadData(){
    console.log("Before get ...");
    dojo.xhrGet({
        url:"http://localhost:9080/sample/shared/getCountries.htm",
        handleAs:"xml",
        load: function(data){
            console.log("In load function ...");
            try {
                for(var i in data){
                   console.log("key", i, "value", data[i]);
                }
            }catch (ex){
                console.error("Failure in load function: " + ex);
            }
            console.log("Exiting load function ...");
        },
        error: function(x){
            console.error("Error in ajax ...");
            console.error(x);
        },
        failOk: false
    });
    console.log("After get ...");
}

score 4 · Accepted Answer · edited May 23 '17 at 11:47

4

Try creating the following wrapper class:

@XmlRootElement
class Countries {
    private List<Country> countries = new ArrayList<Country>()

    //getters/setters
}

And return it from the controller instead of a raw list:

public @ResponseBody Countries getCountries()

Most likely your problem is caused by JAXB that is unable to marshal Java list (it does not know how to name the root tag of the XML document). Note that your problem probably does not occur when requesting data in JSON (if Jackson is available on your CLASSPATH).

See also (similar problems):

edited May 23 '17 at 11:47

Community

1
1

answered Oct 24 '11 at 21:15

Tomasz Nurkiewicz

334,321
69
703
674

I would be surprised if this would cause the `406`, however, I agree that a wrapper is needed. – SingleShot Oct 24 '11 at 21:17
Yeah, I saw this this in another answer. Trying it today. – C. Ross Oct 25 '11 at 10:17

score 1 · Answer 2 · answered Oct 24 '11 at 20:50

1

Hard to say without seeing how you have configured your views / view resolvers. However, the client-side URL containing a .htm is suspect to me, especially if you are using a ContentNegotiatingViewResolver. I recommend dropping the file extension. Browsers automatically use an Accept header for HTML so no need to use an extension.

answered Oct 24 '11 at 20:50

SingleShot

18,821
13
71
101

Obviously the view resolver is working correctly since "I can see the method being invoked and returning without error." – C. Ross Oct 24 '11 at 20:52
Sorry, wasn't quite fast enough for you :-). – C. Ross Oct 24 '11 at 20:53
The "method returning" occurs before view resolution and thus is not an indicator of the server side being configured correctly. – SingleShot Oct 24 '11 at 20:54
`@ResponseBody` skips view resolution altogether. – C. Ross Oct 25 '11 at 10:18
No it doesn't. Try it. It exists for special circumstances, like returning a String that you want to go into the body instead of being interpreted as a view name. The framework will still pick a view to render (i.e. view resolution) based on configured views/resolvers. – SingleShot Oct 25 '11 at 12:04

@ResponseBody not producing XML in Java 6

2 Answers2

Linked