Please push tag for version used to release 2.0.0-RC2

https://repo.maven.apache.org/maven2/jakarta/resource/jakarta.resource-api/2.0.0-RC2

Additionally - there is tag 2.0.0 for not published version, which will probably make conflict on true 2.0.0 release. Consider deletion of it, please.

Compatibility certification request for EE4J implementation of Jakarta Connectors

TCK Results

As required by the
Eclipse Foundation Technology Compatibility Kit License,
following is a summary of the TCK results for releases of Jakarta Connectors.

1.7 Certification Request

Test results:

[javatest.batch] Number of Tests Passed      = 139
[javatest.batch] Number of Tests Failed      = 0
[javatest.batch] Number of Tests with Errors = 0
[javatest.batch] ********************************************************************************
[javatest.batch] PASSED........com/sun/ts/tests/connector/annotations/anno/annotationClient.java#testConfigPropertyAnnotation_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/annotations/anno/annotationClient.java#testConnectorAnnotation_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/annotations/anno/annotationClient.java#testRAAccessibility_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/annotations/anno/annotationClient.java#testSetterMethodConfigPropAnno_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/annotations/mdcomplete/Client.java#testMDCompleteConfigProp_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/annotations/mdcomplete/Client.java#testMDCompleteMCFAnno_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/annotations/partialanno/paClient.java#testDDOverridesAnno_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/annotations/partialanno/paClient.java#testMixedModeConfigPropertyMCF_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/annotations/partialanno/paClient.java#testMixedModeConfigPropertyNoOverride_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/annotations/partialanno/paClient.java#testMixedModeConfigPropertyOverride_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/annotations/partialanno/paClient.java#testMixedModeConfigPropertyRA_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/annotations/partialanno/paClient.java#testNoDefaultVallAnnoElement_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/connManager/connManagerClient1.java#testcheckConnectionManager_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/connManager/connManagerClient1.java#testTransactionSupportLevels_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/compat/compatClient1.java#testGetConnection1_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/compat/compatClient1.java#testgetConnectionWithParameter1_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testAPIApplicationServerInternalException_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testAPICommException_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testAPIEISSystemException_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testAPIHintsContext_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testAPIIllegalStateException_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testAPIInvalidPropertyException_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testAPILocalTransactionException_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testAPIManagedConnection_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testAPIManagedConnectionMetaData_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testAPINotSupportedException_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testAPIResourceAdapterInternalException_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testAPIResourceAllocationException_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testAPIResourceException_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testAPIRetryableUnavailableException_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testAPIRetryableWorkRejectedException_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testAPISecurityException_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testAPISharingViolationException_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testAPIUnavailableException_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testAPIWorkCompletedException_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testAPIWorkException_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testAPIWorkRejectedException_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testGetConnection1_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/connection/connectionClient1.java#testgetConnectionWithParameter1_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/event/eventClient1.java#testConnectionEventListener_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/lifecycle/lifecycleClient1.java#testAssociationMCFandRA_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/lifecycle/lifecycleClient1.java#testAssociationMCFandRA2_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/lifecycle/lifecycleClient1.java#testBootstrapforNull_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/lifecycle/lifecycleClient1.java#testInstantiationOfRA_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/lifecycle/lifecycleClient1.java#testMCFcalledOnce_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/lifecycle/lifecycleClient1.java#testRAforJavaBean_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/lifecycle/lifecycleClient1.java#testRASharability_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/security/securityClient1.java#testAppEISSignon_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/security/securityClient1.java#testCBTestAllCallbacksAndPrin_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/security/securityClient1.java#testCBTestAllCallbacksNullPrin_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/security/securityClient1.java#testCBTestCPCandGPC_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/security/securityClient1.java#testCBTestCPCandNullPrin_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/security/securityClient1.java#testCBTestCPCandPrin_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/security/securityClient1.java#testCBTestCPCandPVC_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/security/securityClient1.java#testCBTestEISCPCandPrin_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/security/securityClient1.java#testCBTestGPCandCPCFail_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/security/securityClient1.java#testComponentManaged_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/security/securityClient1.java#testConnManagerAllocateConnection_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/security/securityClient1.java#testContainerManaged_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/transinflow/transinflowClient1.java#testConcurrentWorkXid_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/transinflow/transinflowClient1.java#testGetTransactionSupport_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/transinflow/transinflowClient1.java#testSetResourceAdapterMethod_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/transinflow/transinflowClient1.java#testTransactionSynchronizationRegistry_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/transinflow/transinflowClient1.java#testXATerminator_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/workcontext/WorkContextClient.java#testHICNotifications_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/workcontext/WorkContextClient.java#testIsContextSupported_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/workcontext/WorkContextClient.java#testNestedWorkContexts_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/workcontext/WorkContextClient.java#testNestedWorkContexts2_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/workcontext/WorkContextClient.java#testNestedWorkContexts3_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/workcontext/WorkContextClient.java#testSecurityContextCBH_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/workcontext/WorkContextClient.java#testSecurityContextExecSubject_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/workcontext/WorkContextClient.java#testSecurityContextServiceSubject_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/workcontext/WorkContextClient.java#testWorkContextErrorCode_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/workcontext/WorkContextClient.java#testWorkContextErrorCode2_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/workcontext/WorkContextClient.java#testWorkContextNotifications_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/workcontext/WorkContextClient.java#testWorkContextProvider_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/workmgt/workmgtClient1.java#testForUnsharedTimer_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/workmgt/workmgtClient1.java#testNestedWork_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/workmgt/workmgtClient1.java#testScheduleWork_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/workmgt/workmgtClient1.java#testScheduleWorkListener_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/workmgt/workmgtClient1.java#testUnknownWorkDuration_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/workmgt/workmgtClient1.java#testWorkCompletedException_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/workmgt/workmgtClient1.java#testWorkListenerImplementation_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/localTx/workmgt/workmgtClient1.java#testWorkManagerImplementaion_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/compat/compatClient1.java#testGetConnection1_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/compat/compatClient1.java#testgetConnectionWithParameter1_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/connection/connectionClient1.java#testGetConnection1_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/connection/connectionClient1.java#testgetConnectionWithParameter1_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/event/eventClient1.java#testConnectionEventListener_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/lifecycle/lifecycleClient1.java#testAssociationMCFandRA_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/lifecycle/lifecycleClient1.java#testAssociationMCFandRA2_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/lifecycle/lifecycleClient1.java#testBootstrapforNull_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/lifecycle/lifecycleClient1.java#testInstantiationOfRA_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/lifecycle/lifecycleClient1.java#testMCFcalledOnce_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/lifecycle/lifecycleClient1.java#testRAforJavaBean_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/lifecycle/lifecycleClient1.java#testRASharability_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/security/securityClient1.java#testAppEISSignon_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/security/securityClient1.java#testComponentManaged_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/security/securityClient1.java#testConnManagerAllocateConnection_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/security/securityClient1.java#testContainerManaged_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/workmgt/workmgtClient1.java#testForUnsharedTimer_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/workmgt/workmgtClient1.java#testNestedWork_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/workmgt/workmgtClient1.java#testScheduleWork_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/workmgt/workmgtClient1.java#testScheduleWorkListener_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/workmgt/workmgtClient1.java#testUnknownWorkDuration_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/workmgt/workmgtClient1.java#testWorkCompletedException_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/workmgt/workmgtClient1.java#testWorkListenerImplementation_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/noTx/workmgt/workmgtClient1.java#testWorkManagerImplementaion_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/permissiondd/Client.java#testValidateCustomPerm_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/permissiondd/Client.java#testValidateLocalGrantForCustomPerm_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/permissiondd/Client.java#testValidateLocalPermsInvalidName_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/permissiondd/Client.java#testValidateMissingPermFails_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/permissiondd/Client.java#testValidateRequiredPermSet_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/permissiondd/Client.java#testValidateRestrictedLocalPerm_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/compat/compatClient1.java#testGetConnection1_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/compat/compatClient1.java#testgetConnectionWithParameter1_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/connection/connectionClient1.java#testGetConnection1_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/connection/connectionClient1.java#testgetConnectionWithParameter1_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/event/eventClient1.java#testConnectionEventListener_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/lifecycle/lifecycleClient1.java#testAssociationMCFandRA_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/lifecycle/lifecycleClient1.java#testAssociationMCFandRA2_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/lifecycle/lifecycleClient1.java#testBootstrapforNull_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/lifecycle/lifecycleClient1.java#testInstantiationOfRA_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/lifecycle/lifecycleClient1.java#testMCFcalledOnce_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/lifecycle/lifecycleClient1.java#testRAforJavaBean_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/lifecycle/lifecycleClient1.java#testRASharability_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/security/securityClient1.java#testAppEISSignon_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/security/securityClient1.java#testComponentManaged_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/security/securityClient1.java#testConnManagerAllocateConnection_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/security/securityClient1.java#testContainerManaged_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/workmgt/workmgtClient1.java#testForUnsharedTimer_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/workmgt/workmgtClient1.java#testNestedWork_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/workmgt/workmgtClient1.java#testScheduleWork_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/workmgt/workmgtClient1.java#testScheduleWorkListener_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/workmgt/workmgtClient1.java#testUnknownWorkDuration_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/workmgt/workmgtClient1.java#testWorkCompletedException_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/workmgt/workmgtClient1.java#testWorkListenerImplementation_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/connector/xa/workmgt/workmgtClient1.java#testWorkManagerImplementaion_from_connectorservlet
[javatest.batch] PASSED........com/sun/ts/tests/signaturetest/connector/ConnectorSigTest.java#signatureTest
[javatest.batch] 
[javatest.batch] Total time = 228s
[javatest.batch] Setup time = 0s
[javatest.batch] Cleanup time = 0s
[javatest.batch] Test results: passed: 139

