jakartaee / jakartaee/platform
Use of JMSConnectionFactoryDefinition/JMSDestinationDefinition annotations based tests was marked as optional in EE10 tests
- Dominant language
- No language data
- Stars
- 230
- Forks
- 76
- Avg merge
- 8d 5h
- Merged PRs (30d)
- 1
Description
**Describe the bug**
There are a package of messaging tests use the `jakarta.jms.JMSConnectionFactoryDefinition` and `jakarta.jms.JMSDestinationDefinition` annotations to define messaging factories and destinations. These tests were marked as both jms_optional javaee_optional in EE10. The wording in the Jakarta Messaging javadoc and spec are not clear that these are optional, and the platform spec does not single these out as optional. Vendors have stated that they did not run the `com.sun.ts.tests.jms.ee20.resourcedefs.*` tests in question as part of the EE10 certification.
I cannot find a clear statement about how these tests became to be marked as optional, so we should clarify this in EE11 at the platform spec level.
Contributor guide
Research direction
Review the Jakarta Messaging javadoc and specification wording for JMSConnectionFactoryDefinition and JMSDestinationDefinition, then inspect the com.sun.ts.tests.jms.ee20.resourcedefs.* tests and their EE10 optional markings. Determine how the tests became optional and clarify their status at the EE11 platform specification level.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100