Next in thread →
Next in month →
Re: [sca-bindings] Comments on WS bindings issues 1, 3, 4
Further to my comment on https://tools.oasis-open.org/issues/browse/SCABINDINGS-1, the normative statement covering this is: [ASM50026] If a reference has a value specified for one or more target services in its @target attribute, there MUST NOT be any child <binding/> elements declared for that reference. Regards, Simon <> wrote on 04/04/2013 12:45:25: > From: Simon Holdsworth/UK/IBM@IBMGB > To: , > Date: 04/04/2013 12:45 > Subject: [sca-bindings] Comments on WS bindings issues 1, 3, 4 > Sent by: <> > > Folks, > > Some comments on the recent bindings issues: > > https://tools.oasis-open.org/issues/browse/SCABINDINGS-1 > > TEST_BWS_2002.composite specifies both @target and binding > > The latest version of the file can be seen at: > > http://tools.oasis-open.org/version-control/browse/wsvn/sca- > bindings/TestCases_BWS/BWS_2002/src/main/resources/Test_BWS_2002.composite > > This test is actually to check if the <binding> element's > @wsdlElement attribute points to a valid WSDL element. > > Assembly spec (csprd04.pdf line 392) states " If the @target > attribute is set, the reference cannot also have binding subelements." > > Given that, the test requires a <binding> element, and therefore the > reference should not have a @target attribute. > This change would not affect the outcome of the test, but could > change the reason for an implementation passing this test. > > Therefore I agree that we should make the proposed change. > > https://tools.oasis-open.org/issues/browse/SCABINDINGS-3 > > Typo in BWS_2011 <soap:address location="&ws_addr_2010;"></soap:address> > > The latest version of the file can be seen at: > > http://tools.oasis-open.org/version-control/browse/wsvn/sca- > bindings/TestCases_BWS/BWS_2011/src/main/resources/Service1InvalidService.wsdl > > This test validates the WSDL binding referred to from a <binding> > element's @wsdlElement attribute. As such the endpoint address in > the WSDL port element is not relevant to the test and could have any > syntactically valid value. The value present has the same syntax > that is used for replaceable endpoint URLs, and by convention that > ought to be &ws_add_2011; to match the test case, however that > variable is not needed or set for this testcase, so technically this > is not an error, but it does look odd. > > The simple answer is to change the text to "2011" but this change > should not affect the outcome of any execution of the testcase. > > https://tools.oasis-open.org/issues/browse/SCABINDINGS-4 > > Typo in BWS_2018 composite > > The latest version of the file can be seen at: > > http://tools.oasis-open.org/version-control/browse/wsvn/sca- > bindings/TestCases_BWS/BWS_2018/src/main/resources/Test_BWS_2018.composite > > The "TestClient" component is defined with a property: > <property name="testName">ASM_2018</property> > > This is clearly incorrect as the test is BWS_2018. However this > test is a negative test with invalid SCDL syntax, which means that > error is caught before the test client is executed, so the test name > attribute (and indeed the test client component) are irrelevant to > the test. Changing this should not affect the outcome of any > execution of this test case, but this ought to be fixed if we have > the opportunity. > > Regards, Simon > > Unless stated otherwise above: > IBM United Kingdom Limited - Registered in England and Wales with > number 741598. > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Next in thread →
Next in month →