Finalize the Jakarta Connectors 2.1 Release

Please complete these steps to finalize the release:

promotes api staging release promotes the specification api jars to maven central. An example release job script can be found here https://wiki.eclipse.org/MavenReleaseScript.
go through the merged jakarta.ee specification website page to verify all the links are valid.
if XML Schemas are published on https://jakarta.ee/schemas, send a PR to update the status from Draft to Final.
approve the compatibility request.
The compatible implementation project/vendor MUST send an email to [email protected] for approval of the compatible implementation for trademark usage.
merge any final release branch as appropriate for the branch management for the project.

Prepare Jakarta Connectors for Jakarta EE 8 Release

Tasks

Update text files
Generate "boilerplate" specification project
Make a staging release
Generate Stand-alone TCK test results
Create a PR to jakartaee/specifications repository
Update the Jakarta EE API jar by submitting a PR to the jakartaee-api project

See here for detailed instructions.

Place holder issue for Pull Request 4

This is a place holder issue for Pull request from javaee/javax.resource#4

Jakarta EE 8 TCK job

To test Jakarta EE 8 compatibility we need to create a Jenkins job on project's Cloud Jenkins instance formally testing the API against the relevant TCK and as needed, relevant CTS subset tests.

For projects that do not already have automated testing, there is provided parameterized Jenkins job that can be invoked to perform these tests. User provides a link to an Eclipse GlassFish test build and sets the test sub-set parameters:

