cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Zoerner <>
Subject Re: Server output as a result of the CustomInvoker and Client output after parameterization refactoring of Client, CustomerService, and Order
Date Fri, 13 May 2011 12:37:20 GMT
Here are the links to the and files that I
have in my development environment.

Also, here are the output files from the client and the server.

You can see from the header that the 400 status code happens fine.

I think that the xml error might be as a result of cxf catching the
exception, but I think that Jetty may be throwing up the xml parsing error,
on its own, for some reason.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message