That's true. I obviously wasn't awake. On Tue, Feb 26, 2013 at 9:15 AM, Stephen Connolly <[email protected]> wrote: > This is not a Maven problem... > > > On 26 February 2013 14:08, Benson Margulies <[email protected]> wrote: > >> So, I've absently-constructed the following problem. >> >> I've got a JAX-RS service that does, essentially, all of its work in a >> StreamingOutput object. It also has an error mapper that produces a >> Json body to go with the 400 status code in the error response. >> >> You can see where this goes: the code succeeds in writing *some* of >> the output, encounters an exception, and then sets up the error >> response. CXF dutifully serializes it, resulting in a mess consisting >> of the beginning of the original output followed by the error output. >> >> Is this a CXF problem? Does the standard offer any guidance? >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >>
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