For CTS -- https://ci.eclipse.org/jakartaee-tck/job/jakartaeetck-certification/
For Stand-alone TCKs -- https://ci.eclipse.org/jakartaee-tck/job/standalonetck-certification/

Additional instructions and guidance for using and directly running TCKs is available on this wiki. Also in the jakartaee-tck project repository.

Need draft PR for EE10

Hello, the deadline for individual component specifications to create a draft PR in the https://github.com/jakartaee/specifications project with candidate final API and specification is Feb 28. There does not need to be a complete PR with a compatible implementation. All that is required is to have the final candidate API staged, and to have a PR that include the candidate final specification. If your project cannot meet this deadline, it is possible it will miss the EE10 release train. Let the platform dev team([email protected]) or the EE10 release coordinator ([email protected]) when you will be able to create the PR, or if the EE10 platform should release with the previous version.

Update EFSL for Specifications and Javadoc

Per the discussions on the Spec Committee and Platform Dev mailing lists, it's been discovered that many of the Javadoc and Spec references to the EFSL need updating. Please reference the following required updates and keep them in mind as your Spec Project is updating the files for Jakarta EE 9.

Note: Some Spec Projects have already started or even completed these updates. If so, just kindly return/close this Issue. Thanks!

Required EFSL updates for Javadoc

