Steve,
It’s already in the platform schema,
https://github.com/eclipse-ee4j/jakartaee-schemas/pull/29/files
I added it last year at the same time we added ManagedExecutorDefinition and the other annotations.
Our project TCK doesn’t currently test this because the function is part of the platform schema not the Concurrency spec, and I had been thinking that any testing which gets done for it would need to be in the platform tests. However,
over the past half year or so there seems to be a greater acceptance within the community of moving platform level testing to the individual spec project TCKs (and then deleting the platform tests), so we could potentially do that.
From:
cu-dev <cu-dev-bounces@xxxxxxxxxxx> on behalf of "Steve Millidge (Payara)" <steve.millidge@xxxxxxxxxxx>
Reply-To: cu developer discussions <cu-dev@xxxxxxxxxxx>
Date: Thursday, March 3, 2022 at 4:03 AM
To: cu developer discussions <cu-dev@xxxxxxxxxxx>
Subject: [EXTERNAL] [cu-dev] Javadoc implies a deployment descriptor
Hi,
The Javadoc for ManagedExecutorDefinition states a deployment descriptor can be used to create a ManagedExecutor see
concurrency-api/ManagedExecutorDefinition.java at master · eclipse-ee4j/concurrency-api · GitHub same for ScheduledExecutorDefinition etc. do we want to remove this from the Javadoc or do we want to try and get this into some platform schema somewhere?
I assume the TCK isn’t testing this?
Thanks
Steve Millidge