Document Jakarta API handling

[tmetzke]

Acceptance Criteria (Required on creation)

• The 7.19 documentation features Jakarta-based assets where it makes sense.
• WildFly 27 and 26-related assets are documented.
• An update guide exists for WildFly regarding 7.19 and versions 26 and 27.

Hints

• Should we explicitly explain somewhere which artifacts use Javax and Jakarta API and which ones to use when?

Links

Breakdown

• [x] Update guide features a hint on the WildFly version update and what to consider when moving to 7.19
• [x] WildFly/JBoss installation guide is updated (new artifacts) and hints at the WildFly 26 compatibility artifact(s)
• [x] JTA Transaction Integration guide features the Jakarta- and Javax-based class.
• [x] Process Application class guide hints at the Jakarta variants (e.g. Servlet application class).
• [x] Remove the MVCC parameter from the datasource examples, e.g. in the WildFly/JBoss guide.
• [x] Add WildFly 27 to supported environments

[ThorbenLindhauer]

This guide will need at least an adjustment (that it doesn't work with the Wildfly distro; however, then there is no full CE distro to use the guide with): https://docs.camunda.org/get-started/javaee7/install/

Note that via https://github.com/camunda/camunda-bpm-platform/issues/2733 we could also decide to remove this guide entirely.

[gbetances089]

WildFly27:

• Remove the MVCC parameter from the datasource example
• REST API - Update on this line to the engine rest jakarta API: Choose the correct version named $PLATFORM_VERSION/camunda-engine-rest-jakarta-$PLATFORM_VERSION.war.

[tmetzke]

This guide will need at least an adjustment (that it doesn't work with the Wildfly distro; however, then there is no full CE distro to use the guide with): https://docs.camunda.org/get-started/javaee7/install/

Note that via #2733 we could also decide to remove this guide entirely.

@ThorbenLindhauer, as of now, this will be archived and doesn't have to be updated anymore, right?

[tmetzke]

I incorporated all feedback up until here into the description.

[yanavasileva]

Maybe already obvious, update supported environments: https://docs.camunda.org/manual/develop/introduction/supported-environments/

[ThorbenLindhauer]

Yeah, correct, we do not need to update the Java EE getting started guide.

[tasso94]

Let's not add the new REST artifact to https://docs.camunda.org/manual/latest/introduction/public-api/ to be flexible in the future to discontinue it again.

[tmetzke]

Let's not add the new REST artifact to https://docs.camunda.org/manual/latest/introduction/public-api/ to be flexible in the future to discontinue it again.

Are we "forced" in any way to make things public API? Do we have any obligations here? If not, I agree with this move. In the end, they are currently merely "compatibility" artifacts that might as well be removed in the future and become the "new normal".

[tasso94]

This docs page is part of customer contracts, but we are not forced to add more artifacts to it.

[tmetzke]

Technical review is done from my side, awesome job! 👍