For javadoc, the EFSL.html located in src/main/javadoc/doc-files should be modified as follows:

the <<url to this license>> needs to be replaced with efsl.php link[1]
the [title and URI of the Eclipse Foundation specification document] needs to be replaced with the Specification Name and URL (Reference [2] for an example.)
The javadoc footer copyright year needs to be updated to 2018, 2020 as defined in the pom.xml

Required EFSL updates for Specifications

For specification, the license-efsl.adoc located in src/main/asciidoc should be modified as follows:

Update copyright year to 2018, 2020 from 2019. Add link to EFSL.
the <<url to this license>> needs to be replaced with efsl.php link[1]
the [title and URI of the Eclipse Foundation specification document] needs to be replaced with the Specification Name and URL (Reference [2] for an example.)

[1] https://www.eclipse.org/legal/efsl.php
[2] https://jakarta.ee/specifications/enterprise-beans/4.0/

Compatibility Certification Request for Eclipse GlassFish 7.0.0-M4

2.1 Certification Request

Release CI/CD pipeline

We need to create a release CI/CD pipeline for this project.

Use these documents as a reference:

Excessively large html spec file, disable embedded images

It turns out that the https://jakarta.ee/specifications/cdi/3.0/jakarta-cdi-spec-3.0.html page is too large to be served by the EF infrastructure currently. The main reason is that the html generation is embedding the image files into the single html file. This comes from the <data-url /> element in this configuration section:

                    <execution>
                        <id>asciidoc-to-html</id>
                        <phase>generate-resources</phase>
                        <goals>
                            <goal>process-asciidoc</goal>
                        </goals>
                        <configuration>
                            <backend>xhtml</backend>
                            <attributes>
                                <doctype>book</doctype>
                                <status>${status}</status>
                                <data-uri />
                                <icons>font</icons>
                                <toc>left</toc>
                                <icons>font</icons>
                                <sectanchors>true</sectanchors>
                                <idprefix />
                                <idseparator>-</idseparator>
                                <docinfo1>true</docinfo1>
                            </attributes>
                        </configuration>
                    </execution>

With that enabled, the generated html file is ~59Mb:

└> ls -l target/generated-docs 
total 216032
drwxr-xr-x  205 starksm  staff      6560 Aug 25 09:27 images
-rw-r--r--    1 starksm  staff  59310423 Aug 25 09:27 jakarta-connectors-spec.html
-rw-r--r--    1 starksm  staff  50446314 Aug 25 09:27 jakarta-connectors-spec.pdf

With that setting removed, the generated html file is 1.1Mb:
└> ls -lh target/generated-docs
total 102536
drwxr-xr-x 205 starksm staff 6.4K Aug 25 09:29 images
-rw-r--r-- 1 starksm staff 1.1M Aug 25 09:29 jakarta-connectors-spec.html
-rw-r--r-- 1 starksm staff 48M Aug 25 09:29 jakarta-connectors-spec.pdf

