Thilina,
Could this also be an issue because I am using the ADB data binding?
Is there any other data binding I need to use for MTOM?
Thanks!
IMO xs:anyType should work at this point... Please file a bug report for
that...
While above is also correct, you can define the return element by
Please use MTOMDataBinding with base64Binary type... See here [1]
~Thilina
[1] http://people.apache.org/~thilina/axis2/docs/mtom-guide.html#25
On 10/9/06, Sathija Pavuluri [EMAIL PROTECTED] wrote:
Thilina,
Could this also be an issue because I am using the ADB data binding?
Is there any other
have a look at this too..
http://www.wso2.net/articles/axis2/java/2006/08/10/binary-with-adb
Thilina
On 10/10/06, Thilina Gunarathne [EMAIL PROTECTED] wrote:
Please use MTOMDataBinding with base64Binary type... See here [1]
~Thilina
[1]
Hi Thilina,
Here is the tcpmon response:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=32D3D08F1EA838446315878FA3E1975E; Path=/enetaware
Content-Type: multipart/related;
boundary=MIMEBoundaryurn_uuid_5AA4462B26C922F16A1160142103004103;
type=application/xop+xml;
)
binaryNode.getDataHandler();
This will return a DataHandler for the MTOM binary node.
Roshan Punnoose
Phone: 301-497-6039
-Original Message-
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
Sent: Friday, October 06, 2006 12:52 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Retrieving an MTOM
System.out.println(\n);
omNode.serialize(System.out);
Please let me know the output you get at this point...
OMElement omNode2 = (OMElement) omChildren.next();
if the deserialization is happening correctly you should get a
Hi,
My replies are inline.
System.out.println(\n);
omNode.serialize(System.out);
Please let me know the output you get at this point...
imagexop:Include xmlns:xop=http://www.w3.org/2004/08/xop/include;
href=cid:1.urn:uuid:[EMAIL PROTECTED]
//image
IMO xs:anyType should work at this point... Please file a bug report for that...
While above is also correct, you can define the return element by
using the following complex type and it's the better way..
xs:complexType
xs:sequence
xs:element name=image type=xs:base64Binary /
/xs:sequence
Hi,
But when I traverse the reportElement there is only one child element
i.e the xop:Include element. I can never get to the attachment itself.
This can't be... Axis2 should automatically detect XOP:include and
should create an OMText instead of XOP:Include...
If possible please post your
