Re: Test update for MTOM/XOP/RRSHB
Christopher B Ferris <[email protected]> Fri, 27 Jul 2007 07:13:12 -0400
| Newsgroups | gmane.text.xml.distributed |
|---|---|
| Message-ID | <OFA5A936CF.96A2F360-ON85257325.003D3D3C-85257325.003D796B@us.ibm.com> |
This is a multipart message in MIME format. --=_alternative 003D76E885257325_= Content-Type: text/plain; charset="US-ASCII" Thanks, Anish! Yves, Could you update the link from the implementation page [1] to point to the updated tests in Anish's note [2]? [1] http://www.w3.org/2000/xp/Group/4/08/implementation.html [2] http://lists.w3.org/Archives/Public/xml-dist-app/2007Jul/0007.html Thanks, Cheers, Christopher Ferris STSM, Software Group Standards Strategy email: [email protected] blog: http://www.ibm.com/developerworks/blogs/page/chrisferris phone: +1 508 234 2986 [email protected] wrote on 07/25/2007 07:59:58 PM: > > This is a follow-up to my earlier email at [1]. > > I. Preface: > > The email at [1] provides a delta to the tests at [2] for the xmime NS > fixup. The tests at [2] point to two emails [3] and [4]. [3] describes > test which are labeled 1a, 1b, 2a, 2b, 3a, 4, 5, 6 and 7. [4] describes > tests which are labled RRSHB1, RRSHB2, RRSHB3 and RRSHB. > > This email merges the delta at [1] with the content of emails at [3] and > [4] so as to provide a single place to look for the updated tests. The > merged tests are listed below. > > II. Updated Tests 1-7 : > > ------------------------------------------------------------------- > Here are a set of test scenarios for MTOM. We will use these tests > during the Candidate Recommendation phase. As noted previously[1] the > tests will take the form of an echo test. These come in two forms; > > 1. A client implementation sends an MTOM message and the server > implementation returns the corresponding XML 1.0 message > 2. A client implementation sends an XML 1.0 message and the server > implementation returns the corresponding MTOM message > > In all cases elements with the namespace name > "http://example.org/mtom/data" and a local name of "Data" will be of a > type derived from xs:base64Binary. Such elements will have a xop:Include > element child in the MTOM messages and base64 text as children in the > XML case. A schema for the elements used is as follows: > > <xs:schema xmlns:xs='http://www.w3.org/2001/XMLSchema' > targetNamespace='http://example.org/mtom/data' > xmlns:x='http://example.org/mtom/data' > > > <xs:import namespace='http://www.w3.org/2005/05/xmlmime' /> > > <xs:element name='Data' > > <xs:complexType> > <xs:simpleContent> > <xs:extension base='xs:base64Binary' > > <xs:attribute ref='xmime:contentType' /> > </xs:extension> > </xs:simpleContent> > </xs:complexType> > </xs:element> > > <xs:element name='EchoTest' > > <xs:complexType> > <xs:sequence> > <xs:element ref='x:Data' minOccurs='1' maxOccurs='unbounded' /> > </xs:sequence> > </xs:complexType> > </xs:element> > > </xs:schema> > > I've listed the various tests below, with example XML messages. Please > note that in all cases, despite the vagaries of mailers, the x:Data > element do not have any whitespace characters as children. The amount of > base64 text sent ( as either text or optimized binary ) is unimportant. > However, to avoid running into memory limitations during testing, it > would be best to send smaller rather than larger binary parts. If > someone wants to propose an upper limit, let me know. I think most of my > own test messages come in below 512Kb. > > > > Test 1: Single binary part. Limit the number of x:Data elements in the > message to 1. An example XML version of the message will be as follows: > > <soap:Envelope xmlns:soap='http://www.w3.org/2003/05/soap-envelope' > > <soap:Body> > <x:Data xmlns:x='http://example.org/mtom/data' > >IK44HhIvWXSX2NIeoJyjiUfI5+ynntOwSmsYyf29ks0NuVSwaHWQedq6kn/qDql6Rmnu5W2 > a44HaiNSnF5B22g==</x:Data> > </soap:Body> > </soap:Envelope> > > Test 1a: Send XML, get back MTOM > Test 1b: Send MTOM, get back XML > > > > Test 2: Multiple binary parts. Allow any number of x:Data elements in > the message. An example XML version of the message will be as follows: > > <soap:Envelope xmlns:soap='http://www.w3.org/2003/05/soap-envelope' > > <soap:Body> > <x:Wrapper> > <x:Data xmlns:x='http://example.org/mtom/data' > >IK44HhIvWXSX2NIeoJyjiUfI5+ynntOwSmsYyf29ks0NuVSwaHWQedq6kn/qDql6Rmnu5W2 > a44HaiNSnF5B22g==</x:Data> > <x:Data xmlns:x='http://example.org/mtom/data' > >3T4iLkRXu+K/QNlhEJqaIt8uE > ZHpS7kRdXBLNhiet+xYAUyTiNPFGBuc8EPti+vc9Fe3mMNxAlGFELkUDEXKA==</x:Data> > <x:Data xmlns:x='http://example.org/mtom/data' > >g0txZNBHOf5ho5pv7NsXLm5m1 > 3dmG5MC2GCUW2bjRar55raIMPUvkiYFpsJ/dwbKtgtZUb07DWi3b4tvst6Xfg==</x:Data> > </x:Wrapper> > </soap:Body> > </soap:Envelope> > > Test 2a: Send XML, get back MTOM > Test 2b: Send MTOM, get back XML > > > > Test 3: Testing xmime:contentType attribute and MIME content-type > header. The xmime:contentType header is specified on x:Data elements in > an XML message. An MTOM message is returned with the MIME content-type > of the binary parts set to the appropriate value. An example XML version > of the message will be as follows: > > <soap:Envelope xmlns:soap='http://www.w3.org/2003/05/soap-envelope' > > <soap:Body> > <x:Data xmlns:x='http://example.org/mtom/data' > xmlns:xmime='http://www.w3.org/2005/05/xmlmime' > xmime:contentType='image/jpeg' > >IK44HhIvWXSX2NIeoJyjiUfI5+ynntOwSmsYyf29ks0NuVSwaHWQedq6kn/qDql6Rmnu5W2 > a44HaiNSnF5B22g==</x:Data> > </soap:Body> > </soap:Envelope> > > The corresponding MTOM message would set the content-type header of the > binary part for the x:Data element to 'image/jpeg' > > Test 3a: Send XML, get back MTOM > Test 3b: Not applicable. > > > > Test 4: Failure test: Missing MIME part. Send an MTOM message with a > xop:Include element that references a non-existent MIME part. A SOAP > fault should be returned indicating that the message was in error. > > Test 5: Failure test: Use of content-location. Send an MTOM message that > references one or more MIME parts by content-location (rather than > content-id). A SOAP fault should be returned indicating that the message > was in error. > > Test 6: Failure test: Use of startinfo parameter that does NOT specify > application/soap+xml. Send an MTOM message that uses a startinfo of > image/jpeg. A SOAP fault should be returned indicating that the message > was in error. > > Test 7: Failure test: Use of type parameter on the root part that does > NOT specify application/soap+xml. Send an MTOM message that uses a type > parameter of image/jpeg for the root part. A SOAP fault should be > returned indicating that the message was in error. > > [1] http://lists.w3.org/Archives/Public/xml-dist-app/2004Jul/0025.html > ------------------------------------------------------------------- > > > > III. Updated RRSHB Tests > > ------------------------------------------------------------------- > RRSHB Implementation/Interop tests for the CR phase :- > > The tests below cover the following: > * basic RRSHB testing > * testing with multiple RRSH blocks that represent the same resource but > have different meta-data > * RRSHB testing in conjunction with xmlmime:contentType attribute > * RRSHB testing in conjunction with MTOM > > > The schema for the elements and attributes used in the tests is as > follows (reuses the 'Data' element from MTOM tests with different > namespace): > > <xs:schema xmlns:xs='http://www.w3.org/2001/XMLSchema' > targetNamespace='http://example.org/rrshb/test' > xmlns:x='http://example.org/rrshb/test' > > > <xs:import namespace='http://www.w3.org/2005/05/xmlmime' /> > > <xs:element name='Data' > > <xs:complexType> > <xs:simpleContent> > <xs:extension base='xs:base64Binary' > > <xs:attribute ref='xmime:contentType' /> > </xs:extension> > </xs:simpleContent> > </xs:complexType> > </xs:element> > > <xs:element name='GetResourceRepresentation' > > <xs:complexType> > <xs:attribute name='resource' type='xs:anyURI' use='required' /> > </xs:complexType> > </xs:element> > > <xs:element name='ResourceRepresentation' > > <xs:complexType> > <xs:sequence> > <xs:element ref='x:Data' minOccurs='1' maxOccurs='unbounded' /> > </xs:sequence> > <xs:attribute name='resource' type='xs:anyURI' use='required' /> > </xs:complexType> > </xs:element> > > </xs:schema> > > > > Test 1: Basic RRSHB testing > > The tests consists of - > > Request message: node A (client) sends a message to node B (server) with > Resource Representation Header block(s) for the resource identified by > "http://example.org/rrshb/test/data". SOAP Body consists of the element > {http://example.org/rrshb/test}GetResourceRepresentation. If multiple > RRSHB are present in the message they must have different values for the > attribute "xmlmime:contentType". > > example request message: > > <soap:Envelope xmlns:soap='http://www.w3.org/2003/05/soap-envelope' > xmlns:rep='http://www.w3.org/2004/08/representation' > xmlns:xmlmime='http://www.w3.org/2005/05/xmlmime'> > <soap:Header> > <rep:Representation resource='http://example.org/rrshb/test/data'> > <rep:Data xmlmime:contentType='image/png'>...</rep:Data> > </rep:Representation> > <rep:Representation resource='http://example.org/rrshb/test/data'> > <rep:Data xmlmime:contentType='image/jpeg'>...</rep:Data> > </rep:Representation> > </soap:Header> > <soap:Body> > <x:GetResourceRepresentation > xmlns:x='http://example.org/rrshb/test' > resource='http://example.org/rrshb/test/data' /> > </x:GetResourceRepresentation> > </soap:Body> > </soap:Envelope> > > Response message: node B (server) responds to node A (client) by > including all the representations of the resource identified by > "http://example.org/rrshb/test/data", in the SOAP Body as the content of > the element {http://example.org/rrshb/test}ResourceRepresentation. > > example message: > > <soap:Envelope xmlns:soap='http://www.w3.org/2003/05/soap-envelope' > xmlns:rep='http://www.w3.org/2004/08/representation' > xmlns:xmlmime='http://www.w3.org/2005/05/xmlmime'> > <soap:Body> > <x:ResourceRepresentation xmlns:x='http://example.org/rrshb/test' > resource='http://example.org/rrshb/test/data'/> > <x:Data xmlmime:contentType='image/png'>...</x:Data> > <x:Data xmlmime:contentType='image/jpeg'>...</x:Data> > </soap:Body> > </soap:Envelope> > > > Test 2: RRSHB testing with MTOM > > Same as test 1 but the request message uses MTOM to optimize all the > RRSHB (by using xop:Include) and the response message uses MTOM to > optimize all the x:Data elements (by using xop:Include) > > > Test 3: RRSHB testing with "reinsert" > > In this test the SOAP path consists of node A --> node B --> node A. > Node B acts as a forwarding intermediary. The message sent from node A > to node B is same as in test 1, but all the RRSHB headers have the > "reinsert" and "relay" attribute with the value of "true". The message > sent from node B to node A is same as in test 1, but all the RRSHB > headers included in the request message are also present in the response > message. > > > The tests do not cover section "4.3.3 Extension example: HTTP resolver > extension", as this was considered to be an example and non-normative. > ------------------------------------------------------------------- > > > -Anish > -- > > [1] http://lists.w3.org/Archives/Public/xml-dist-app/2007Jul/0003.html > [2] http://www.w3.org/2000/xp/Group/4/08/implementation.html > [3] http://lists.w3.org/Archives/Public/xml-dist-app/2004Aug/0013.html > [4] http://lists.w3.org/Archives/Public/xml-dist-app/2004Sep/0013.html > --=_alternative 003D76E885257325_= Content-Type: text/html; charset="US-ASCII" <br><font size=2 face="sans-serif">Thanks, Anish!</font> <br> <br><font size=2 face="sans-serif">Yves,</font> <br> <br><font size=2 face="sans-serif">Could you update the link from the implementation page [1] to point to the updated tests in Anish's note [2]?</font> <br> <br><font size=2 face="sans-serif">[1] http://www.w3.org/2000/xp/Group/4/08/implementation.html</font> <br><font size=2 face="sans-serif">[2] http://lists.w3.org/Archives/Public/xml-dist-app/2007Jul/0007.html</font> <br> <br><font size=2 face="sans-serif">Thanks,</font> <br> <br><font size=2 face="sans-serif">Cheers,</font> <br> <br><font size=2 face="sans-serif">Christopher Ferris<br> STSM, Software Group Standards Strategy<br> email: [email protected]<br> blog: http://www.ibm.com/developerworks/blogs/page/chrisferris<br> phone: +1 508 234 2986</font> <br> <br><tt><font size=2>[email protected] wrote on 07/25/2007 07:59:58 PM:<br> <br> > <br> > This is a follow-up to my earlier email at [1].<br> > <br> > I. Preface:<br> > <br> > The email at [1] provides a delta to the tests at [2] for the xmime NS <br> > fixup. The tests at [2] point to two emails [3] and [4]. [3] describes <br> > test which are labeled 1a, 1b, 2a, 2b, 3a, 4, 5, 6 and 7. [4] describes <br> > tests which are labled RRSHB1, RRSHB2, RRSHB3 and RRSHB.<br> > <br> > This email merges the delta at [1] with the content of emails at [3] and <br> > [4] so as to provide a single place to look for the updated tests. The <br> > merged tests are listed below.<br> > <br> > II. Updated Tests 1-7 :<br> > <br> > -------------------------------------------------------------------<br> > Here are a set of test scenarios for MTOM. We will use these tests<br> > during the Candidate Recommendation phase. As noted previously[1] the<br> > tests will take the form of an echo test. These come in two forms;<br> > <br> > 1. A client implementation sends an MTOM message and the server<br> > implementation returns the corresponding XML 1.0 message<br> > 2. A client implementation sends an XML 1.0 message and the server<br> > implementation returns the corresponding MTOM message<br> > <br> > In all cases elements with the namespace name<br> > "http://example.org/mtom/data" and a local name of "Data" will be of a<br> > type derived from xs:base64Binary. Such elements will have a xop:Include<br> > element child in the MTOM messages and base64 text as children in the<br> > XML case. A schema for the elements used is as follows:<br> > <br> > <xs:schema xmlns:xs='http://www.w3.org/2001/XMLSchema'<br> > targetNamespace='http://example.org/mtom/data'<br> > xmlns:x='http://example.org/mtom/data' ><br> > <br> > <xs:import namespace='http://www.w3.org/2005/05/xmlmime' /><br> > <br> > <xs:element name='Data' ><br> > <xs:complexType><br> > <xs:simpleContent><br> > <xs:extension base='xs:base64Binary' ><br> > <xs:attribute ref='xmime:contentType' /><br> > </xs:extension><br> > </xs:simpleContent><br> > </xs:complexType><br> > </xs:element><br> > <br> > <xs:element name='EchoTest' ><br> > <xs:complexType><br> > <xs:sequence><br> > <xs:element ref='x:Data' minOccurs='1' maxOccurs='unbounded' /><br> > </xs:sequence><br> > </xs:complexType><br> > </xs:element><br> > <br> > </xs:schema><br> > <br> > I've listed the various tests below, with example XML messages. Please<br> > note that in all cases, despite the vagaries of mailers, the x:Data<br> > element do not have any whitespace characters as children. The amount of<br> > base64 text sent ( as either text or optimized binary ) is unimportant.<br> > However, to avoid running into memory limitations during testing, it<br> > would be best to send smaller rather than larger binary parts. If<br> > someone wants to propose an upper limit, let me know. I think most of my<br> > own test messages come in below 512Kb.<br> > <br> > <br> > <br> > Test 1: Single binary part. Limit the number of x:Data elements in the<br> > message to 1. An example XML version of the message will be as follows:<br> > <br> > <soap:Envelope xmlns:soap='http://www.w3.org/2003/05/soap-envelope' ><br> > <soap:Body><br> > <x:Data xmlns:x='http://example.org/mtom/data'<br> > >IK44HhIvWXSX2NIeoJyjiUfI5+ynntOwSmsYyf29ks0NuVSwaHWQedq6kn/qDql6Rmnu5W2<br> > a44HaiNSnF5B22g==</x:Data><br> > </soap:Body><br> > </soap:Envelope><br> > <br> > Test 1a: Send XML, get back MTOM<br> > Test 1b: Send MTOM, get back XML<br> > <br> > <br> > <br> > Test 2: Multiple binary parts. Allow any number of x:Data elements in<br> > the message. An example XML version of the message will be as follows:<br> > <br> > <soap:Envelope xmlns:soap='http://www.w3.org/2003/05/soap-envelope' ><br> > <soap:Body><br> > <x:Wrapper><br> > <x:Data xmlns:x='http://example.org/mtom/data'<br> > >IK44HhIvWXSX2NIeoJyjiUfI5+ynntOwSmsYyf29ks0NuVSwaHWQedq6kn/qDql6Rmnu5W2<br> > a44HaiNSnF5B22g==</x:Data><br> > <x:Data xmlns:x='http://example.org/mtom/data'<br> > >3T4iLkRXu+K/QNlhEJqaIt8uE<br> > ZHpS7kRdXBLNhiet+xYAUyTiNPFGBuc8EPti+vc9Fe3mMNxAlGFELkUDEXKA==</x:Data><br> > <x:Data xmlns:x='http://example.org/mtom/data'<br> > >g0txZNBHOf5ho5pv7NsXLm5m1<br> > 3dmG5MC2GCUW2bjRar55raIMPUvkiYFpsJ/dwbKtgtZUb07DWi3b4tvst6Xfg==</x:Data><br> > </x:Wrapper><br> > </soap:Body><br> > </soap:Envelope><br> > <br> > Test 2a: Send XML, get back MTOM<br> > Test 2b: Send MTOM, get back XML<br> > <br> > <br> > <br> > Test 3: Testing xmime:contentType attribute and MIME content-type<br> > header. The xmime:contentType header is specified on x:Data elements in<br> > an XML message. An MTOM message is returned with the MIME content-type<br> > of the binary parts set to the appropriate value. An example XML version<br> > of the message will be as follows:<br> > <br> > <soap:Envelope xmlns:soap='http://www.w3.org/2003/05/soap-envelope' ><br> > <soap:Body><br> > <x:Data xmlns:x='http://example.org/mtom/data'<br> > xmlns:xmime='http://www.w3.org/2005/05/xmlmime'<br> > xmime:contentType='image/jpeg'<br> > >IK44HhIvWXSX2NIeoJyjiUfI5+ynntOwSmsYyf29ks0NuVSwaHWQedq6kn/qDql6Rmnu5W2<br> > a44HaiNSnF5B22g==</x:Data><br> > </soap:Body><br> > </soap:Envelope><br> > <br> > The corresponding MTOM message would set the content-type header of the<br> > binary part for the x:Data element to 'image/jpeg'<br> > <br> > Test 3a: Send XML, get back MTOM<br> > Test 3b: Not applicable.<br> > <br> > <br> > <br> > Test 4: Failure test: Missing MIME part. Send an MTOM message with a<br> > xop:Include element that references a non-existent MIME part. A SOAP<br> > fault should be returned indicating that the message was in error.<br> > <br> > Test 5: Failure test: Use of content-location. Send an MTOM message that<br> > references one or more MIME parts by content-location (rather than<br> > content-id). A SOAP fault should be returned indicating that the message<br> > was in error.<br> > <br> > Test 6: Failure test: Use of startinfo parameter that does NOT specify<br> > application/soap+xml. Send an MTOM message that uses a startinfo of<br> > image/jpeg. A SOAP fault should be returned indicating that the message<br> > was in error.<br> > <br> > Test 7: Failure test: Use of type parameter on the root part that does<br> > NOT specify application/soap+xml. Send an MTOM message that uses a type<br> > parameter of image/jpeg for the root part. A SOAP fault should be<br> > returned indicating that the message was in error.<br> > <br> > [1] http://lists.w3.org/Archives/Public/xml-dist-app/2004Jul/0025.html<br> > -------------------------------------------------------------------<br> > <br> > <br> > <br> > III. Updated RRSHB Tests<br> > <br> > -------------------------------------------------------------------<br> > RRSHB Implementation/Interop tests for the CR phase :-<br> > <br> > The tests below cover the following:<br> > * basic RRSHB testing<br> > * testing with multiple RRSH blocks that represent the same resource but<br> > have different meta-data<br> > * RRSHB testing in conjunction with xmlmime:contentType attribute<br> > * RRSHB testing in conjunction with MTOM<br> > <br> > <br> > The schema for the elements and attributes used in the tests is as<br> > follows (reuses the 'Data' element from MTOM tests with different<br> > namespace):<br> > <br> > <xs:schema xmlns:xs='http://www.w3.org/2001/XMLSchema'<br> > targetNamespace='http://example.org/rrshb/test'<br> > xmlns:x='http://example.org/rrshb/test' ><br> > <br> > <xs:import namespace='http://www.w3.org/2005/05/xmlmime' /><br> > <br> > <xs:element name='Data' ><br> > <xs:complexType><br> > <xs:simpleContent><br> > <xs:extension base='xs:base64Binary' ><br> > <xs:attribute ref='xmime:contentType' /><br> > </xs:extension><br> > </xs:simpleContent><br> > </xs:complexType><br> > </xs:element><br> > <br> > <xs:element name='GetResourceRepresentation' ><br> > <xs:complexType><br> > <xs:attribute name='resource' type='xs:anyURI' use='required' /><br> > </xs:complexType><br> > </xs:element><br> > <br> > <xs:element name='ResourceRepresentation' ><br> > <xs:complexType><br> > <xs:sequence><br> > <xs:element ref='x:Data' minOccurs='1' maxOccurs='unbounded' /><br> > </xs:sequence><br> > <xs:attribute name='resource' type='xs:anyURI' use='required' /><br> > </xs:complexType><br> > </xs:element><br> > <br> > </xs:schema><br> > <br> > <br> > <br> > Test 1: Basic RRSHB testing<br> > <br> > The tests consists of -<br> > <br> > Request message: node A (client) sends a message to node B (server) with<br> > Resource Representation Header block(s) for the resource identified by<br> > "http://example.org/rrshb/test/data". SOAP Body consists of the element<br> > {http://example.org/rrshb/test}GetResourceRepresentation. If multiple<br> > RRSHB are present in the message they must have different values for the<br> > attribute "xmlmime:contentType".<br> > <br> > example request message:<br> > <br> > <soap:Envelope xmlns:soap='http://www.w3.org/2003/05/soap-envelope'<br> > xmlns:rep='http://www.w3.org/2004/08/representation'<br> > xmlns:xmlmime='http://www.w3.org/2005/05/xmlmime'><br> > <soap:Header><br> > <rep:Representation resource='http://example.org/rrshb/test/data'><br> > <rep:Data xmlmime:contentType='image/png'>...</rep:Data><br> > </rep:Representation><br> > <rep:Representation resource='http://example.org/rrshb/test/data'><br> > <rep:Data xmlmime:contentType='image/jpeg'>...</rep:Data><br> > </rep:Representation><br> > </soap:Header><br> > <soap:Body><br> > <x:GetResourceRepresentation<br> > xmlns:x='http://example.org/rrshb/test'<br> > resource='http://example.org/rrshb/test/data' /><br> > </x:GetResourceRepresentation><br> > </soap:Body><br> > </soap:Envelope><br> > <br> > Response message: node B (server) responds to node A (client) by <br> > including all the representations of the resource identified by <br> > "http://example.org/rrshb/test/data", in the SOAP Body as the content of <br> > the element {http://example.org/rrshb/test}ResourceRepresentation.<br> > <br> > example message:<br> > <br> > <soap:Envelope xmlns:soap='http://www.w3.org/2003/05/soap-envelope'<br> > xmlns:rep='http://www.w3.org/2004/08/representation'<br> > xmlns:xmlmime='http://www.w3.org/2005/05/xmlmime'><br> > <soap:Body><br> > <x:ResourceRepresentation xmlns:x='http://example.org/rrshb/test' <br> > resource='http://example.org/rrshb/test/data'/><br> > <x:Data xmlmime:contentType='image/png'>...</x:Data><br> > <x:Data xmlmime:contentType='image/jpeg'>...</x:Data><br> > </soap:Body><br> > </soap:Envelope><br> > <br> > <br> > Test 2: RRSHB testing with MTOM<br> > <br> > Same as test 1 but the request message uses MTOM to optimize all the <br> > RRSHB (by using xop:Include) and the response message uses MTOM to<br> > optimize all the x:Data elements (by using xop:Include)<br> > <br> > <br> > Test 3: RRSHB testing with "reinsert"<br> > <br> > In this test the SOAP path consists of node A --> node B --> node A. <br> > Node B acts as a forwarding intermediary. The message sent from node A <br> > to node B is same as in test 1, but all the RRSHB headers have the <br> > "reinsert" and "relay" attribute with the value of "true". The message <br> > sent from node B to node A is same as in test 1, but all the RRSHB <br> > headers included in the request message are also present in the response<br> > message.<br> > <br> > <br> > The tests do not cover section "4.3.3 Extension example: HTTP resolver<br> > extension", as this was considered to be an example and non-normative.<br> > -------------------------------------------------------------------<br> > <br> > <br> > -Anish<br> > --<br> > <br> > [1] http://lists.w3.org/Archives/Public/xml-dist-app/2007Jul/0003.html<br> > [2] http://www.w3.org/2000/xp/Group/4/08/implementation.html<br> > [3] http://lists.w3.org/Archives/Public/xml-dist-app/2004Aug/0013.html<br> > [4] http://lists.w3.org/Archives/Public/xml-dist-app/2004Sep/0013.html<br> > <br> </font></tt> --=_alternative 003D76E885257325_=--