Yes, there are MIME boundaries but the message looks something like this:
--MIMEBoundaryurn_uuid_72EC4B349174A8C3141174305830430
content-type: application/xop+xml; charset=UTF-8; type="text/xml";
content-transfer-encoding: binary
content-id: <0.urn:uuid:[EMAIL PROTECTED]>
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header
/><soapenv:Body>
<Testing xmlns:tns="http://queryposer.regenstrief.org"><returnStatistics
xmlns:r="http://spin.regenstrief.org/query"><breakdownVariable
name="cmore patient gender" ordinal="1"><variableComponent r:id="A"
r:name="Gender (value)">value</variableComponent><condition name="cmore
patient gender"><all><variable code="21840-4" name="cmore patient
gender" r:displayName="cmore patient gender (21840-4)"
r:objectType="REGISTRATION" r:valueType="CE" system="LN"
/></all></condition><breakdown max="25"><cutpoint name="Missing value"
ordinal="1" /><cutpoint name="female (F)" ordinal="2"><ccode code="F"
name="female" r:displayName="female (F)" system="SEX"
/></cutpoint><cutpoint name="male (M)" ordinal="3"><ccode code="M"
name="male" r:displayName="male (M)" system="SEX" /></cutpoint><cutpoint
name="transgender (T)" ordinal="4"><ccode code="T" name="transgender"
r:displayName="transgender (T)" system="SEX" /></cutpoint><cutpoint
name="unknown (U)" ordinal="5"><ccode code="U" name="unknown"
r:displayName="unknown (U)" system="SEX"
/></cutpoint></breakdown></breakdownVariable><cells><count>548</count><r:count_discarded>0</r:count_discarded><cell><count>1</count><breakdownVariable
cutpoint="2" ordinal="1"
/></cell><cell><count>543</count><breakdownVariable cutpoint="3"
ordinal="1" /></cell><cell><count>4</count><breakdownVariable
cutpoint="5" ordinal="1" /></cell></cells></returnStatistics>
<pdf>JVBERi0xLjMKJcfsj6IKNiAwIG9iago8PC9MZW5ndGggNyAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nL1U61dTRxA3QiNcepQitKVCXa1atGaz7we0jYIioFRyvRbFW
1oKQYEklgBFKvbhs/avdnY3N8Zy+qFfPDnJZl6/nZnfzG4igiki7tM8l2vRZlSMBbq/FW0i6k3ZsVxD40lUvIwoSlajLKLg/lBp4Vcrji1KatHIocO5zo4Pckfy3V1pPdeT7/4wbXQcO/pR</pdf>
</Testing></soapenv:Body></soapenv:Envelope>
--MIMEBoundaryurn_uuid_72EC4B349174A8C3141174305830430--
The mime boundaries are in there but the binary data is being base64
encoded and stored in the actually body of the xml instead of an include
tag inside the xml pointing to the binary data stored outside.
Tammy
Punnoose, Roshan wrote:
Are the MIME boundaries present? That is one way of telling whether or not MTOM
is being used.
Something like:
--MIME...---
all the data
----MIME...---
If not, then MTOM is not being used. Then you can up the root logger to DEBUG and see what it actually is, and where the axis conf is coming from. (I believe)
Roshan
________________________________
From: Tammy Dugan [mailto:[EMAIL PROTECTED]
Sent: Fri 3/16/2007 1:26 PM
To: axis-user@ws.apache.org
Subject: [Axi2] Can't get MTOM attachments by reference to work
I use the following code to add attachments to an outgoing soap message:
//add an attachment if needed
if (this.attachmentContent != null)
{
for (int i = 0; i < this.attachmentContent.length; i++)
{
DataSource ds = new
ByteArrayDataSource(this.attachmentContent[i].toByteArray(),
this.attachmentContentType[i]);
OMText data = fac.createOMText(new DataHandler(ds), true);
OMElement parent = fac.createOMElement("pdf",null);
parent.addChild(data);
resp.addChild(parent); ;
}
}
I have the following test client that sends and receives a message from
a URLConnection:
charCnt = 0;
in = new BufferedReader( new InputStreamReader(
conn.getInputStream() ) );
out = new BufferedWriter( new FileWriter( OUTPUT_FILE ) );
while ( (response = in.readLine()) != null)
{
out.write( response );
out.write( "\n" );
charCnt += response.length();
}
in.close();
out.flush();
out.close();
When I look at the response output, the attachments in base64 encoded in
the body of the xml. I have <parameter name="enableMTOM"
locked="false">true</parameter> in axis2.xml and am not overriding it in
the services.xml file so why isn't the attachment being sent by
reference? Here is my services.xml file entry for the service I am testing:
<service name="QueryStatisticsReturn" scope="soapsession">
<parameter
name="ServiceClass">org.regenstrief.queryposer.QueryStatisticsReturnServlet</parameter>
<operation name="queryStatisticsReturn">
<messageReceiver
class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
</operation>
</service>
Thanks,
Tammy Dugan
--
Tammy Dugan
Computer Programmer
Regenstrief Institute, Inc.
1050 Wishard Blvd., RG5
Indianapolis, IN 46202
(317) 630 - 7346
Confidentiality Notice: The contents of this message and any files transmitted
with it may contain confidential and/or privileged information and are intended
solely for the use of the named addressee(s). Additionally, the information
contained herein may have been disclosed to you from medical records with
confidentiality protected by federal and state laws. Federal regulations and
State laws prohibit you from making further disclosure of such information
without the specific written consent of the person to whom the information
pertains or as otherwise permitted by such regulations. A general authorization
for the release of medical or other information is not sufficient for this
purpose.
If you have received this message in error, please notify the sender by return
e-mail and delete the original message. Any retention, disclosure, copying,
distribution or use of this information by anyone other than the intended
recipient is strictly prohibited.
---------------------------------------------------------------------
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]
--
Tammy Dugan
Computer Programmer
Regenstrief Institute, Inc.
1050 Wishard Blvd., RG5
Indianapolis, IN 46202
(317) 630 - 7346
Confidentiality Notice: The contents of this message and any files transmitted
with it may contain confidential and/or privileged information and are intended
solely for the use of the named addressee(s). Additionally, the information
contained herein may have been disclosed to you from medical records with
confidentiality protected by federal and state laws. Federal regulations and
State laws prohibit you from making further disclosure of such information
without the specific written consent of the person to whom the information
pertains or as otherwise permitted by such regulations. A general authorization
for the release of medical or other information is not sufficient for this
purpose.
If you have received this message in error, please notify the sender by return
e-mail and delete the original message. Any retention, disclosure, copying,
distribution or use of this information by anyone other than the intended
recipient is strictly prohibited.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]