Yep. DIME is fully deprecated by Microsoft now. (It's even hard getting a good low level description of how it works). It was Microsoft's answer to SWA (SOAP With Attachments). Both technologies are obsolete now, and the world has (for better or for worse) chosen MTOM. -jeff
-----Original Message----- From: Pantvaidya, Vishwajit [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 24, 2007 3:24 PM To: axis-user@ws.apache.org Subject: RE: Exchange word/pdf docs using axis java service to support .NE T cl ient I configured my WSDL for DIME on the axis side and stubs got generated fine. But on the .NET client side, WSE2.0 supports DIME but WSE3.0 supports only MTOM - so we need WSE2.0. But WSE2.0 needs Visual Studio .NET 2003 while we have Visual Studio 2005 - and it seems difficult to move backto the older version. So currently looks like the only option we have it to migrate the server to Axis2 and MTOM. - Vish. >-----Original Message----- >From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] >Sent: Thursday, July 19, 2007 5:51 AM >To: axis-user@ws.apache.org >Subject: Re: Exchange word/pdf docs using axis java service to support .NE >T cl ient > >Microsoft implements support for attachments in the Web Services >Extensions (WSE) framework, which extends ASMX, and in WCF. WSE >supports WS-Attachments using DIME. WCF supports MTOM. Neither >supports SOAP with Attachments (SwA) using MIME. > >Axis supports both WS-Attachments and SwA. No extension is required. >Axis2 supports MTOM. > >Anne > >On 7/18/07, Pantvaidya, Vishwajit <[EMAIL PROTECTED]> wrote: >> I am going ahead and trying - will let everybody know my experience. >> >> Meanwhile 2 quick questions: >> 1. MIME seems to be an old standard - does .NET version 2 support it? In >> that case, I may not need to use DIME. >> 2. Axis1 FAQ says it supports DIME attachments. Does it by itself >> support it or I need to use MSFT WSE with it for that? >> >> >> Thanks, >> >> Vish. >> >> >> >-----Original Message----- >> >From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] >> >Sent: Wednesday, July 18, 2007 1:10 PM >> >To: axis-user@ws.apache.org >> >Subject: Re: Exchange word/pdf docs using axis java service to support >> .NE >> >T cl ient >> > >> >Try it and see. >> > >> >On 7/18/07, Pantvaidya, Vishwajit <[EMAIL PROTECTED]> wrote: >> >> Thanks a lot Anne. I had read that doc - but I see now that I had >> >> inadvertently skipped some relevant content. Steve suggests not to >> >> include the attachments parameter in the method signature in WSDL. >> Won't >> >> axis complain that the received request does not match the method >> >> signature? I would like the WSDL to have the attachment defined. >> >> >> >> Also, I had already defined the following WSDL with a multipart mime >> >> request consisting of an id and attachment. Axis 1.2 generated the >> java >> >> stubs, etc correctly for that. Will that work? >> >> >> >> <s:element name="IdElement" type="s:string"/> >> >> <s:element name="AttachmentElement" type="s:base64Binary"/> >> >> >> >> <wsdl:message name="UploadAttachmentRequest"> >> >> <wsdl:part name="id" element="tns:IdElement"/> >> >> <wsdl:part name="attachment" >> element="tns:AttachmentElement"/> >> >> </wsdl:message> >> >> >> >> <wsdl:operation name="UploadAttachment"> >> >> <soap:operation soapAction="" style="document"/> >> >> <wsdl:input> >> >> <mime:multipartRelated> >> >> <mime:part> >> >> <soap:body part="id" use="literal"/> >> >> </mime:part> >> >> <mime:part> >> >> <mime:content part="attachment" >> >> type="application/msword"/> >> >> </mime:part> >> >> </mime:multipartRelated> >> >> </wsdl:input> >> >> <wsdl:output/> >> >> </wsdl:operation> >> >> >> >> >> >> Thanks, >> >> >> >> Vish. >> >> >> >> >> >> >-----Original Message----- >> >> >From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] >> >> >Sent: Wednesday, July 18, 2007 11:50 AM >> >> >To: axis-user@ws.apache.org >> >> >Subject: Re: Exchange word/pdf docs using axis java service to >> support >> >> .NE >> >> >T cl ient >> >> > >> >> >Neither .NET 1 nor Axis 1.2 supports the WS-I Attachments profile. >> You >> >> >should use DIME. See >> >> >http://www.mail-archive.com/axis- >> >> >[EMAIL PROTECTED]/msg08732/Fear_of_Attachments.pdf >> >> >for guidance. >> >> > >> >> >Anne >> >> > >> >> >On 7/17/07, Pantvaidya, Vishwajit <[EMAIL PROTECTED]> wrote: >> >> >> We are using Axis-Java 1.2.1 (not Axis2) and .NET2. >> >> >> >> >> >> >> >> >> >> >> >> >-----Original Message----- >> >> >> >From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] >> >> >> >Sent: Tuesday, July 17, 2007 5:08 AM >> >> >> >To: axis-user@ws.apache.org >> >> >> >Subject: Re: Exchange word/pdf docs using axis java service to >> >> support >> >> >.NET >> >> >> >cl ient >> >> >> > >> >> >> >Please confirm: are you using Axis 1.2 or Axis2 1.2? >> >> >> >And what version of .NET are you using? >> >> >> > >> >> >> >Anne >> >> >> > >> >> >> >On 7/16/07, Pantvaidya, Vishwajit <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> I need to add functionality that will enable our webservice >> built >> >> >using >> >> >> >axis >> >> >> >> java 1.2 to exchange word/pdf docs with a .NET client. I can do >> it >> >> >using >> >> >> >> just byte[] or using attachments. >> >> >> >> >> >> >> >> - Should I prefer attachments if file is large? Does using >> >> attachments >> >> >> >mean >> >> >> >> that the implementation splits the file automatically into >> packets >> >> >that >> >> >> >are >> >> >> >> individually delivered? >> >> >> >> >> >> >> >> - If using attachments, I would like the attachments interface >> to >> >> be >> >> >> >visible >> >> >> >> from wsdl - I guess that rules out SAAJ >> >> >> >> >> >> >> >> - The WS-I attachments profile >> >> >> >> http://www.ws-i.org/Profiles/AttachmentsProfile-1.0.html >> >> >> >> seems to recommend using XML attachment type wsi:swaRef. But >> does >> >> >anyone >> >> >> >> know if this will work with a .NET based client. Because >> elsewhere >> >> I >> >> >see >> >> >> >> statements that DIME is the only format that .NET supports. Is >> >> that >> >> >true? >> >> >> >> >> >> >> >> - If not swaRef, can I use MIME with base64binary, etc? >> >> >> >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >--------------------------------------------------------------------- >> >> >> >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] >> >> >> >> >> >> >> >> > >> >> >> >--------------------------------------------------------------------- >> >> >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] >> >> >> >> >> > >> >--------------------------------------------------------------------- >> >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] >> >> > >--------------------------------------------------------------------- >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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
