jakartaee / jakartaee-schemas Goto Github PK

Update <context-service>, <managed-executor>, <managed-scheduled-executor>, and <managed-thread-factory> in deployment descriptor schema to match up with the additions to the annotations from the following pull requests:

• jakartaee/concurrency#348
• jakartaee/concurrency#349

See jakartaee/jakarta.ee#1505

Create corresponding <context-service>, <managed-executor>, <managed-scheduled-executor>, <managed-thread-factory> definitions in deployment descriptor schema to match up with the following annotations from jakartaee/concurrency#141

• ContextServiceDefinition
• ManagedExecutorDefinition
• ManagedScheduledExecutorDefinition
• ManagedThreadFactoryDefinition

What is the plan for Jakarta EE 10.

I know schema updates will be required for Servlet 6.0 and JSP 3.1. I'm happy to provide a PR for that but I need some direction in terms of what is required.

I know especially for Jakarta EE 9 it is mostly XML schemas to refactor into the new namespace, but could this repository also hold other schemas especially JSON schemas in future versions?
There the $id property for a top-level schema should be an absolute-URI, with a domain that you control. For example, "jakarta.ee".

See pull request #15:

"Update Common shareable schemas from 9 to 10"
#15

That created a new "jakartaee_10.xsd", which was propogated to the then present includes of "jakartaee_9.xsd".

There were a number of followup pull requests which renamed the schemas:

"Update Application Deployment Descriptor Schema for Jakarta EE 10"
#19

"Update application client xml schema for Jakarta EE 10"
#20

And others. However, not all of the schemas have been renamed:

connector_2_0.xsd
jakartaee_web_services_2_0.xsd
web-facelettaglibrary_3_0.xsd
web-facesconfig_3_0.xsd

(Not needed: ejb-jar_4_0.xsd.)

This creates incompatible versions of these schemas, which have the old Jakarta EE 9 name and version, but have includes to Jakarta EE 10 schemas.

These remaining schemas need an updated version and need to be renamed.

The published version, at least application.xsd is missing the concurrency elements.

Originally posted by @arjantijms in eclipse-ee4j/glassfish#23989 (comment)

The Jakarta Enterprise Beans specification will NOT be updated for Jakarta EE 10, but will remain at spec level 4.0.

The ejb-jar_4_0.xsd must remain compatible with Jakarta EE 9.

It appears the following was changed in the 4.0 XSD, which would cause it to no longer work for a Jakarata EE 9 implementation:

<xsd:include schemaLocation="jakartaee_10.xsd"/>

Please revert the ejb XSD back to only including jakartaee_9.xsd, as the EJB specification will not be updated to support the new features of Jakarta EE 10, and the scehma must remain campatible with Jakarta EE 9.

Updating the XSD for EJB to include jakartaee_10.xsd has effectively forced a spec revision, as it is requiring the EJB implementation to support new features added elsewhere in Jakarta EE 10.