Willem,
Not objecting to this, but wondering why it's necessary? Such conduits
really should be configured based on URL, not some strange internal name or
similar. Seriously, a conduit thing like:
http:conduit name=http.* ...
would likely accomplish the exact same thing.
Dan
On
Hi All,
The requirements is to post the the form data along with the image/flash
file upload via AJAX sumbit.
In the server side we used @Consume(multipart/form-data) and the API
argument is org.apache.cxf.jaxrs.ext.multipart.MultipartBody
When we do a AJAX submit along with file upload
Hi Dan,
I did some test by using the http:conduit name=*.http-conduit.
It doesn't work and the created HttpConduit 's getBeanName return null.
I didn't see the http:conduit name=http.* can do the trick.
On Fri Mar 23 19:38:09 2012, Daniel Kulp wrote:
Willem,
Not objecting to this, but
Hi,
I attached a unit test for this problem to your jira ticket.
I thought a quick solution is to copy all the namespace bindings from
the reader object to the root dom element but the public API does not
have an iterator to access all the bindings. So, that didn't work.
Someone might have a
Hi
On 23/03/12 14:07, Ganesh wrote:
Hi All,
The requirements is to post the the form data along with the image/flash
file upload via AJAX sumbit.
In the server side we used @Consume(multipart/form-data) and the API
argument is org.apache.cxf.jaxrs.ext.multipart.MultipartBody
When we do a AJAX
Hi,
Thanks Aki for the test :), the issue really needed it.I can change the
SAAJInInterceptor so that it does not set the XMLStreamReader.class
SoapMessage's content for only the fault. But if there are more classes that
are programmed to use the XMLStreamReader for the fault, I think it is
Just committed a fix for this to trunk using Aki's unit test. Can you and
Aki take a quick look?
Basically, the SOAP Envelope/Body is stored on the message as a DOM node.
Thus, when we parse the fault to the DOM, we can actually parse it right
into the correct place in the original DOM.
Finally, I got a chance to follow up. Thanks Freeman for creating a
Jira and addressing the issue.
On 01/16/2012 01:08 AM, Freeman Fang wrote:
Hi William,
Sorry for the late response, last week I was on travel so can't catch
email in time.
Your suggestion looks good for me, could you
Hi Aki,I added something else to the test. The unmarshalFault methods is used
by the SAAJInInterceptor also, and it is there when the class receives the
XMLStreamReader.class content for the fault only since the SAAJInInterceptor
prepares it like that for this method.
I added this:
