Return-Path: X-Original-To: apmail-axis-java-dev-archive@www.apache.org Delivered-To: apmail-axis-java-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 11BCC10E5A for ; Sat, 9 Nov 2013 11:07:37 +0000 (UTC) Received: (qmail 91652 invoked by uid 500); 9 Nov 2013 11:07:28 -0000 Delivered-To: apmail-axis-java-dev-archive@axis.apache.org Received: (qmail 90984 invoked by uid 500); 9 Nov 2013 11:07:21 -0000 Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@axis.apache.org Delivered-To: mailing list java-dev@axis.apache.org Received: (qmail 90973 invoked by uid 99); 9 Nov 2013 11:07:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Nov 2013 11:07:17 +0000 Date: Sat, 9 Nov 2013 11:07:17 +0000 (UTC) From: "Maarten van den Broek (JIRA)" To: java-dev@axis.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AXIS2-5597) The adressing module adds the addressing namespace declaration in the header element, which is not allowed by BP 1.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AXIS2-5597?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1381= 8105#comment-13818105 ]=20 Maarten van den Broek commented on AXIS2-5597: ---------------------------------------------- I was on the wrong track with BP1.2 compliancy. Actually, BP1.1 has been ch= ecked. I have downloaded the BP1.1 compliancy test tools from http://www.ws= -i.org/Testing/Tools/2005/06/WSI_Test_Java_Final_1.1.zip and tested the mes= sage with these tools. The conclusion of this test is that the axis2 addressing module does not pr= oduce BP1.1 compliant messages. The reason for this I have given in the fir= st entry for this post. It would be nice if this issue could be fixed. The input and the results of the test are given below. The message as captured by TCPIPMON in Eclipse was: POST /ictu-ocvwus-ws/OSB2W-be HTTP/1.1 Content-Type: text/xml; charset=3DUTF-8 SOAPAction: "http://service.compliance.osb.gbo.overheid.nl/wsdl/2009/02/com= pliancevoorziening-v2/IOSB2ComplianceService/toUpperCaseRequest" User-Agent: Axis2 Content-Length: 900 Host: localhost:4041 http://localhost:4041/ictu-ocvwus-ws/OSB2W-be http://www.w3.org/2005/08/addressing/anonymous http://www.w3.org/2005/08/addressing/anonymous urn:uuid:bc017897-807f-45e3-86a6-e1a1bb98e2df= @gm.messagedesign.nl http://service.compliance.osb.gbo.overheid.nl/wsdl/2009/02/= compliancevoorziening-v2/IOSB2ComplianceService/toUpperCaseRequest abc The test resulted in the following output of the Monitor tool for the BP1.= 1 compliancy test: This configuration file is used to test the WS-I= sample applications running on a single system. 60 3 Test WUS-BE 4041 https://wus.cv.prod.osb.overheid= .nl 1000 15 <?xml version=3D'1.0' encoding=3D'UTF-8&a= pos;?><soapenv:Envelope xmlns:soapenv=3D"http://schemas.xmlsoap.= org/soap/envelope/"><soapenv:Header xmlns:wsa=3D"http://www= .w3.org/2005/08/addressing"><wsa:To>http://localhost:4041/ict= u-ocvwus-ws/OSB2W-be</wsa:To><wsa:ReplyTo><wsa:Address>ht= tp://www.w3.org/2005/08/addressing/anonymous</wsa:Address></wsa:Re= plyTo><wsa:From><wsa:Address>http://www.w3.org/2005/08/addre= ssing/anonymous</wsa:Address></wsa:From><wsa:MessageID>ur= n:uuid:f5cf038d-2dcd-422b-8f46-197bcfc06426@gm.messagedesign.nl</wsa:Mes= sageID><wsa:Action>http://service.compliance.osb.gbo.overheid.nl/w= sdl/2009/02/compliancevoorziening-v2/IOSB2ComplianceService/toUpperCaseRequ= est</wsa:Action></soapenv:Header><soapenv:Body><tns:to= UpperCase xmlns:tns=3D"http://service.compliance.osb.gbo.overheid.nl/2= 00706/osb-compliancevoorziening.xsd"><tns:data>abc</tns:da= ta></tns:toUpperCase></soapenv:Body></soapenv:Envelope>= ; 127.0.0.1:51798 wus.cv.prod.osb.overheid.nl:80 POST /ictu-ocvwus-ws/OSB2W-be HTTP/1.1 Content-Type: text/xml; charset=3DUTF-8 SOAPAction: "http://service.compliance.osb.gbo.overheid.nl/wsdl/2009/0= 2/compliancevoorziening-v2/IOSB2ComplianceService/toUpperCaseRequest"&= #xd; User-Agent: Axis2 Host: localhost:4041 Content-Length: 900 <?xml version=3D'1.0' encoding=3D'UTF-8&a= pos;?><S:Envelope xmlns:S=3D"http://schemas.xmlsoap.org/soap/env= elope/"><S:Header><To xmlns=3D"http://www.w3.org/2005= /08/addressing">http://www.w3.org/2005/08/addressing/anonymous</= To><Action xmlns=3D"http://www.w3.org/2005/08/addressing"&g= t;http://service.compliance.osb.gbo.overheid.nl/wsdl/2009/02/compliancevoor= ziening-v2/IOSB2ComplianceService/toUpperCaseResponse</Action><Mes= sageID xmlns=3D"http://www.w3.org/2005/08/addressing">uuid:b89= b2f69-362f-475c-83ad-2b6fd000931b</MessageID><RelatesTo xmlns=3D&q= uot;http://www.w3.org/2005/08/addressing">urn:uuid:f5cf038d-2dcd-42= 2b-8f46-197bcfc06426@gm.messagedesign.nl</RelatesTo></S:Header>= <S:Body><ns2:toUpperCaseResponse xmlns=3D"http://www.logius.n= l/digikoppeling/gb/2010/10" xmlns:ns2=3D"http://service.complianc= e.osb.gbo.overheid.nl/200706/osb-compliancevoorziening.xsd" xmlns:ns3= =3D"http://service.compliance.osb.gbo.overheid.nl/xsd/2012/03/complian= cevoorziening-v2_2" xmlns:ns4=3D"http://service.compliance.osb.gb= o.overheid.nl/xsd/2009/02/compliancevoorziening-v2"><ns2:dataUit= >ABC</ns2:dataUit></ns2:toUpperCaseResponse></S:Body>&= lt;/S:Envelope> wus.cv.prod.osb.overheid.nl:80 127.0.0.1:51798 HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Set-Cookie: JSESSIONID=3DA16EDFE6DCC0D2A9BC4AAA275E3692B1; Path=3D/ictu-ocv= wus-ws Content-Type: text/xml;charset=3Dutf-8 Date: Sat, 09 Nov 2013 10:15:28 GMT Content-Length: 1105 Applying the analyzer tool to this output resulted in the following report = file with BP1600 failed: false d:/java/wsi-test-tools/commo= n/profiles/SSBP10_BP11_TAD.xml d:/java/ws= i-test-tools/java/samples/logWUS-BE.xml This configuration file is used to test the WS-I= sample applications running on a single system. <?xml version=3D'1.0' encoding=3D&apos= ;UTF-8'?><soapenv:Envelope xmlns:soapenv=3D"http://schemas.= xmlsoap.org/soap/envelope/"><soapenv:Header xmlns:wsa=3D"ht= tp://www.w3.org/2005/08/addressing"><wsa:To>http://localhost:= 4041/ictu-ocvwus-ws/OSB2W-be</wsa:To><wsa:ReplyTo><wsa:Addre= ss>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address><= ;/wsa:ReplyTo><wsa:From><wsa:Address>http://www.w3.org/2005/= 08/addressing/anonymous</wsa:Address></wsa:From><wsa:Message= ID>urn:uuid:f5cf038d-2dcd-422b-8f46-197bcfc06426@gm.messagedesign.nl<= /wsa:MessageID><wsa:Action>http://service.compliance.osb.gbo.overh= eid.nl/wsdl/2009/02/compliancevoorziening-v2/IOSB2ComplianceService/toUpper= CaseRequest</wsa:Action></soapenv:Header><soapenv:Body>&l= t;tns:toUpperCase xmlns:tns=3D"http://service.compliance.osb.gbo.overh= eid.nl/200706/osb-compliancevoorziening.xsd"><tns:data>abc<= ;/tns:data></tns:toUpperCase></soapenv:Body></soapenv:Env= elope> 127.0.0.1:51798 wus.cv.prod.osb.overheid.nl:80 POST /ictu-ocvwus-ws/OSB2W-be HTTP/1.1 Content-Type: text/xml; charset=3DUTF-8 SOAPAction: "http://service.compliance.osb.gbo.overheid.nl/wsdl/2009/0= 2/compliancevoorziening-v2/IOSB2ComplianceService/toUpperCaseRequest"&= #xd; User-Agent: Axis2 Host: localhost:4041 Content-Length: 900 HTTP allows arbitrary headers to occu= r in messages. =20 Element Location: lineNumber=3D34 <?xml version=3D'1.0' encoding=3D&apos= ;UTF-8'?><S:Envelope xmlns:S=3D"http://schemas.xmlsoap.org/= soap/envelope/"><S:Header><To xmlns=3D"http://www.w3.= org/2005/08/addressing">http://www.w3.org/2005/08/addressing/anonym= ous</To><Action xmlns=3D"http://www.w3.org/2005/08/addressing= ">http://service.compliance.osb.gbo.overheid.nl/wsdl/2009/02/compli= ancevoorziening-v2/IOSB2ComplianceService/toUpperCaseResponse</Action>= ;<MessageID xmlns=3D"http://www.w3.org/2005/08/addressing">= uuid:b89b2f69-362f-475c-83ad-2b6fd000931b</MessageID><RelatesTo xm= lns=3D"http://www.w3.org/2005/08/addressing">urn:uuid:f5cf038d= -2dcd-422b-8f46-197bcfc06426@gm.messagedesign.nl</RelatesTo></S:He= ader><S:Body><ns2:toUpperCaseResponse xmlns=3D"http://www.= logius.nl/digikoppeling/gb/2010/10" xmlns:ns2=3D"http://service.c= ompliance.osb.gbo.overheid.nl/200706/osb-compliancevoorziening.xsd" xm= lns:ns3=3D"http://service.compliance.osb.gbo.overheid.nl/xsd/2012/03/c= ompliancevoorziening-v2_2" xmlns:ns4=3D"http://service.compliance= .osb.gbo.overheid.nl/xsd/2009/02/compliancevoorziening-v2"><ns2:= dataUit>ABC</ns2:dataUit></ns2:toUpperCaseResponse></S:Bo= dy></S:Envelope> wus.cv.prod.osb.overheid.nl:80 127.0.0.1:51798 HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Set-Cookie: JSESSIONID=3DA16EDFE6DCC0D2A9BC4AAA275E3692B1; Path=3D/ictu-ocv= wus-ws Content-Type: text/xml;charset=3Dutf-8 Date: Sat, 09 Nov 2013 10:15:28 GMT Content-Length: 1105 This configuration file is used to test the WS-I= sample applications running on a single system. <?xml version=3D'1.0' encoding=3D&apos= ;UTF-8'?><soapenv:Envelope xmlns:soapenv=3D"http://schemas.= xmlsoap.org/soap/envelope/"><soapenv:Header xmlns:wsa=3D"ht= tp://www.w3.org/2005/08/addressing"><wsa:To>http://localhost:= 4041/ictu-ocvwus-ws/OSB2W-be</wsa:To><wsa:ReplyTo><wsa:Addre= ss>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address><= ;/wsa:ReplyTo><wsa:From><wsa:Address>http://www.w3.org/2005/= 08/addressing/anonymous</wsa:Address></wsa:From><wsa:Message= ID>urn:uuid:f5cf038d-2dcd-422b-8f46-197bcfc06426@gm.messagedesign.nl<= /wsa:MessageID><wsa:Action>http://service.compliance.osb.gbo.overh= eid.nl/wsdl/2009/02/compliancevoorziening-v2/IOSB2ComplianceService/toUpper= CaseRequest</wsa:Action></soapenv:Header><soapenv:Body>&l= t;tns:toUpperCase xmlns:tns=3D"http://service.compliance.osb.gbo.overh= eid.nl/200706/osb-compliancevoorziening.xsd"><tns:data>abc<= ;/tns:data></tns:toUpperCase></soapenv:Body></soapenv:Env= elope> 127.0.0.1:51798 wus.cv.prod.osb.overheid.nl:80 POST /ictu-ocvwus-ws/OSB2W-be HTTP/1.1 Content-Type: text/xml; charset=3DUTF-8 SOAPAction: "http://service.compliance.osb.gbo.overheid.nl/wsdl/2009/0= 2/compliancevoorziening-v2/IOSB2ComplianceService/toUpperCaseRequest"&= #xd; User-Agent: Axis2 Host: localhost:4041 Content-Length: 900 The envelope does not conform to th= e structure specified in SOAP 1.1 Section 4 The header entry wsa:To is not namesp= ace-qualified =20 Element Location: lineNumber=3D34 <?xml version=3D'1.0' encoding=3D&apos= ;UTF-8'?><S:Envelope xmlns:S=3D"http://schemas.xmlsoap.org/= soap/envelope/"><S:Header><To xmlns=3D"http://www.w3.= org/2005/08/addressing">http://www.w3.org/2005/08/addressing/anonym= ous</To><Action xmlns=3D"http://www.w3.org/2005/08/addressing= ">http://service.compliance.osb.gbo.overheid.nl/wsdl/2009/02/compli= ancevoorziening-v2/IOSB2ComplianceService/toUpperCaseResponse</Action>= ;<MessageID xmlns=3D"http://www.w3.org/2005/08/addressing">= uuid:b89b2f69-362f-475c-83ad-2b6fd000931b</MessageID><RelatesTo xm= lns=3D"http://www.w3.org/2005/08/addressing">urn:uuid:f5cf038d= -2dcd-422b-8f46-197bcfc06426@gm.messagedesign.nl</RelatesTo></S:He= ader><S:Body><ns2:toUpperCaseResponse xmlns=3D"http://www.= logius.nl/digikoppeling/gb/2010/10" xmlns:ns2=3D"http://service.c= ompliance.osb.gbo.overheid.nl/200706/osb-compliancevoorziening.xsd" xm= lns:ns3=3D"http://service.compliance.osb.gbo.overheid.nl/xsd/2012/03/c= ompliancevoorziening-v2_2" xmlns:ns4=3D"http://service.compliance= .osb.gbo.overheid.nl/xsd/2009/02/compliancevoorziening-v2"><ns2:= dataUit>ABC</ns2:dataUit></ns2:toUpperCaseResponse></S:Bo= dy></S:Envelope> wus.cv.prod.osb.overheid.nl:80 127.0.0.1:51798 HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Set-Cookie: JSESSIONID=3DA16EDFE6DCC0D2A9BC4AAA275E3692B1; Path=3D/ictu-ocv= wus-ws Content-Type: text/xml;charset=3Dutf-8 Date: Sat, 09 Nov 2013 10:15:28 GMT Content-Length: 1105 > The adressing module adds the addressing namespace declaration in the hea= der element, which is not allowed by BP 1.2 > -------------------------------------------------------------------------= ------------------------------------------- > > Key: AXIS2-5597 > URL: https://issues.apache.org/jira/browse/AXIS2-5597 > Project: Axis2 > Issue Type: Bug > Components: Addressing > Affects Versions: 1.6.2 > Reporter: Maarten van den Broek > > Validation of an axis2 message with an addressing header gives a BP1600 e= rror. > This issue can probably be resolved by changing line 210 > addressingNamespaceObject =3D header.declareNamespace(addressingNamesp= ace, WSA_DEFAULT_PREFIX); > in the class org.apache.axis2.handlers.addressing.AddressingOutHandler to > addressingNamespaceObject =3D envelope.declareNamespace(addressingNam= espace, WSA_DEFAULT_PREFIX); > Maybe more changes are necessary. -- This message was sent by Atlassian JIRA (v6.1#6144) --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org For additional commands, e-mail: java-dev-help@axis.apache.org