You are viewing a plain text version of this content. The canonical link for it is here.
Posted to axis-cvs@ws.apache.org by sa...@apache.org on 2006/05/04 07:54:43 UTC

svn commit: r399562 - /webservices/axis2/trunk/java/xdocs/1_0/mtom-guide.html

Author: saminda
Date: Wed May  3 22:54:41 2006
New Revision: 399562

URL: http://svn.apache.org/viewcvs?rev=399562&view=rev
Log:
minor changes to the xdocs

Modified:
    webservices/axis2/trunk/java/xdocs/1_0/mtom-guide.html

Modified: webservices/axis2/trunk/java/xdocs/1_0/mtom-guide.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/1_0/mtom-guide.html?rev=399562&r1=399561&r2=399562&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/1_0/mtom-guide.html (original)
+++ webservices/axis2/trunk/java/xdocs/1_0/mtom-guide.html Wed May  3 22:54:41 2006
@@ -337,8 +337,8 @@
 parts in the Message Context. Users can access binary attachments using the
 content-id. Care should be taken to rip off the "cid" prefix when content-id
 is taken from the "Href" attributes. When accessing the message context from
-a service users need to use the message context injection mechanism by
-introducing an "init" method to the service class.(see the following service
+a service users need to get hold of the message context from "setOperationContext()"
+method from the service class.(see the following service
 example)</p>
 
 <p>Note: Axis2 supports content-id referencing only. Axis2 does not support