Sreedhar, MTOM and SwA are two diffrent things. Both deal with attachments but in different manner. Actually when talking about attachments you'll encounter SwA, SwARef and MTOM/XOP. SwA has interop issues which SwARef did solve and MTOM relieves the interposed SOAP processors from having to deal with resource consumption while processing messages in transit. However, looking at your detailed report (thanks, that simplifies things a lot) i can see two things: anonymous wrote : | org.jboss.ws.binding.BindingException: Mime type text/xml not allowed for parameter mimepart allowed types are [application/xml] | anonymous wrote : | URL temp = new File("resources/jaxrpc/samples/swa/attach.xml").toURL(); | See first one states that the endpoint does only accept attachment of the type "application/octet-stream". Looking at your samples code in the second quote, you create a URL to a *.xml file. The JAF API will create a DataHandler instance with the content-type 'text/xml' from that, which then would be submitted. If you change the client to use the right content-type everything works fine. Please consult the JAF API for further information on this topic. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051323#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...