The image files are also excessively large and can be scaled down with no loss in clarity if desired to reduce the pdf size. One example is the conn-79.jpg file which is 5.3Mb and 4951 × 6514 pixels. Just converting this to a lower quality image with the same size and dpi reduces the size to 667Kb with no apparent loss of image quality.

Some observed issues in 2.0 Specification Text

A list of apparent formatting and other errors in Connector Spec

Copyright dates should be consistent across TCK, JavaDocs, and Spec. Docs. I believe they should be 2018, 2019 for all three.
JavaDocs could benefit with a "Send comments to [email protected]" or something like that in the page footer.
Following refer to the Spec. doc. (Reviewed the .html copy)
- Many internal links don't work. Dare I say most? Due to this, I couldn't tell if they were intended to be external references or not.
- Some refs. appear to be footnotes, but there is no aggregation of these (at least not in the .html render)
- Diagram in 8.6.4 -- Consecutive question mark text in left-most item should be: "Transaction.enlistResource(XAResource)". Text in bottom (final) should be: "XAResource.start(XID, flag)" (Quote from last Java EE version of Spec.)
- Diagram in 8.6.5 Text with question marks should be (left most) "Transaction.delistResource(XAResource, flag)" text in right most should be, "XAResource.end(XId, flag)". (same source as previous).
- 8.6.5, diagram fidelity loss. The text in the top far-right box originally used text position to distinguish the final three lanes (in lane-order, left to right: ManagedConnection Factory; Managed Connection; XAResource. This detail is lost in the new diagram.
- Diagram in 8.10.3 "Connection Sharing Across Component Instances" string of question marks (just below LocalTransaction.begin) should be: "EJB A gets a connection handle and performs a unit of work on the EIS resource manager"
- 11.4.4.1 DistributableWork interface -- Text formatting problems in paragraph immediately following the code block.
- 14.9.2.1 XML format document format could be improved
- 17.4.1 Text formatting in 2nd paragraph
- 18.9, malformed control/text directive (appears to be missing a second closing square bracket).
- 18.12.x has occasional free-floating punctuation. This results in a couple of strange looking lines of text.
- 19.4 toward the end is a misformatted paragraph.

More general observations

References to legacy Spec. versions might be improved if they can use Jakarta EE references. Some legacy EJB references could be Jakarta Enterprise Bean Spec. references or could be EJB / Java EE references. Since the links didn't work, I couldn't easily sort it out. We would like to avoid references that are ambiguous, wherever possible even though the conversion and subsequent name changes are not helping us keep clarity.
Need to decide what to do with the references in section 2.5 to SCA and JBI. Are these even useful any more?
Was surprised to see the text in section 2.7 (document conventions) so far down into the text. I'd have expected this to be before any of the Specification Proper text had started.
May need to rework section 8.4 -- relationship to JAkarta Transaction, JTA (CORBA 1.1 definition?)
Section 22 Runtime Environment will need to be updated when we update to JDK 11
Would be nice if we could figure out how to relabel the appendices as appendices (comparing against the final Java EE JCA Spec.)
I think the "external references" section could be valuable. Consider reinstating that section.

Use Repeatable meta-annotation

Annotations that could be made @Repeatable include;
AdministeredObjectDefinition, ConnectionFactoryDefinition

Consider renaming resource.cci.Record to avoid collisions with java.lang.Record

JDK 14 introduces java.lang.Record thus making all usages of *.resource.cci.Record ambiguous even if there is direct import.

javax.resource.cci.MappedRecord should extend Map with generics

Currently MappedRecord is defined as interface MappedRecord extends Record, java.util.Map, java.io.Serializable which effectively disallows providing implementation of MappedRecord with generics.

Specification type in package name

The spec has a very small typo
javax.transaction-.xa.XAException --> I think there is a "-" we should remove.

Update images in spec document for Jakarta EE 9

Images need an update in the specification document for Jakarta EE 9

Release to OSSRH staging repository

Uptake new Eclipse versions of dependencies (if any). Use GlassFish 5.1 Release Tracker wiki to find components versions to use.
Release to OSSRH staging repository
Update GlassFish 5.1 Release Tracker with released version number.

Integrate to GlassFish

Integrate to Eclipse GlassFish
Pass all CTS/TCK tests

#15 must be finished before starting working on this task.

Compatibility certification request for Eclipse GlassFish as implementation of Jakarta Connectors 2.0

2.0 Certification Request

provide 2.1.0-RC1 for early adopters

multiple implementation projects do depend on this including but not limited to GlassFish, Metro, EclipseLink, so it would be very helpful, if some early build with changes targeted for EE 10 is made available to them, ie through staging

Start a Release Review

Passing Release Review is a required step before making a first public release. Deadline for passing the review is Nov 30th, 2018. Release review takes some time to complete, so it makes sense initiating it as soon as possible.

Start Release Review
Update Release Review Tracker

Additional information:

Convert "Eclipse Project for JCA" into a specification project

In order to prepare this project to engage in specification work, we need to convert it into a specification project as defined by the Eclipse Foundation Specification Process (EFSP). As part of this work, we will change the project name and the scope.

We'll use this issue to capture the work that needs to be done as part of this effort.

Resolve #37
Resolve #36
Successful complete a restructuring review
Designate the project as a specification project of the Jakarta EE Working Group
Change project name
Change project scope

Before final release update transactions api version

Currently the pom for the api references a Jakara Transactions RC version as that is the current latest available api. It must be updated before final release.

Move this repo to https://github.com/jakartaee

In the steering committee we voted to moved all specification projects from eclipse-ee4j to jakartaee. As such this repo should move to in due time.

Moving is fairly automatic, and redirects will be automatically put in place from the current location here to the new location.

If someone can authorise the move I can take care of it if needed.

Extra from: https://www.eclipse.org/lists/jakarta.ee-spec/msg02073.html

"We voted on it in 2019 and then in 2020 we added it explicitly to our 2021 plan and voted on that plan. I think we just need to start executing. I sent about 30 emails like the following in an attempt to add some shape to it and kick off the move in the spec projects.

Also note that many projects have indeed moved: https://github.com/jakartaee/

ActivationSpec and supportsDynamicUpdates

The JCA specs mentions the support of dynamic updates on configuration properties of ActivationSpec, but does not mention AFAIK how the resource adapter should behave related to the endpointActivation.
When a property on the ActivationSpec is changed at runtime, will the resource adapter walk through an endpointDeactivation-endpointActivation sequence or does the underlying worker needs to handle this itself?
And how to retrieve the active ActivationSpec bean instance at runtime from within a certain application? Should the resource adapter do a self-registration within JNDI so the application can access this?

The idea is that I provide a sane default configuration for my endpoints at deployment time, but that I can change the configuration at run-time without the need to restart my application. For example, when the Ethereum client node address changes.
See also:
https://github.com/e-Contract/ethereum-resource-adapter

Could someone highlight how to implement dynamic updates on ActivationSpec?

Spec documents must start with jakarta- prefix

Spec documentations must have jakarta- prefix.

Jakarta release has wrong OSGi Bundle-SymbolicName

Jakarta release of this API has wrong value of OSGi Bundle-SymbolicName in MANIFEST.MF.
Current value is javax.resource-api but expected value could be jakarta.resource-api .

Update Scope Statement for Jakarta Connector Architecture Project

Update the scope statement for the project: https://projects.eclipse.org/projects/ee4j.jakartaee-platform/governance

See https://docs.google.com/spreadsheets/d/1FPLjo_DJDOQngVtdrYgaDk98d9NBG-0ODgdmOG3LOsI/edit?usp=sharing for examples.

Wrong OSGi relation between JCA 1.7 and JTA 1.3 (JavaEE8, JakartaEE8)

I'm working on https://github.com/ops4j/org.ops4j.pax.transx OSGi project and I want to polish the dependencies related to different JavaEE APIs.
I also maintain my own matrix of versions (no JavaEE 9 yet) here

There is some confusion about JTA 1.2/1.3 and JCA 1.7 versions

According to Oracle JavaEE 7 components, there should be JTA 1.2 and JCA 1.7
According to Oracle JavaEE 8 components, there should be JTA 1.2 and JCA 1.7
According to Eclipse EE4j 8 B.1. Java EE 8 and Jakarta EE 8 Specification Comparisons, Jakarta EE 8 should use JTA 1.3 and not 1.2 - which is explained in B.1.1. Transaction 1.2 vs 1.3 section

However I checked available Maven central artifacts:

javax.resource/javax.resource-api/1.7 has Import-Package: ...,javax.transaction;version="[1.2,1.3)",javax.transaction.xa;version="[1.2,1.3)"
javax.resource/javax.resource-api/1.7.1 has Import-Package: ...,javax.transaction;version="[1.3,2.0)",javax.transaction.xa
jakarta.resource/jakarta.resource-api/1.7.4 has Import-Package: ...,javax.transaction;version="[1.3,2.0)",javax.transaction.xa

However each of the above has some problems...

Javax JCA API 1.7 has too narrow version range...
which was fixed in https://github.com/javaee/javax.resource/pull/4/files and Javax JCA API 1.7.1, but this version however should include JTA 1.2 API, as specified in JavaEE 8 (differently than in JakartaEE 8)
Jakarta JCA API 1.7.4 gets it almost correct, but
- Even if it's Jakarta version (and JTA 1.3 is justified here) the package is still javax.transaction and JakartaEE8 should be compatible with JavaEE8, so the range should be [1.2,2)
- it exports doc-files package which is a result of wrong maven-bundle-plugin configuration

Place holder issue for Pull Request 2

This is a place holder issue for Pull request from javaee/javax.resource#2

Update Eclipse GlassFish

Update Eclipse GlassFish to use the new version of your API (and implementation, if applicable) by submitting a PR to GlassFish.

Although a new version of GlassFish will not be released for Jakarta EE 8, we hope to release an update sometime later.

Build CI/CD pipeline

This task is for creating a basic build CI/CD pipeline for this project on Eclipse infrastructure. More information is here: https://ci.eclipse.org/.

Public Release

Last CTS runs indicate no failures in this component. It's time to make a public release. Before the release make sure that Eclipse Release Review is passed and all dependencies have been released.

Schema needs an update for Jakarta EE 9

Schemas need to be updated to the new namespace. Once done the appendix in the specification document needs work

Complete the Release of Connectors 2.0

These are the remaining steps as per the spec-committee guide for the project team to complete to finalise the release of Connectors 2.0:

promotes api staging release promotes the specification api jars to maven central. An example release job script can be found here https://wiki.eclipse.org/MavenReleaseScript.
go through the merged jakarta.ee specification website page to verify all the links are valid.
approve the compatibility request.
The compatible implementation project/vendor MUST send an email to [email protected] for approval of the compatible implementation for trademark usage.
merge any final release branch as appropriate for the branch management for the project.

Remove deprecated APIs for Jakarta EE 9

There are some deprecated apis lying around in the api. May as well remove them if we are moving namespace.

Project naming confusion

The Jakarta documentation about this specification indicates that the API uses the naming jakarta.connectors:jakarta.connectors-api:[version] (https://jakarta.ee/specifications/connectors/2.0/). So why are we using a different Artifact/Group IDs here?

https://github.com/eclipse-ee4j/jca-api/blob/b24b3471a445b177b19594e6f296916ab9f026c8/api/pom.xml#L28-L30

Support for creating connector spec resources like ConnectionFactory in Resource Adapters

Just as it can be useful to package (embed) a resource adapter and an application together, it could also be useful to be able to allow resource adapters to create what would normally be application defined resources like @ConnectionFactoryDefinition and @ConnectionFactoryDefinitions. This would allow the creation of a self-contained ear that could be deployed to any jakarta ee compliant app server w/o having to deal with server config.

Change project name to Jakarta Connectors

Background information:
https://waynebeaton.wordpress.com/2019/04/04/renaming-java-ee-specifications-for-jakarta-ee/

Checklist:

GitHub
README file
CONTRIBUTING file
Eclipse Project under https://projects.eclipse.org/projects/ee4j

Place holder issue for Pull Request 6

This is a place holder issue for Pull request from javaee/javax.resource#6

Place holder issue for Pull Request 1

This is a place holder issue for Pull request from javaee/javax.resource#1

Place holder issue for Pull Request 3

This is a place holder issue for Pull request from javaee/javax.resource#3

Deliver Jakarta Connectors Specification Version update for Jakarta EE 9

Is your feature request related to a problem? Please describe.
Jakarta EE 9 is the next major release, with the main focus of moving from the javax namespace to the jakarta namespace.

Describe the solution you'd like
This issue will be used to track the progress of this work effort via the Jakarta EE 9 Project board.

Additional context
Jakarta EE Specification Process
Eclipse Project Handbook
Eclipse Release Record for Jakarta EE 9

ToDo

Need explicit requirement against resource adapter implementing both specs at once

We should include a requirement in the Jakarta Connectors spec stating that a single resource adapter RAR file must not simultaneously implement both the Jakarta Connectors spec and the Java EE JCA spec. If any resource adapters choose to implement both at once in a single RAR, I could see this bringing a lot of trouble to application servers as well as users who would end up going through the trouble of having to figure out how to bring in the missing spec classes that aren't provided by the app server, the extra footprint it would require, and the possibility of things not working right.

Merge (original) JCA Connectors specification source

Just an FYI... The original (oracle) JCA Connectors specification source is now available via this CQ: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=21459

Please import/modify/merge it when time allows, hopefully in time for Jakarta EE 9. Thanks!

Update reference Jakarta Platform, Enterprise Edition (Jakarta EE) Specification, version 8

Update reference of Jakarta Platform, Enterprise Edition (Jakarta EE) Specification, version 8 at 5.1.2 Application Server Vendor

jakartaee/specifications#268 (comment)

Place holder issue for Pull Request 5

This is a place holder issue for Pull request from javaee/javax.resource#5

Update CONTRIBUTING.md for Specification Project's repositories

Create/Update CONTRIBUTING files

Per input from the Eclipse EMO, each Specification Project needs to ensure that a CONTRIBUTING.md or CONTRIBUTING.adoc file exists in each specification-related repository maintained by Specification Projects.
In addition, the CONTRIBUTING.md or CONTRIBUTING.adoc file needs to include the following text:

## Eclipse Development Process

This Eclipse Foundation open project is governed by the Eclipse Foundation
Development Process and operates under the terms of the Eclipse IP Policy.

The Jakarta EE Specification Committee has adopted the Jakarta EE Specification
Process (JESP) in accordance with the Eclipse Foundation Specification Process
v1.2 (EFSP) to ensure that the specification process is complied with by all
Jakarta EE specification projects.

* https://eclipse.org/projects/dev_process
* https://www.eclipse.org/org/documents/Eclipse_IP_Policy.pdf
* https://jakarta.ee/about/jesp/
* https://www.eclipse.org/legal/efsp_non_assert.php

Please do this at your earliest convenience.
Thank you!

-- EE4J PMC ([email protected])

Change Maven coordinates

All current API libraries shipped must be distributed to Maven Central under a sub-package of the jakarta groupId. Before the first release Maven coordinates of this project must be changed as it's described here.

jakartaee / connectors Goto Github PK

connectors's People

Contributors

Stargazers

Watchers

Forkers

connectors's Issues

TCK Results

1.7 Certification Request

Tasks

2.1 Certification Request

2.0 Certification Request

Recommend Projects

Recommend Topics

Recommend Org

Jobs