I'll try the new nightly build soon for the first problem. I'm using
ADB, since that's the default--I don't have a preference at this
point.
Here's the XSD section of the WSDL for the operation I'm calling
(downloadAttachment). The rest of the WSDL isn't very
intereting--standard doc-literal
Sure. Please let us know. If you need another wsdl to compare, please
take at the xmime wsdl here:
http://www.wso2.net/articles/axis2/java/2006/08/10/binary-with-adb
On 9/7/06, Jay Gillibrand [EMAIL PROTECTED] wrote:
I'll try the new nightly build soon for the first problem. I'm using
ADB,
I'm calling an XFire based web service that is using MTOM to return
attachments. Tracing the actual HTTP request I can see the response
looks like what I'd expect, but Axis2 fails to parse the results.
The problem _seems_ to be that my Axis2 client stubs are expecting the
attachments to be
Please use a nightly build of Axis2.
Options options = myStub._getServiceClient().getOptions();
options.setProperty(org.apache.axis2.Constants.Configuration.ENABLE_MTOM,
Boolean.TRUE);
-- dims
On 9/6/06, Jay Gillibrand [EMAIL PROTECTED] wrote:
I'm calling an XFire based web service that
I tried the nightly and had two problems. First, one of the methods in
the stub wouldn't even compile since it was filled with mismatched ifs
and elses. Since it wasn't related to the download method I'm calling,
I just commented it out for now.
Second, the stub for the download method still
Hi Jay,
The web site says clients automatically handle MTOM
attachments...
Yes.. It's true.. Client identifies and creates a OMText object in the
place of XOP:Include element... Configuration Dims has mentioned is
usefull when sending MTOM attachements.
What's the data binding framework you
