Here it is... Thanks, dims
--- Lance Andersen <[EMAIL PROTECTED]> wrote: > Hi Dims, > > Could you do me a favor please and send me the jtr file from the test > run for > > saaj\api\javax_xml_soap\AttachmentPart\URLClient_getAllMimeHeaders1Test_from_standalone > > > Regards, > Lance > > Davanum Srinivas wrote: > > >Lance, > > > >Attached is a Challenge for 23 failures of current Axis code. The TCK does > >not allow us to add > our > >own custom MimeHeaders when we create a SOAP Part or Attachment Part. If we > >comment our 2 lines > of > >code that add a auto-generated content-id (Line 101 in > org.apache.axis.attachments.AttachmentPart > >and Line 147 in org.apache.axis.attachments.SOAPPart) then we can pass these > >23 tests. BUT we > >don't want to do this as this is a condition imposed by the TCK and NOT in > >any of the specs > that > >we know of (SAAJ/JAXM/JAX-RPC). > > > >Thanks, > >dims > > > > > > > > > >===== > >Davanum Srinivas - http://xml.apache.org/~dims/ > > > >__________________________________________________ > >Do You Yahoo!? > >Sign up for SBC Yahoo! Dial - First Month Free > >http://sbc.yahoo.com > > > >------------------------------------------------------------------------ > > > >1. Licensee Name: Apache > > > >2. TCK and version: SAAJ (saaj_tck-1_1-fcs-bin-06_jun_2002.zip) > > > >3. SDK version: NA > > > >4. Priority (low, medium, high, ): HIGH > > > >5. Specification Reference: > > - Spec Name: SOAP with Attachments API for Java > > - Spec version : (SAAJ) v1.1 Maintenance Release > > - Spec date: June 2002 > > - Page/Section to reference: NA > > > >6. Test Name(s): A total of 23 tests fail. > > > > saaj\api\javax_xml_soap\AttachmentPart\URLClient_getAllMimeHeaders1Test_from_standalone > > > > saaj\api\javax_xml_soap\AttachmentPart\URLClient_getAllMimeHeaders2Test_from_standalone > > > > saaj\api\javax_xml_soap\AttachmentPart\URLClient_getAllMimeHeaders3Test_from_standalone > > > > saaj\api\javax_xml_soap\AttachmentPart\URLClient_getAllMimeHeaders4Test_from_standalone > > > saaj\api\javax_xml_soap\AttachmentPart\URLClient_getMatchingMimeHeaders5Test_from_standalone > > > > saaj\api\javax_xml_soap\AttachmentPart\URLClient_getMimeHeader2Test_from_standalone > > > saaj\api\javax_xml_soap\AttachmentPart\URLClient_getNonMatchingMimeHeaders4Test_from_standalone > > > > saaj\api\javax_xml_soap\AttachmentPart\URLClient_removeMimeHeader1Test_from_standalone > > > > saaj\api\javax_xml_soap\AttachmentPart\URLClient_removeMimeHeader3Test_from_standalone > > > > saaj\api\javax_xml_soap\AttachmentPart\URLClient_removeMimeHeader4Test_from_standalone > > > > saaj\api\javax_xml_soap\AttachmentPart\URLClient_setMimeHeader2Test_from_standalone > > > > saaj\api\javax_xml_soap\SOAPPart\URLClient_getAllMimeHeaders1Test_from_standalone > > > > saaj\api\javax_xml_soap\SOAPPart\URLClient_getAllMimeHeaders2Test_from_standalone > > > > saaj\api\javax_xml_soap\SOAPPart\URLClient_getAllMimeHeaders3Test_from_standalone > > > > saaj\api\javax_xml_soap\SOAPPart\URLClient_getAllMimeHeaders4Test_from_standalone > > > > saaj\api\javax_xml_soap\SOAPPart\URLClient_getMatchingMimeHeaders5Test_from_standalone > > > > saaj\api\javax_xml_soap\SOAPPart\URLClient_getMimeHeader2Test_from_standalone > > > > saaj\api\javax_xml_soap\SOAPPart\URLClient_getNonMatchingMimeHeaders1Test_from_standalone > > > > saaj\api\javax_xml_soap\SOAPPart\URLClient_getNonMatchingMimeHeaders4Test_from_standalone > > > > saaj\api\javax_xml_soap\SOAPPart\URLClient_removeMimeHeader1Test_from_standalone > > > > saaj\api\javax_xml_soap\SOAPPart\URLClient_removeMimeHeader3Test_from_standalone > > > > saaj\api\javax_xml_soap\SOAPPart\URLClient_removeMimeHeader4Test_from_standalone > > > > saaj\api\javax_xml_soap\SOAPPart\URLClient_setMimeHeader2Test_from_standalone > > > >7. Problem Description: > > > >Axis automatically generates "Content-Id" headers (CID) when attachment > >parts and soap parts > are first created. In addition the logic tries to as best as possible to make > CIDs universally > unique for each attachment as required for MIME type attachements. This > allows applications > using Axis attachments to simply request the attachment's CID and immediately > use it as a > reference for an href attribute without the need for first generating this > CID itself and having > to set it in the attachment part. Further more I don't believe that this > behavior in any way > contradicts the JAX-M, JAX-RPC or SAAJ specifications. However, the TCK has > tests which set > headers and then validate that ONLY those headers are present. Which fails > for Axis. These > tests should be changed to validate that headers which it set are present but > ignore additional > headers. Or, obtain the list of already present headers, add additional > headers, and then > validate that the headers within the attachments hav! > >e ! > >been updated appropriately include the new headers added or modified. > > > > > > -- > Lance Andersen email: [EMAIL PROTECTED] > Sun Microsystems Inc. phone: (781) 442-2037 > 1 Network Drive, UBUR02-301 fax : (781) 442-1610 > Burlington, MA 01803 > > > ===== Davanum Srinivas - http://xml.apache.org/~dims/ __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com
URLClient_getAllMimeHeaders1Test_from_standalone.jtr
Description: URLClient_getAllMimeHeaders1Test_from_standalone.jtr
