| Re: [jca-dev] Connector TCK test deployment failures after updating from connector_1_0.dtd to connector_2_0.xsd |
Adding Jakarta Connectors ml... On 8/25/20 4:54 PM, Scott Marlow wrote:
Hi,If the connector tests are failing due to connector_1_0.dtd [1] being less strict than connector_2_0.xsd [2] about the `connection-interface` type, should the TCK connector tests adjust for the stricter connector_2_0.xsd [2] requirement that `connection-interface` be of type "jakartaee:fully-qualified-classType"?Does connector_2_0.xsd require the `connection-interface` class to be in the jakarta namespace?The test failure is mentioned in jakartaee-tck/pull#474 [3] (see second paragraph in comment) and also in test result [4].Connector 2.0 spec [5] shows that connection-interface could be at least one of { jakarta.resource.cci.Connection, jakarta.jms.QueueConnection, jakarta.jms.TopicConnection, jakarta.jms.Connection }.So perhaps the connector TCK tests should update `com.sun.ts.tests.common.connector.whitebox.TSConnectionFactory` to be of type jakarta.resource.cci.Connection.For reference [6] shows the pull/474 ([3]) connector/whitebox/ra-compat-tx.xml file that may need more changes.Scott [1] http://java.sun.com/dtd/connector_1_0.dtd [2] https://jakarta.ee/xml/ns/jakartaee/connector_2_0.xsd[3] https://github.com/eclipse-ee4j/jakartaee-tck/pull/474#issuecomment-680238740 [4] https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck-alw/job/pr%252F474/2/testReport/com.sun.ts.tests.connector.connManager/connManagerClient1/jakartaeetck_run___connector___testTransactionSupportLevels_from_jsp [5] https://jakarta.ee/specifications/connectors/2.0/connectors-spec-2.0-RC2.html [6] https://github.com/eclipse-ee4j/jakartaee-tck/blob/6be543f6f5fdf62a7189e0570c5c80b4df0360a9/src/com/sun/ts/tests/common/connector/whitebox/ra-compat-tx.xml