SCA JMS Binding v1.1 TestCases Version 1.0
Committee Specification Draft 01
8 November 2010
http://docs.oasis-open.org/opencsa/sca-bindings/sca-jmsbinding-1.1-testcases-1.0-csd01.html
http://docs.oasis-open.org/opencsa/sca-bindings/sca-jmsbinding-1.1-testcases-1.0-csd01.odt
http://docs.oasis-open.org/opencsa/sca-bindings/sca-jmsbinding-1.1-testcases-1.0-csd01.pdf (Authoritative)
N/A
http://docs.oasis-open.org/opencsa/sca-bindings/sca-jmsbinding-1.1-testcases-1.0.html
http://docs.oasis-open.org/opencsa/sca-bindings/sca-jmsbinding-1.1-testcases-1.0.odt
http://docs.oasis-open.org/opencsa/sca-bindings/sca-jmsbinding-1.1-testcases-1.0.pdf (Authoritative)
OASIS Service Component Architecture / Bindings (SCA-Bindings) TC
Simon Holdsworth, IBM <simon_holdsworth@uk.ibm.com>
Anthony Elder, IBM <ant.elder@uk.ibm.com>
Simon Holdsworth, IBM <simon_holdsworth@uk.ibm.com>
Anish Karmarkar, Oracle <Anish.Karmarkar@oracle.com>
This specification is related to:
This document defines the TestCases for the SCA JMS Binding specification.
The TestCases represent a series of tests that an SCA runtime must pass in order to claim conformance to the requirements of the SCA JMS Binding specification.
This document was last revised or approved by the OASIS Service Component Architecture / Binding (SCA-Bindings) TC on the above date. The level of approval is also listed above. Check the "Latest Version" or "Latest Approved Version" location noted above for possible later revisions of this document.
Technical Committee members should send comments on this specification to the Technical Committee’s email list. Others should send comments to the Technical Committee by using the “Send A Comment” button on the Technical Committee’s web page at http://www.oasis-open.org/committees/sca-bindings/.
For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (http://www.oasis-open.org/committees/sca-bindings/ipr.php).
When referencing this specification the following citation format should be used:
SCA-JMSBINDING-TESTCASES-1.0 OASIS Committee Specification Draft 01, SCA JMS Binding v1.1 TestCases Version 1.0, November 2010, http://docs.oasis-open.org/opencsa/sca-bindings/sca-jmsbinding-1.1-testcases-1.0-csd01.pdf
Notices
Copyright © OASIS® 2010. All Rights Reserved.
All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.
This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.
OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.
OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.
The names "OASIS", “SCA” and “Service Component Architecture” are trademarks of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see http://www.oasis-open.org/who/trademark.php for above guidance.
Table of Contents
1 Introduction 5
1.1 TestCase Structure 5
1.2 Namespaces and Java Package Names 6
1.3 Terminology 7
1.4 Normative References 7
1.5 Non-normative References 7
2 TestCases 8
2.1 Section 3 8
3 Cross Mapping of Test Assertions to TestCases 38
4 Catalog of Test Artifacts 41
4.1 Composite Files - lower level 41
4.2 Java Interfaces 41
4.3 Java Implementation Classes 42
4.4 WSDL Interface Files 42
5 Conformance 44
Appendix A.Acknowledgments 45
Appendix B.Revision History 46
This document defines the TestCases for the SCA JMS Binding specification.
The tests described in this document are related to the Test Assertions described in the SCA JMS Binding Test assertions document [JMS-TA].
The SCA JMS Binding testcases follow a standard structure. They are divided into two main parts:
JMS Test Client, which drives the test and checks that the results are as expected
SCA Test Application which consists of SCA Composites, WSDL files, XSDs and code artifacts such as Java classes, organized into a series of SCA contributions
The basic idea is that the SCA Test Application runs on the SCA runtime that is under test, while the JMS Test Client runs as a standalone application, invoking and being invoked by the Test Application through one or more service interfaces.
The JMS Test Client is designed as a standalone Java application. The version built here is a Java application which uses the JUnit test framework.
The JMS Test Client is structured to contain configuration information about the testcase, which consists of:
metadata identifying the SCA Test Application in terms of the SCA Contributions that are used and the Composites that must be deployed and run
data indicating which service operation(s) must be invoked with input data and expected output data (including exceptions for expected failure cases)
The JMS Test Client consists of a base runtime class, BaseJMSTestCase.java. Each actual testcase is implemented by a small class which extends the base runtime class. The bulk of the code required to run a test is held in the base runtime class. The small testcase class contains the configuration for the specific test, which it provides to the code in the base runtime class through a standard interface.
The JMS Test Client base runtime class is structured so that there is a replaceable class called the RuntimeBridge, which is used to communicate with the SCA runtime under test, for the purposes of deploying and running the test application. Each SCA runtime provider can produce a version of this class. The code within the runtime bridge is likely to be highly proprietary and specific to the SCA runtime for which it is written. Which runtime bridge class is used at runtime is controlled by an environment variable or system variable with the name "OASIS_TESTENV_RUNTIME_BRIDGE_CLASS", which is read by the code in BaseJMSTestCase.
The JMS Test Client uses JMS to communicate with the SCA Test Application. Tests involve SCA services and references with JMS bindings, and possibly with bidirectional interfaces. Each SCA Test Application consists of one top level SCA Composite file and its associated artifacts (implementations, interface files), plus the JMS Test Client described above.
A typical test application has a design where the top level composite offers a single service to the JMS Test Client application over a JMS binding. The top level composite contains one component which offers the service that is used by the client application, and may have a single reference which invokes the JMS Test Client.
Note that the design of these testcases promotes reuse of artifacts between testcases, so that many testcases share components. For example, components implementing simple invokable services are all implemented using a single parameterized implementation artifact.
All the test artifacts are contained in a number of Contributions, which are simply filesystem directories which are all peers in the filesystem hierarchy. The names of the directories are the names of the Contributions and the names are significant. The names of Contributions containing implementation type specific artifacts (such as Java classes) are also specially structured to allow for replacement of one type of implementation artifact with another.
Broadly, Contribution names are as follows:
BJM_nnnnn - a contribution that is specific for a particular testcase, where "nnnnn" is the number of the testcase. Often this is required because a particular testcase involves artifacts that contain errors that are statically checkable - an SCA runtime is permitted to reject such artifacts when they are contributed and deployed and it is important to ensure that contributions containing deliberate errors for one testcase do not interfere with the operation of other testcases.
BJM_nnnnn_Java - a contribution for a specific testcase where there is a need for language specific artifacts that relate to that testcase alone
General - a shared contribution containing implementation type independent artifacts that can be used by many testcases.
General_Java - a shared contribution containing implementation type dependent artifacts for Java POJOs. These artifacts can include both Java classes and also SCA composites that directly use Java classes..
Contribution1, Contribution2, etc - contributions that are used by various testcases that are testing the handling of SCA contributions
The SCA JMS Binding testcase suite makes use of some XML namespaces and Java package names, as follows:
These apply to artifacts such as Composites
http://docs.oasis-open.org/ns/opencsa/scatests/200903
http://test.sca.oasisopen.org/
For Java interface classes and for Java implementation classes
org.oasisopen.sca.test
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this specification are to be interpreted as described in IETF RFC 2119 [RFC 2119].
[RFC
2119] S. Bradner. Key words for use in RFCs to Indicate
Requirement Levels. IETF RFC 2119, March 1997.
http://www.ietf.org/rfc/rfc2119.txt
[JMS-TA] OASIS Committee Specification Draft 01, SCA JMS Binding Test Assertions, November 2010 http://docs.oasis-open.org/opencsa/sca-bindings/sca-jmsbinding-1.1-test-assertions-1.0-csd01.pdf
N/A
Testcase ID |
BJM_30001_TestCase |
Test Assertion |
BJM-TA-30001 |
Description |
Tests that the @uri attribute of a <binding.jms> element matches the syntax defined by the IETF URI Scheme for Java™ Message Service 1.0 |
Artifacts |
BJM_30001_TestCase.java Test_BJM_30001.composite TestInvocation.wsdl Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30002_1_TestCase |
Test Assertion |
BJM-TA-30002 |
Description |
Tests that when the @uri attribute is specified, the SCA runtime MUST raise an error if the referenced resources do not already exist This is the test for the destination does not exist |
Artifacts |
BJM_30002_1_TestCase.java Test_BJM_30002_1.composite TestInvocation.wsdl Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30002_2_TestCase |
Test Assertion |
BJM-TA-30002 |
Description |
Tests that when the @uri attribute is specified, the SCA runtime MUST raise an error if the referenced resources do not already exist This is the test for the connection factory does not exist |
Artifacts |
BJM_30002_2_TestCase.java Test_BJM_30002_2.composite TestInvocation.wsdl Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30003_TestCase |
Test Assertion |
BJM-TA-30003 |
Description |
Tests that when the @correlationScheme attribute is "sca:messageID" the SCA runtime MUST set the correlation ID of replies to the message ID of the corresponding request |
Artifacts |
BJM_3003_TestCase.java Test_BJM_3003.composite Service1.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service1 operation1 invoked with BJM_3003 request message</return>” |
Testcase ID |
BJM_30004_TestCase |
Test Assertion |
BJM-TA-30004 |
Description |
Tests that the correlation ID of a reply message is set to the value of the correlation ID of the corresponding request message when a request/reply operation is invoked. |
Artifacts |
BJM_3004_TestCase.java Test_BJM_3004.composite Service1.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service1 operation1 invoked with BJM_3004 request message</return>” |
Testcase ID |
BJM_30005_TestCase |
Test Assertion |
BJM-TA-30005 |
Description |
Tests that if the value of the @correlationScheme attribute is "sca:none" the SCA runtime MUST NOT set the correlation ID |
Artifacts |
BJM_3005_TestCase.java Test_BJM_3005.composite Service1.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service1 operation1 invoked with BJM_3005 request message</return>” |
Testcase ID |
BJM_30007_TestCase |
Test Assertion |
BJM-TA-30007 |
Description |
Tests that the correlation ID of request messages are set to a non-null value when using the sca:correlationID correlation scheme on a reference. |
Artifacts |
BJM_3007_TestCase.java Test_BJM_3007.composite |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service1 operation1 invoked with BJM_3007 request message</return>” |
Testcase ID |
BJM_30011A_TestCase |
Test Assertion |
BJM-TA-30011 |
Description |
Tests when the @create attribute value for a destination, connectionFactory or activationSpec element is "always" and the @jndiName attribute is present and the resource cannot be created at the location specified by the @jndiName attribute then the SCA runtime MUST raise an error This test is for the activationSpec |
Artifacts |
BJM_3011A_TestCase.java Test_BJM_3011A.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30011C_TestCase |
Test Assertion |
BJM-TA-30011 |
Description |
Tests when the @create attribute value for a destination, connectionFactory or activationSpec element is "always" and the @jndiName attribute is present and the resource cannot be created at the location specified by the @jndiName attribute then the SCA runtime MUST raise an error This test is for the connectionFactory |
Artifacts |
BJM_3011C_TestCase.java Test_BJM_3011C.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30011D_TestCase |
Test Assertion |
BJM-TA-30011 |
Description |
Tests when the @create attribute value for a destination, connectionFactory or activationSpec element is "always" and the @jndiName attribute is present and the resource cannot be created at the location specified by the @jndiName attribute then the SCA runtime MUST raise an error This test is for the destination |
Artifacts |
BJM_3011D_TestCase.java Test_BJM_3011D.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30012A_TestCase |
Test Assertion |
BJM-TA-30012 |
Description |
Tests when the @create attribute value for a destination, connectionFactory or activationSpec element is "ifNotExist" then the @jndiName attribute MUST specify the location of the possibly existing resource This test is for the activationSpec |
Artifacts |
BJM_3012A_TestCase.java Test_BJM_3012A.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30012C_TestCase |
Test Assertion |
BJM-TA-30012 |
Description |
Tests when the @create attribute value for a destination, connectionFactory or activationSpec element is "ifNotExist" then the @jndiName attribute MUST specify the location of the possibly existing resource This test is for the connectionFactory |
Artifacts |
BJM_3012C_TestCase.java Test_BJM_3012C.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30012D_TestCase |
Test Assertion |
BJM-TA-30012 |
Description |
Tests when the @create attribute value for a destination, connectionFactory or activationSpec element is "ifNotExist" then the @jndiName attribute MUST specify the location of the possibly existing resource This test is for the destination |
Artifacts |
BJM_3012D_TestCase.java Test_BJM_3012D.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30014A_TestCase |
Test Assertion |
BJM-TA-30014 |
Description |
Tests when the @create attribute value for a destination, connectionFactory or activationSpec element is "ifNotExist" and the @jndiName attribute refers to an existing resource that is not a JMS Destination of the approprate type, a JMS connection factory or a JMS activation spec respectively then the SCA runtime MUST raise an error This test is for the activationSpec |
Artifacts |
BJM_3014A_TestCase.java Test_BJM_3014A.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30014C_TestCase |
Test Assertion |
BJM-TA-30014 |
Description |
Tests when the @create attribute value for a destination, connectionFactory or activationSpec element is "ifNotExist" and the @jndiName attribute refers to an existing resource that is not a JMS Destination of the approprate type, a JMS connection factory or a JMS activation spec respectively then the SCA runtime MUST raise an error This test is for the connectionFactory |
Artifacts |
BJM_3014C_TestCase.java Test_BJM_3014C.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30014D_TestCase |
Test Assertion |
BJM-TA-30014 |
Description |
Tests when the @create attribute value for a destination, connectionFactory or activationSpec element is "ifNotExist" and the @jndiName attribute refers to an existing resource that is not a JMS Destination of the approprate type, a JMS connection factory or a JMS activation spec respectively then the SCA runtime MUST raise an error This test is for the destination |
Artifacts |
BJM_3014D_TestCase.java Test_BJM_3014D.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30015Aa_TestCase |
Test Assertion |
BJM-TA-30015 |
Description |
Tests when the @create attribute value for a destination, connectionFactory or activationSpec element is "never" and the @jndiName attribute is not specified, or the resource is not present at the location identified by the @jndiName attribute, or the location refers to a resource of an incorrect type then the SCA runtime MUST raise an error This test is for activationspec and no @jndiName |
Artifacts |
BJM_3015Aa_TestCase.java Test_BJM_30145Aa.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30015Ab_TestCase |
Test Assertion |
BJM-TA-30015 |
Description |
Tests when the @create attribute value for a destination, connectionFactory or activationSpec element is "never" and the @jndiName attribute is not specified, or the resource is not present at the location identified by the @jndiName attribute, or the location refers to a resource of an incorrect type then the SCA runtime MUST raise an error This test is for activationspec and resource not present |
Artifacts |
BJM_3015Ab_TestCase.java Test_BJM_30145Ab.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30015Ac_TestCase |
Test Assertion |
BJM-TA-30015 |
Description |
Tests when the @create attribute value for a destination, connectionFactory or activationSpec element is "never" and the @jndiName attribute is not specified, or the resource is not present at the location identified by the @jndiName attribute, or the location refers to a resource of an incorrect type then the SCA runtime MUST raise an error This test is for activationspec and resource wrong type |
Artifacts |
BJM_3015Ac_TestCase.java Test_BJM_30145Ac.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30015Ca_TestCase |
Test Assertion |
BJM-TA-30015 |
Description |
Tests when the @create attribute value for a destination, connectionFactory or activationSpec element is "never" and the @jndiName attribute is not specified, or the resource is not present at the location identified by the @jndiName attribute, or the location refers to a resource of an incorrect type then the SCA runtime MUST raise an error This test is for connectionFactory and no @jndiName |
Artifacts |
BJM_3015Ca_TestCase.java Test_BJM_30145Ca.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30015Cb_TestCase |
Test Assertion |
BJM-TA-30015 |
Description |
Tests when the @create attribute value for a destination, connectionFactory or activationSpec element is "never" and the @jndiName attribute is not specified, or the resource is not present at the location identified by the @jndiName attribute, or the location refers to a resource of an incorrect type then the SCA runtime MUST raise an error This test is for connectionFactory and resource not present |
Artifacts |
BJM_3015Cb_TestCase.java Test_BJM_30145Cb.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30015Cc_TestCase |
Test Assertion |
BJM-TA-30015 |
Description |
Tests when the @create attribute value for a destination, connectionFactory or activationSpec element is "never" and the @jndiName attribute is not specified, or the resource is not present at the location identified by the @jndiName attribute, or the location refers to a resource of an incorrect type then the SCA runtime MUST raise an error This test is for connectionFactory and resource wrong type |
Artifacts |
BJM_3015Cc_TestCase.java Test_BJM_30145Cc.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30015Da_TestCase |
Test Assertion |
BJM-TA-30015 |
Description |
Tests when the @create attribute value for a destination, connectionFactory or activationSpec element is "never" and the @jndiName attribute is not specified, or the resource is not present at the location identified by the @jndiName attribute, or the location refers to a resource of an incorrect type then the SCA runtime MUST raise an error This test is for destination and no @jndiName |
Artifacts |
BJM_3015Da_TestCase.java Test_BJM_30145Da.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30015Db_TestCase |
Test Assertion |
BJM-TA-30015 |
Description |
Tests when the @create attribute value for a destination, connectionFactory or activationSpec element is "never" and the @jndiName attribute is not specified, or the resource is not present at the location identified by the @jndiName attribute, or the location refers to a resource of an incorrect type then the SCA runtime MUST raise an error This test is for destination and resource not present |
Artifacts |
BJM_3015Db_TestCase.java Test_BJM_30145Db.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30015Dc_TestCase |
Test Assertion |
BJM-TA-30015 |
Description |
Tests when the @create attribute value for a destination, connectionFactory or activationSpec element is "never" and the @jndiName attribute is not specified, or the resource is not present at the location identified by the @jndiName attribute, or the location refers to a resource of an incorrect type then the SCA runtime MUST raise an error This test is for destination and resource wrong type |
Artifacts |
BJM_3015Dc_TestCase.java Test_BJM_3015Dc.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30017_TestCase |
Test Assertion |
BJM-TA-30017 |
Description |
Tests that a binding.jms element MUST NOT include both a connectionFactory element and an activationSpec element |
Artifacts |
BJM_3017_TestCase.java Test_BJM_3017.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30018_TestCase |
Test Assertion |
BJM-TA-30018 |
Description |
Tests when the connectionFactory element is present, then the destination MUST be defined either by the destination element or the @uri attribute |
Artifacts |
BJM_3018_TestCase.java Test_BJM_3018.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30020_TestCase |
Test Assertion |
BJM-TA-30020 |
Description |
Tests that the activationSpec element MUST NOT be present when the binding is being used for an SCA reference |
Artifacts |
BJM_3020_TestCase.java Test_BJM_3020.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30021_TestCase |
Test Assertion |
BJM-TA-30021 |
Description |
Tests that a response element MUST NOT include both a connectionFactory element and an activationSpec element |
Artifacts |
BJM_3021_TestCase.java Test_BJM_3021.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30023_TestCase |
Test Assertion |
BJM-TA-30023 |
Description |
Tests that the response/activationSpec element MUST NOT be present when the binding is being used for an SCA service |
Artifacts |
BJM_3023_TestCase.java Test_BJM_3023.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30024_1_TestCase |
Test Assertion |
BJM-TA-30024 |
Description |
Tests when sending messages for a JMS binding, the SCA runtime MUST set each of the JMSType, JMSDeliveryMode, JMSTimeToLive and JMSPriority headers to values specified in the binding definition in the following priority order: 1) the value for the header specified in the @uri attribute (highest priority); 2) the value for the header specified in the operationProperties/headers element matching the operation being invoked; 3) the value for the header specified in the headers element; 4) the default value for the header as specified by the definition of the binding.jms/headers element (lowest priority) This is the URI case |
Artifacts |
BJM_3024_1_TestCase.java Test_BJM_3024_1.composite Service1.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><arg0>service1 operation1 invoked with BJM_3024 request message</arg0>” |
Testcase ID |
BJM_30024_2_TestCase |
Test Assertion |
BJM-TA-30024 |
Description |
Tests when sending messages for a JMS binding, the SCA runtime MUST set each of the JMSType, JMSDeliveryMode, JMSTimeToLive and JMSPriority headers to values specified in the binding definition in the following priority order: 1) the value for the header specified in the @uri attribute (highest priority); 2) the value for the header specified in the operationProperties/headers element matching the operation being invoked; 3) the value for the header specified in the headers element; 4) the default value for the header as specified by the definition of the binding.jms/headers element (lowest priority) This is the operationProperties case |
Artifacts |
BJM_3024_2_TestCase.java Test_BJM_3024_2.composite Service1.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><arg0>service1 operation1 invoked with BJM_3024 request message</arg0>” |
Testcase ID |
BJM_30024_3_TestCase |
Test Assertion |
BJM-TA-30024 |
Description |
Tests when sending messages for a JMS binding, the SCA runtime MUST set each of the JMSType, JMSDeliveryMode, JMSTimeToLive and JMSPriority headers to values specified in the binding definition in the following priority order: 1) the value for the header specified in the @uri attribute (highest priority); 2) the value for the header specified in the operationProperties/headers element matching the operation being invoked; 3) the value for the header specified in the headers element; 4) the default value for the header as specified by the definition of the binding.jms/headers element (lowest priority) This is the header case |
Artifacts |
BJM_3024_3_TestCase.java Test_BJM_3024_3.composite Service1.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><arg0>service1 operation1 invoked with BJM_3024 request message</arg0>” |
Testcase ID |
BJM_30024_4_TestCase |
Test Assertion |
BJM-TA-30024 |
Description |
Tests when sending messages for a JMS binding, the SCA runtime MUST set each of the JMSType, JMSDeliveryMode, JMSTimeToLive and JMSPriority headers to values specified in the binding definition in the following priority order: 1) the value for the header specified in the @uri attribute (highest priority); 2) the value for the header specified in the operationProperties/headers element matching the operation being invoked; 3) the value for the header specified in the headers element; 4) the default value for the header as specified by the definition of the binding.jms/headers element (lowest priority) This is the default case |
Artifacts |
BJM_3024_4_TestCase.java Test_BJM_3024_4.composite Service1.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><arg0>service1 operation1 invoked with BJM_3024 request message</arg0>” |
Testcase ID |
BJM_30025_1_TestCase |
Test Assertion |
BJM-TA-30025 |
Description |
Tests when sending messages for a JMS binding, the SCA runtime MUST set each named user property with type and value specified in the binding definition in the following priority order: 1) the type and value for the named user property specified in an operationProperties/headers/property element matching the name of the operation being invoked (highest priority); 2) the type and value for the named user property specified in a headers/property element (lowest priority) This is the operationProperties case |
Artifacts |
BJM_3025_1_TestCase.java Test_BJM_3025_1.composite Service1.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><arg0>service1 operation1 invoked with BJM_3025 request message</arg0>” |
Testcase ID |
BJM_30025_2_TestCase |
Test Assertion |
BJM-TA-30025 |
Description |
Tests when sending messages for a JMS binding, the SCA runtime MUST set each named user property with type and value specified in the binding definition in the following priority order: 1) the type and value for the named user property specified in an operationProperties/headers/property element matching the name of the operation being invoked (highest priority); 2) the type and value for the named user property specified in a headers/property element (lowest priority) This is the headers case |
Artifacts |
BJM_3025_2_TestCase.java Test_BJM_3025_2.composite Service1.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><arg0>service1 operation1 invoked with BJM_3025 request message</arg0>” |
Testcase ID |
BJM_30026_1_TestCase |
Test Assertion |
BJM-TA-30026 |
Description |
Tests when receiving messages for a JMS binding, the SCA runtime MUST use a message selector if specified in the binding definition in the following priority order: 1) the value for the message selector specified in the @uri attribute value's "selector" parameter (highest priority); 2) the value for the message selector specified in the messageSelection/@selector attribute; 3) otherwise no message selector is used (lowest priority) This is the @uri case |
Artifacts |
BJM_3026_1_TestCase.java Test_BJM_3026_1.composite Service1.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service1 operation1 invoked with BJM_3026 type1 message</return>” |
Testcase ID |
BJM_30026_2_TestCase |
Test Assertion |
BJM-TA-30026 |
Description |
Tests when receiving messages for a JMS binding, the SCA runtime MUST use a message selector if specified in the binding definition in the following priority order: 1) the value for the message selector specified in the @uri attribute value's "selector" parameter (highest priority); 2) the value for the message selector specified in the messageSelection/@selector attribute; 3) otherwise no message selector is used (lowest priority) This is the messageSelection case |
Artifacts |
BJM_3026_2_TestCase.java Test_BJM_3026_2.composite Service1.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service1 operation1 invoked with BJM_3026 type1 message</return>” |
Testcase ID |
BJM_30026_3_TestCase |
Test Assertion |
BJM-TA-30026 |
Description |
Tests when receiving messages for a JMS binding, the SCA runtime MUST use a message selector if specified in the binding definition in the following priority order: 1) the value for the message selector specified in the @uri attribute value's "selector" parameter (highest priority); 2) the value for the message selector specified in the messageSelection/@selector attribute; 3) otherwise no message selector is used (lowest priority) This is the default case |
Artifacts |
BJM_3026_3_TestCase.java Test_BJM_3026_3.composite Service1.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service1 operation1 invoked with BJM_3026 request message</return>” |
Testcase ID |
BJM_30029_TestCase |
Test Assertion |
BJM-TA-30029 |
Description |
Tests that the value of the operationProperties/@selectedOperation attribute MUST be unique across the containing binding.jms element |
Artifacts |
BJM_3029_TestCase.java Test_BJM_3029.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30031_TestCase |
Test Assertion |
BJM-TA-30031 |
Description |
Tests that the resourceAdapter element MUST be present when JMS resources are to be created for a JMS provider that implements the JCA 1.5 Specification [JCA15] specification, and is ignored otherwise |
Artifacts |
BJM_3031_TestCase.java Test_BJM_3031.composite Service1.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service1 operation1 invoked with BJM_3031 request message</return>” |
Testcase ID |
BJM_30034_TestCase |
Test Assertion |
BJM-TA-30034 |
Description |
Tests when the @uri attribute is specified, the destination element MUST NOT be present |
Artifacts |
BJM_3034_TestCase.java Test_BJM_3034.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_30036_TestCase |
Test Assertion |
BJM-TA-30036 |
Description |
Tests that the binding.jms element MUST conform to the XML schema defined in sca-bindingjms-1.1.xsd |
Artifacts |
BJM_3036_TestCase.java Test_BJM_3036.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_40001D_TestCase |
Test Assertion |
BJM-TA-40001 |
Description |
Tests The SCA runtime MUST support the default JMS wire format and operation selector behavior, and MAY provide additional means to override it |
Artifacts |
BJM_4001_TestCase.java Test_BJM_4001.composite Service1.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service1 operation1 invoked with BJM_4001 request message</return>” |
Testcase ID |
BJM_40002_1_TestCase |
Test Assertion |
BJM-TA-40002 |
Description |
Tests if operationSelector.jmsDefault is used if no operationSelector element is specified This tests if there is only one operation on the service's interface, then that operation is the selected operation name |
Artifacts |
BJM_4002_TestCase.java Test_BJM_4002.composite TestComposite21.composite Service1.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service1 operation1 invoked with BJM_4002_1 request message</return>” |
Testcase ID |
BJM_40002_2_TestCase |
Test Assertion |
BJM-TA-40002 |
Description |
Tests if operationSelector.jmsDefault is used if no operationSelector element is specified This tests when more than one operation in the interface; the JMS user property "scaOperationName" is present and the value of that user property is used as the selected operation name |
Artifacts |
BJM_4002__2_TestCase.java Test_BJM_4002.composite TestComposite21.composite Service2.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service2 operation2 invoked with BJM_4002_2 request message</return>” |
Testcase ID |
BJM_40002_3_TestCase |
Test Assertion |
BJM-TA-40002 |
Description |
Tests if operationSelector.jmsDefault is used if no operationSelector element is specified This tests when more than one operation in the interface; no scaOperationName user property; the message is a JMS text or bytes message containing XML, and the selected operation name is the local name of the root element of the XML payload. |
Artifacts |
BJM_4002_3_TestCase.java Test_BJM_4002.composite TestComposite21.composite Service2.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service2 operation2 invoked with BJM_4002 request message</return>” |
Testcase ID |
BJM_40002_4_TestCase |
Test Assertion |
BJM-TA-40002 |
Description |
Tests if operationSelector.jmsDefault is used if no operationSelector element is specified This tests when more than one operation in the interface; no scaOperationName user property; no top-level XML element in the message body matching an operation name; the selected operation name is "onMessage” |
Artifacts |
BJM_4002_4_TestCase.java Test_BJM_4002.composite TestComposite21.composite Service5.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service5 onMessage invoked with BJM_4002_4 request message</return>” |
Testcase ID |
BJM_40003_TestCase |
Test Assertion |
BJM-TA-40003 |
Description |
Tests when using the default wire format to send request messages, if there is a single parameter and the interface includes more than one operation, the SCA runtime MUST set the JMS user property "scaOperationName" to the name of the operation being invoked |
Artifacts |
BJM_4003_TestCase.java Test_BJM_4003.composite |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>Service2Impl2.operation1 service1 operation1 invoked with BJM_4003 request message</return>” |
Testcase ID |
BJM_40004_TestCase |
Test Assertion |
BJM-TA-40004 |
Description |
Tests if no wireFormat element is specified in a JMS binding then SCA runtimes MUST use wireFormat.jmsDefault as the default |
Artifacts |
BJM_4004_TestCase.java Test_BJM_4004.composite TestComposite1.composite Service1.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_40004_2_TestCase |
Test Assertion |
BJM-TA-40004 |
Description |
Tests if no wireFormat element is specified in a JMS binding then SCA runtimes MUST use wireFormat.jmsDefault as the default |
Artifacts |
BJM_4004_2_TestCase.java Test_BJM_4004.composite TestComposite1.composite Service1.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service1 operation1 invoked with BJM_4004 request message</return>” |
Testcase ID |
BJM_40005T_TestCase |
Test Assertion |
BJM-TA-40005 |
Description |
Tests When using the default wire format an SCA runtime MUST be able to receive both JMS text and bytes messages This is the Text message test |
Artifacts |
BJM_4005T_TestCase.java Test_BJM_4005.composite TestComposite1.composite Service1.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service1 operation1 invoked with BJM_4005 request message</return>” |
Testcase ID |
BJM_40005B_TestCase |
Test Assertion |
BJM-TA-40005 |
Description |
Tests When using the default wire format an SCA runtime MUST be able to receive both JMS text and bytes messages This is the Bytes message test |
Artifacts |
BJM_4005B_TestCase.java Test_BJM_4005.composite TestComposite1.composite Service1.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service1 operation1 invoked with BJM_4005 request message</return>” |
Testcase ID |
BJM_40006_TestCase |
Test Assertion |
BJM-TA-40006 |
Description |
Tests when using the default wire format an SCA runtime MUST send either a JMS text or a JMS bytes message |
Artifacts |
BJM_4006_TestCase.java Test_BJM_4006.composite TestComposite34.composite Service3.wsdl |
Expected output |
Positive test: “Reply message is BytesMessage or TextMessage” |
Testcase ID |
BJM_40008_TestCase |
Test Assertion |
BJM-TA-40008 |
Description |
Tests when a binding.jms element specifies the operationSelector.jmsDefault element, the SCA runtime MUST use the default operation selection algorithm to determine the selected operation |
Artifacts |
BJM_4008_TestCase.java Test_BJM_4008.composite TestComposite21.composite Service2.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service2 operation2 invoked with BJM_4008 request message</return>” |
Testcase ID |
BJM_40009_TestCase |
Test Assertion |
BJM-TA-40009 |
Description |
Tests when a binding.jms element specifies the wireFormat.jmsDefault element, the SCA runtime MUST use the default wire format |
Artifacts |
BJM_4009_TestCase.java Test_BJM_4009.composite TestComposite1.composite Service1.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service1 operation1 invoked with BJM_4009 request message</return>” |
Testcase ID |
BJM_40010_TestCase |
Test Assertion |
BJM-TA-40010 |
Description |
Tests when a message is received at an SCA service with JMS binding and the resolved operation name is in the target component's interface, the SCA runtime MUST invoke the target component using the resolved operation name |
Artifacts |
BJM_4010_TestCase.java Test_BJM_4010.composite TestComposite21.composite Service2.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service2 operation2 invoked with BJM_4010 request message</return>” |
Testcase ID |
BJM_40011_TestCase |
Test Assertion |
BJM-TA-40011 |
Description |
Tests when a message is received at an SCA service with JMS binding and the resolved operation name is not in the target component's interface the SCA runtime MUST raise an error |
Artifacts |
BJM_4011_TestCase.java Test_BJM_4011.composite TestComposite21.composite Service2.wsdl |
Expected output |
Negative test: “exception” |
Testcase ID |
BJM_50001_TestCase |
Test Assertion |
BJM-TA-50001 |
Description |
Tests that the JMS binding implementations MUST support the JMS intent |
Artifacts |
BJM_5001_TestCase.java Test_BJM_5001.composite TestComposite1.composite Service1.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service1 operation1 invoked with BJM_5001 request message</return>” |
Testcase ID |
BJM_60002_TestCase |
Test Assertion |
BJM-TA-60002 |
Description |
Tests that for an SCA service with a JMS binding and unidirectional interface, when a request message is received as part of a one-way MEP, the SCA runtime MUST ignore the JMSReplyTo destination header in the JMS message, and not raise an error |
Artifacts |
BJM_6002_TestCase.java Test_BJM_6002.composite TestComposite34.composite Service3.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><arg0>service3 operation1 invoked with BJM_6002 request message</arg0>” |
Testcase ID |
BJM_60003_1_TestCase |
Test Assertion |
BJM-TA-60003 |
Description |
Tests that for an SCA reference with a JMS binding that has a destination specified via the response element, the SCA runtime MUST receive response messages as defined by the binding's @correlationScheme attribute. This is the test for the messageID correlation scheme |
Artifacts |
BJM_6003_1_TestCase.java Test_BJM_6003.composite Service1.wsdl TestComposite1.composite TestInvocation.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service1 operation1 invoked service1 operation1 invoked with BJM_6003_1 request message</return>” |
Testcase ID |
BJM_60003_2_TestCase |
Test Assertion |
BJM-TA-60003 |
Description |
Tests that for an SCA reference with a JMS binding that has a destination specified via the response element, the SCA runtime MUST receive response messages as defined by the binding's @correlationScheme attribute. This is the test for the correlationID correlation scheme |
Artifacts |
BJM_6003_2_TestCase.java Test_BJM_6003.composite Service1.wsdl TestComposite1.composite TestInvocation.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service1 operation1 invoked service1 operation1 invoked with BJM_6003_2 request message</return>” |
Testcase ID |
BJM_60003_3_TestCase |
Test Assertion |
BJM-TA-60003 |
Description |
Tests that for an SCA reference with a JMS binding that has a destination specified via the response element, the SCA runtime MUST receive response messages as defined by the binding's @correlationScheme attribute. This is the test for the none correlation scheme |
Artifacts |
BJM_6003_3_TestCase.java Test_BJM_6003.composite Service1.wsdl TestComposite1.composite TestInvocation.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service1 operation1 invoked service1 operation1 invoked with BJM_6003_3 request message</return>” |
Testcase ID |
BJM_60004_TestCase |
Test Assertion |
BJM-TA-60004 |
Description |
Tests that for an SCA reference with a JMS binding, when a request message is sent as part of a request/response MEP, and the JMS binding has a response element with a destination defined, then the SCA runtime MUST use that destination for the JMSReplyTo header in the JMS message it creates for the request |
Artifacts |
BJM_6004_TestCase.java Test_BJM_6004.composite |
Expected output |
Positive test: “JMSReplyTo is as expected” |
Testcase ID |
BJM_60005_TestCase |
Test Assertion |
BJM-TA-60005 |
Description |
Tests that for an SCA reference with a JMS binding, when a request message is sent as part of a request/response MEP, and the JMS binding does not have a response element with a destination defined, the SCA runtime MUST provide an appropriate destination on which to receive response messages and use that destination for the JMSReplyTo header in the JMS message it creates for the request |
Artifacts |
BJM_6005_TestCase.java Test_BJM_6005.composite |
Expected output |
Positive test: “JMSReplyTo is set” |
Testcase ID |
BJM_60007_TestCase |
Test Assertion |
BJM-TA-60007 |
Description |
Tests that for an SCA service with a JMS binding, when a response message is sent as part of a request/response MEP where the request message included a non-null JMSReplyTo destination, the SCA runtime MUST send the response message to that destination |
Artifacts |
BJM_6007_TestCase.java Test_BJM_6007.composite Service1.wsdl TestComposite1.composite |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service1 operation1 invoked with BJM_6007 request message</return>” |
Testcase ID |
BJM_60007_2_TestCase |
Test Assertion |
BJM-TA-60007 |
Description |
Tests that for an SCA service with a JMS binding, when a response message is sent as part of a request/response MEP where the request message included a non-null JMSReplyTo destination, the SCA runtime MUST send the response message to that destination This is the case where the service binding includes a response destination, which should be ignored as the JMSReplyTo should be used. |
Artifacts |
BJM_6007_2_TestCase.java Test_BJM_6007.composite Service1.wsdl TestComposite1.composite |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service1 operation1 invoked with BJM_6007 request message</return>” |
Testcase ID |
BJM_60008_TestCase |
Test Assertion |
BJM-TA-60008 |
Description |
Tests that for an SCA service with a JMS binding, when a response message is sent as part of a request/response MEP where the request message included a null JMSReplyTo destination and the JMS binding includes a response/destination element the SCA runtime MUST send the response message to that destination |
Artifacts |
BJM_6008_TestCase.java Test_BJM_6008.composite TestComposite1.composite Service1.wsdl |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><return>service1 operation1 invoked with BJM_6008 request message</return>” |
Testcase ID |
BJM_60011_TestCase |
Test Assertion |
BJM-TA-60011 |
Description |
Tests that for an SCA reference with a JMS binding and a bidirectional interface, when a request message is sent as part of a request/response MEP the SCA runtime MUST set the scaCallbackDestination user property in the message it creates to a JMS URI string, in the format defined by the IETF URI Scheme for Java Message Service 1.0 [IETFJMS], that identifies the destination to which callback messages are to be sent |
Artifacts |
BJM_6011_TestCase.java Test_BJM_6011.composite Service3Impl3.java |
Expected output |
Positive test: “scaCallbackDestination property is a jms URI” |
Testcase ID |
BJM_60012_TestCase |
Test Assertion |
BJM-TA-60012 |
Description |
Tests that for an SCA reference with a JMS binding and bidirectional interface, when a request message is sent as part of a one-way MEP the SCA runtime MUST set the destination to which callback messages are to be sent as the JMSReplyTo destination in the message it creates |
Artifacts |
BJM_6012_TestCase.java Test_BJM_6012.composite Service3Impl4.java |
Expected output |
Positive test: “JMSReplyTo is set” |
Testcase ID |
BJM_60013_TestCase |
Test Assertion |
BJM-TA-60013 |
Description |
Tests that for an SCA reference with a JMS binding and bidirectional interface, when a request message is sent as part of a request/response MEP, the SCA runtime MUST set the JMSReplyTo header in the message it creates as described in section 6.2 |
Artifacts |
BJM_6013_TestCase.java Test_BJM_6013.composite Service3Impl3.java |
Expected output |
Positive test: “JMSReplyTo header is set” |
Testcase ID |
BJM_60013_2_TestCase |
Test Assertion |
BJM-TA-60013 |
Description |
Tests that for an SCA reference with a JMS binding and bidirectional interface, when a request message is sent as part of a request/response MEP, the SCA runtime MUST set the JMSReplyTo header in the message it creates as described in section 6.2 |
Artifacts |
BJM_6013_2_TestCase.java Test_BJM_6013_2.composite Service3Impl3.java |
Expected output |
Positive test: “JMSReplyTo header is set as expected” |
Testcase ID |
BJM_60014_1_1_TestCase |
Test Assertion |
BJM-TA-60014 |
Description |
Tests that for an SCA reference with a JMS binding and bidirectional interface, the SCA runtime MUST identify the callback destination from the reference's callback service binding if present, or supply a suitable callback destination if not present This is the test for the destination defined on the callback binding using a uri attribute |
Artifacts |
BJM_6014_1_1_TestCase.java Test_BJM_6014_1_1.composite Service3Impl3.java |
Expected output |
Positive test: “scaCallbackDestination property is a jms URI” |
Testcase ID |
BJM_60014_1_2_TestCase |
Test Assertion |
BJM-TA-60014 |
Description |
Tests that for an SCA reference with a JMS binding and bidirectional interface, the SCA runtime MUST identify the callback destination from the reference's callback service binding if present, or supply a suitable callback destination if not present This is the case where the callback destination is specified on the binding by a destination element |
Artifacts |
BJM_6014_1_2_TestCase.java Test_BJM_6014_1_2.composite Service3Impl3.java |
Expected output |
Positive test: “scaCallbackDestination property is a jms URI” |
Testcase ID |
BJM_60014_2_TestCase |
Test Assertion |
BJM-TA-60014 |
Description |
Tests that for an SCA reference with a JMS binding and bidirectional interface, the SCA runtime MUST identify the callback destination from the reference's callback service binding if present, or supply a suitable callback destination if not present This is the test for the destination defined on the callback binding using a <destination> element |
Artifacts |
BJM_6014_2_TestCase.java Test_BJM_6014_2.composite Service3Impl3.java |
Expected output |
Positive test: “scaCallbackDestination property is a jms URI” |
Testcase ID |
BJM_60015_1_TestCase |
Test Assertion |
BJM-TA-60015 |
Description |
For an SCA service with a JMS binding, when a callback request message is sent for either a one-way or request/response MEP, the SCA runtime MUST send the callback request message to the callback destination. This is test for the service callback binding identifying the callback destination |
Artifacts |
BJM_6015_1_TestCase.java Test_BJM_6015.composite Service4Impl1.java |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><arg0>onewayOperation1 callback request</arg0>” |
Testcase ID |
BJM_60015_2_TestCase |
Test Assertion |
BJM-TA-60015 |
Description |
For an SCA service with a JMS binding, when a callback request message is sent for either a one-way or request/response MEP, the SCA runtime MUST send the callback request message to the callback destination. This is test for the scaCallbackDestination property identifying the callback destination |
Artifacts |
BJM_6015_2_TestCase.java Test_BJM_6015.composite Service4Impl1.java |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><arg0>onewayOperation1 callback request</arg0>” |
Testcase ID |
BJM_60015_3_TestCase |
Test Assertion |
BJM-TA-60015 |
Description |
For an SCA service with a JMS binding, when a callback request message is sent for either a one-way or request/response MEP, the SCA runtime MUST send the callback request message to the callback destination. This is test for the JMS replyTo property identifying the callback destination |
Artifacts |
BJM_6015_3_TestCase.java Test_BJM_6015.composite Service4Impl1.java |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><arg0>onewayOperation1 callback request</arg0>” |
Testcase ID |
BJM_60016_TestCase |
Test Assertion |
BJM-TA-60016 |
Description |
Tests that for an SCA service with a JMS binding, when a callback request message is sent and no callback destination can be identified then the SCA runtime SHOULD raise an error, and MUST throw an exception to the caller of the callback operation. |
Artifacts |
BJM_6016_TestCase.java Test_BJM_6016.composite Service4Impl1.java |
Expected output |
Negative test: “excpetion” |
Testcase ID |
BJM_60017_1_TestCase |
Test Assertion |
BJM-TA-60017 |
Description |
Tests that for an SCA service with a JMS binding, when a callback request message is sent the SCA runtime MUST set the JMSReplyTo destination in the callback request message as defined in sections 6.1 or 6.2 as appropriate for the type of the callback operation invoked. This is the section 6.2 request-response callback case so a replyTo should be set.
|
Artifacts |
BJM_6017_1_TestCase.java Test_BJM_6017.composite Service4Impl2.java |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><arg0>onewayOperation1 callback request</arg0>” |
Testcase ID |
BJM_60017_2_TestCase |
Test Assertion |
BJM-TA-60017 |
Description |
Tests that for an SCA service with a JMS binding, when a callback request message is sent the SCA runtime MUST set the JMSReplyTo destination in the callback request message as defined in sections 6.1 or 6.2 as appropriate for the type of the callback operation invoked.
This is the section 6.1 oneway callback case so no replyTo should be set.
|
Artifacts |
BJM_6017_2_TestCase.java Test_BJM_6017.composite Service4Impl2.java |
Expected output |
Positive test: “<?xml version=\"1.0\" encoding=\"UTF-8\"?><arg0>operation1 callback request</arg0>” |
Test Assertion |
Test Cases |
BJM-TA-30001 |
BJM_3001_TestCase |
BJM-TA-30002 |
BJM_3002_1_TestCase,BJM_3002_2_TestCase |
BJM-TA-30003 |
BJM_3003_TestCase |
BJM-TA-30004 |
BJM_3004_TestCase |
BJM-TA-30005 |
BJM_3005_TestCase |
BJM-TA-30006 |
Not required (SCA runtimes MAY allow...) |
BJM-TA-30007 |
BJM_3007_TestCase |
BJM-TA-30010 |
Not required (TA SHOULD not MUST) |
BJM-TA-30011 |
BJM_3011A_TestCase,BJM_3011C_TestCase BJM_3011D_TestCase |
BJM-TA-30012 |
BJM_3012A_TestCase,BJM_3012C_TestCase BJM_3012D_TestCase |
BJM-TA-30013 |
Not tested |
BJM-TA-30014 |
BJM_3014A_TestCase,BJM_3014C_TestCase BJM_3014D_TestCase |
BJM-TA-30015 |
BJM_3015Aa_TestCase,BJM_3015Ab_TestCase,BJM_3015Ac_TestCase,BJM_3015Ca_TestCase,BJM_3015Cb_TestCase,BJM_3015Cc_TestCase,BJM_3015Da_TestCase,BJM_3015Db_TestCase,BJM_3015Dc_TestCase |
BJM-TA-30017 |
BJM_3017_TestCase |
BJM-TA-30018 |
BJM_3018_TestCase |
BJM-TA-30019 |
Not tested |
BJM-TA-30020 |
BJM_3020_TestCase |
BJM-TA-30021 |
BJM_3021_TestCase |
BJM-TA-30022 |
Not tested |
BJM-TA-30023 |
BJM_3023_TestCase |
BJM-TA-30024-1 |
BJM_3024_1_TestCase |
BJM-TA-30024-2 |
BJM_3024_2_TestCase |
BJM-TA-30024-3 |
BJM_3024_3_TestCase |
BJM-TA-30024-4 |
BJM_3024_4_TestCase |
BJM-TA-30025-1 |
BJM_3025_1_TestCase |
BJM-TA-30025-2 |
BJM_3025_2_TestCase |
BJM-TA-30026-1 |
BJM_3026_1_TestCase |
BJM-TA-30026-2 |
BJM_3026_2_TestCase |
BJM-TA-30026-3 |
BJM_3026_3_TestCase |
BJM-TA-30028 |
Not required (SCA runtimes MAY allow...) |
BJM-TA-30029 |
BJM_3029_TestCase |
BJM-TA-30030 |
Not required (SCA runtimes MAY allow...) |
BJM-TA-30031 |
BJM_3031_TestCase |
BJM-TA-30034 |
BJM_3034_TestCase |
BJM-TA-30036 |
BJM_3036_TestCase |
BJM-TA-30037 |
Not tested |
Test Assertion |
Test Cases |
BJM-TA-40001 |
BJM_4001_TestCase |
BJM-TA-40002 |
BJM_4002_1_TestCase,BJM_4002_2_TestCase,BJM_4002_3_TestCase,BJM_4002_4_TestCase |
BJM-TA-40003 |
BJM_4003_TestCase |
BJM-TA-40004 |
BJM_4004_TestCase,BJM_4004_2_TestCase |
BJM-TA-40005 |
BJM_4005B_TestCase,BJM_4005T_TestCase |
BJM-TA-40006 |
BJM_4006_TestCase |
BJM-TA-40007 |
Not required (SCA runtimes MAY allow...) |
BJM-TA-40008 |
BJM_4008_TestCase |
BJM-TA-40009 |
BJM_4009_TestCase |
BJM-TA-40010 |
BJM_4010_TestCase |
BJM-TA-40011 |
BJM_4011_TestCase |
Test Assertion |
Test Cases |
BJM-TA-50001 |
BJM_5001_TestCase |
BJM-TA-50002 |
Not tested |
Test Assertion |
Test Cases |
BJM-TA-60001 |
Not tested |
BJM-TA-60002 |
BJM_6002_TestCase |
BJM-TA-60003 |
BJM_6003_1_TestCase,BJM_6003_2_TestCase,BJM_6003_3_TestCase |
BJM-TA-60004 |
BJM_6004_TestCase |
BJM-TA-60005 |
BJM_6005_TestCase |
BJM-TA-60006 |
Not tested |
BJM-TA-60007 |
BJM_6007_TestCase,BJM_6007_2_TestCase |
BJM-TA-60008 |
BJM_6008_TestCase |
BJM-TA-60009 |
Not required (SHOULD not MUST) |
BJM-TA-60010 |
Not tested |
BJM-TA-60011 |
BJM_6011_TestCase |
BJM-TA-60012 |
BJM_6012_TestCase |
BJM-TA-60013 |
BJM_6013_TestCase,BJM_6013_2_TestCase |
BJM-TA-60014-1 |
BJM_6014_1_1_TestCase,BJM_6014_1_2_TestCase |
BJM-TA-60014-2 |
BJM_6014_2_TestCase |
BJM-TA-60015 |
BJM_6015_1_TestCase, BJM_6015_2_TestCase, BJM_6015_3_TestCase |
BJM-TA-60016 |
BJM_6016_TestCase |
BJM-TA-60017 |
BJM_6017_1_TestCase, BJM_6017_2_TestCase |
BJM-TA-60018 |
Not tested |
Name |
Valid |
Description |
TestClient_0001.composite |
Y |
Test client invocation composite 1 service TestInvocation interface TestInvocation 1 reference reference1 (1..1) interface Service1 |
TestComposite1.composite |
Y |
1 service Service1 interface Service1 0 references Service1Impl |
TestComposite21.composite |
Y |
1 service Service2 interface Service2 0 references Service2Impl |
TestComposite34.composite |
Y |
1 service Service3 interface Service3 1 reference Reference3 interface Service3 Service3Impl |
TestComposite4.composite |
Y |
1 service Service1 interface Service1 0 references Service1Impl2 |
Name |
Description |
Service1.java |
Remotable interface with 1 operation “operation1”, string input and output |
Service2.java |
Remotable interface with 2 operations “operation1”, string input and output “operation2”, string input and output |
Service3.java |
Remotable interface with 1 oneway operation “operation1”, string input |
Service4.java |
Remotable interface with call back Service4Callback, with 2 operations “operation1”, string input and output “onewayOperation1”, string input |
Service5.java |
Remotable interface with 2 operations “onMessage”, string input and output “dummy”, string input and output |
Service4Callback.java |
Remotable interface with 2 operations “callbackMessage”, string input “callbackWithReply”, string input and output |
TestInvocation.java |
Remotable interface with 1 operation “invokeTest”, string input,string output |
Name |
Description |
Service1Impl.java |
1 service “Service1”, 1 property “serviceName” |
Service1Impl2.java |
1 service “Service1”, 1 property “serviceName”, 1 reference “reference1” |
Service2Impl.java |
1 service “Service2”, 1 property “serviceName” |
Service2Impl2.java |
1 service “Service2”, 1 references “reference1” |
Service3Impl2.java |
1 service “Service3”, 1 property “serviceName”, 1 reference “reference3” |
Service3Impl3.java |
1 service “Service3”, 1 property “serviceName”, 1 reference “reference4” |
Service3Impl4.java |
1 service “Service3”, 1 property “serviceName”, 1 reference “reference4” |
Service4Impl1.java |
1 service “Service4” |
Service4Impl2.java |
1 service “Service4” |
Service5Impl.java |
1 service “Service5”, 1 property “serviceName” |
BJM_0001_Client.java |
1 service “TestInvocation”, 1 property “testName”, 1 reference “reference1” |
Name |
Description |
Service1.wsdl |
Service1 interface 1 operation “operation1”, string input and output |
Service2.wsdl |
Service2 interface 2 operations “operation1”, string input and output “operation2”, string input and output |
Service3.wsdl |
Service3 interface 1 operation “operation1”, string input and no output |
Service5.wsdl |
Service5 interface 2 operations “onMessage”, string input and output “dummy”, string input and output |
TestInvocation.wsdl |
TestInvocation interface supplied by SCA component to allow client application to invoke test artifacts 1 operation: - "invokeTest" string input, string output |
There are no conformance statements relating to the TestCases.
The following individuals have participated in the creation of this specification and are gratefully acknowledged
Participant Name |
Affiliation |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Revision |
Date |
Editor |
Changes Made |
wd01 |
2010-04-15 |
Simon Holdsworth |
Initial draft |
wd02 |
2010-09-16 |
Ant Elder |
Initial tests for wd06 test assertions doc |
wd03 |
2010-10-07 |
Ant Elder |
Review updates and wd07 test assertions doc |
wd04 |
2010-10-21 |
Ant Elder |
More review updates |
wd05 |
2010-10-27 |
Ant Elder |
Added BJM_3007 and further review updates |
wd06 |
2010-10-29 |
Simon Holdsworth |
Updated references, other editorial updates |
wd07 |
2010-11-11 |
Ant Elder |
Updated some expect messages texts |