I can't tell you until tomorrow. Comcast can't route to issues.apache.org tonight, and I just disconnected from the complex alternative path I was using just now.
> -----Original Message----- > From: Jim Ma [mailto:[EMAIL PROTECTED] > Sent: Sunday, November 25, 2007 9:27 PM > To: [email protected] > Subject: Re: Diagnosis of stupid JAXB/JAXWS errors > > Hi Benson , > > Is this issue same as https://issues.apache.org/jira/browse/CXF-1226? > > Regards > > Jim > > Benson Margulies wrote: > > Consider the following pile of snails. Now, I realize, I don't need > > them in CXF, but I had coded them to test something. > Except, that, I'd > > neglected to code the @WebResult at all, so while I had a wrapper, > > there was no way for the code to know the element to use > for the response. > > > > It didn't work, of course. It also didn't diagnose in the > log. Should > > this sort of thing produce some whining? > > > > @RequestWrapper(className = > > > "org.apache.cxf.javascript.fortest.BasicTypeFunctionReturnStri > ngWrapper" > > ) > > @ResponseWrapper(className = > > "org.apache.cxf.javascript.fortest.StringWrapper") > > @WebResult(name = "returnValue", targetNamespace = > > "uri:org.apache.cxf.javascript.testns") > > > > >
