Update external support links

docs/documentation/examples/index.md

@@ -9,4 +9,4 @@ Completed the [Getting Started Guides](../../get-started/index.md)? Now discover
 
 This page collects links to hands-on examples around Operaton.
 
-* [Examples](https://github.com/operaton/operaton-examples) (on GitHub)
+* [Operaton Examples](https://github.com/operaton/operaton-examples) (on GitHub)

docs/documentation/installation/full/tomcat/index.md

@@ -12,6 +12,6 @@ menu:
 
 ---
 
-This document describes the installation of the [Full Distribution](../../../introduction/downloading-operaton.md#full-distribution) for [Apache Tomcat Application Server](http://tomcat.apache.org/).
+This document describes the installation of the [Full Distribution](../../../introduction/downloading-operaton.md#full-distribution) for [Apache Tomcat Application Server](https://tomcat.apache.org/).
 
 There are different options for installing the Full Distribution:

docs/documentation/installation/full/tomcat/manual.md

@@ -7,7 +7,7 @@ description: "Manually install and configure the Full Distribution on a vanilla
 ---
 ## Install the Full Distribution on a Tomcat Application Server manually
 
-This section describes how you can install Operaton and its components on a vanilla [Apache Tomcat](http://tomcat.apache.org/), if you are not able to use the pre-packaged Tomcat distribution. In addition, download the matching Tomcat distribution from the [Operaton GitHub releases](https://github.com/operaton/operaton/releases) to fetch the required Operaton modules. Release assets are attached to version tags such as `v$PLATFORM_VERSION`; snapshot assets are published as GitHub prereleases with tags such as `2.2.0-SNAPSHOT`.
+This section describes how you can install Operaton and its components on a vanilla [Apache Tomcat](https://tomcat.apache.org/), if you are not able to use the pre-packaged Tomcat distribution. In addition, download the matching Tomcat distribution from the [Operaton GitHub releases](https://github.com/operaton/operaton/releases) to fetch the required Operaton modules. Release assets are attached to version tags such as `v$PLATFORM_VERSION`; snapshot assets are published as GitHub prereleases with tags such as `2.2.0-SNAPSHOT`.
 
 :::note[Reading the Guide]
 Throughout this guide we will use a number of variables to denote common path names and constants:
@@ -28,10 +28,10 @@ To resolve this, move the weld library away from the war and place it into the `
 
 The above workaround is not guaranteed to work for cases with bean references between WAR deployments (WAR A referencing a bean from WAR B).
 
-The following test scenarios fail on Tomcat 10:
+The following test scenarios fail on Tomcat 11:
 
-* [CallActivityContextSwitchTest](https://github.com/operaton/operaton-bpm-platform/blob/f37877b822dabcbf3cee5806bd5833d18cdcb543/qa/integration-tests-engine/src/test/java/org/operaton/bpm/integrationtest/functional/context/CallActivityContextSwitchTest.java)
-* [CdiBeanCallActivityResolutionTest](https://github.com/operaton/operaton-bpm-platform/blob/f37877b822dabcbf3cee5806bd5833d18cdcb543/qa/integration-tests-engine/src/test/java/org/operaton/bpm/integrationtest/functional/cdi/CdiBeanCallActivityResolutionTest.java)
+* [CallActivityContextSwitchTest](https://github.com/operaton/operaton/blob/main/qa/integration-tests-engine/src/test/java/org/operaton/bpm/integrationtest/functional/context/CallActivityContextSwitchTest.java)
+* [CdiBeanCallActivityResolutionTest](https://github.com/operaton/operaton/blob/main/qa/integration-tests-engine/src/test/java/org/operaton/bpm/integrationtest/functional/cdi/CdiBeanCallActivityResolutionTest.java)
 :::
 
 

docs/documentation/installation/full/wildfly/index.md

@@ -12,6 +12,6 @@ menu:
 
 ---
 
-This document describes the installation of the [Full Distribution](../../../introduction/downloading-operaton.md#full-distribution) for [WildFly Application Server](http://www.wildfly.org).
+This document describes the installation of the [Full Distribution](../../../introduction/downloading-operaton.md#full-distribution) for [WildFly Application Server](https://www.wildfly.org/).
 
 There are different options for installing the Full Distribution:

docs/documentation/installation/full/wildfly/manual.md

@@ -7,7 +7,7 @@ description: "Install and configure the Full Distribution on a vanilla WildFly A
 ---
 ## Install the Full Distribution on a WildFly Application Server manually
 
-This document describes the installation of Operaton and its components on a vanilla [WildFly Application Server](http://www.wildfly.org) or JBoss EAP 7 / 8.
+This document describes the installation of Operaton and its components on a vanilla [WildFly Application Server](https://www.wildfly.org/) or JBoss EAP 7 / 8.
 
 :::note[Reading this Guide]
 This guide uses a number of variables to denote common path names and constants:
@@ -136,8 +136,8 @@ typically `bin`.
 Using H2 as a database is ideal for development purposes but is not recommended for usage in a productive environment.
 These links point you to resources for other databases:
 
-* [How to configure an Oracle database](http://www.ironjacamar.org/doc/userguide/1.0/en-US/html_single/#ex_datasources_oracle)
-* [How to configure a MySQL database](http://www.ironjacamar.org/doc/userguide/1.0/en-US/html_single/#ex_datasources_mysql)
+* [How to configure an Oracle database](https://www.ironjacamar.org/doc/userguide/1.0/en-US/html_single/#ex_datasources_oracle)
+* [How to configure a MySQL database](https://www.ironjacamar.org/doc/userguide/1.0/en-US/html_single/#ex_datasources_mysql)
 
 ### Optional Components
 
@@ -259,7 +259,6 @@ See one of the following ways to fix this:
 2. Exclude implicitly added JAX-RS dependencies.
  * Add a `jboss-deployment-structure.xml` file to you application in the WEB-INF folder.
  * Exclude the JAX-RS subsystem and add the Jackson dependencies, with the version which is used by the Operaton Spin Plugin.
- * This solution is also shown in the [Jackson Annotation Example for WildFly](https://github.com/operaton/operaton-bpm-examples/blob/master/wildfly/jackson-annotations) in the Operaton example repository.
 
 See this [Forum Post](https://forum.operaton.org/t/operaton-json-marshalling-and-jsonignore/271/19) for other approaches and information.
 

docs/documentation/introduction/architecture.md

@@ -15,7 +15,7 @@ Operaton can be used both as a standalone process engine server or embedded insi
 
 ![Process Engine Architecture](/img/documentation/introduction/process-engine-architecture.png)
 
-* [Process Engine Public API](../user-guide/process-engine/process-engine-api.md): Service-oriented API allowing Java applications to interact with the process engine. The different responsibilities of the process engine (i.e., Process Repository, Runtime Process Interaction, Task Management, ...) are separated into individual services. The public API features a [command-style access pattern](http://en.wikipedia.org/wiki/Command_pattern): Threads entering the process engine are routed through a Command Interceptor which is used for setting up Thread Context such as Transactions.
+* [Process Engine Public API](../user-guide/process-engine/process-engine-api.md): Service-oriented API allowing Java applications to interact with the process engine. The different responsibilities of the process engine (i.e., Process Repository, Runtime Process Interaction, Task Management, ...) are separated into individual services. The public API features a [command-style access pattern](https://en.wikipedia.org/wiki/Command_pattern): Threads entering the process engine are routed through a Command Interceptor which is used for setting up Thread Context such as Transactions.
 * **BPMN 2.0 Core Engine**: This is the core of the process engine. It features a lightweight execution engine for graph structures (PVM - Process Virtual Machine), a BPMN 2.0 parser which transforms BPMN 2.0 XML files into Java Objects and a set of BPMN Behavior implementations (providing the implementation for BPMN 2.0 constructs such as Gateways or Service Tasks).
 * [Job Executor](../user-guide/process-engine/the-job-executor.md): The Job Executor is responsible for processing asynchronous background work such as Timers or asynchronous continuations in a process.
 * **The Persistence Layer**: The process engine features a persistence layer responsible for persisting process instance state to a relational database. We use the MyBatis mapping engine for object relational mapping.
@@ -99,14 +99,13 @@ The Operaton web applications are based on a RESTful architecture.
 
 Frameworks used:
 
-* [JAX-RS](https://jax-rs-spec.java.net) based REST API
-* [AngularJS](http://angularjs.org)
-* [RequireJS](http://requirejs.org)
-* [jQuery](http://jquery.com)
-* [Twitter Bootstrap](http://getbootstrap.com)
+* [JAX-RS / Jakarta REST](https://jakarta.ee/specifications/restful-ws/) based REST API
+* [AngularJS](https://angularjs.org)
+* [RequireJS](https://requirejs.org)
+* [jQuery](https://jquery.com)
+* [Bootstrap](https://getbootstrap.com)
 
 Additional custom frameworks developed by Operaton hackers:
 
-* [operaton-bpmn.js](https://github.com/operaton/operaton-bpmn.js): Operaton BPMN 2.0 JavaScript libraries
 * [ngDefine](https://github.com/Nikku/requirejs-angular-define): integration of AngularJS into RequireJS powered applications
 * [angular-data-depend](https://github.com/Nikku/angular-data-depend): toolkit for implementing complex, data heavy AngularJS applications

docs/documentation/introduction/index.md

@@ -30,7 +30,7 @@ To give you an overview of Operaton, the following illustration shows the most i
 ## Modeler
 
 * [Operaton Modeler](../modeling-bpmn/index.md): Modeling tool for BPMN 2.0 and CMMN 1.1 diagrams as well as DMN 1.3 decision tables.
-* [bpmn.io](http://bpmn.io/): Open-source project for the modeling framework and toolkits.
+* [bpmn.io](https://bpmn.io/): Open-source project for the modeling framework and toolkits.
 
 ## Web Applications
 

docs/documentation/introduction/public-api.md

@@ -40,4 +40,4 @@ HTTP API (REST API):
 
 ## Backwards Compatibility for Public API
 
-The Operaton versioning scheme follows the MAJOR.MINOR.PATCH pattern put forward by [Semantic Versioning](http://semver.org/). Operaton will maintain public API backwards compatibility for MINOR version updates. Example: Update from version `1.0.x` to `1.1.x` will not break the public API.
+The Operaton versioning scheme follows the MAJOR.MINOR.PATCH pattern put forward by [Semantic Versioning](https://semver.org/). Operaton will maintain public API backwards compatibility for MINOR version updates. Example: Update from version `1.0.x` to `1.1.x` will not break the public API.

docs/documentation/introduction/third-party-libraries/index.md

@@ -15,12 +15,3 @@ This section covers third party libraries and their use in Operaton. It provides
 For selected third-party libraries that we consider especially noteworthy, this page describes their license terms and use in the Operaton artifacts.
 
 For legal reference and any other license-related aspects please refer to [Licences](../licenses.md).
-
-
-## Web Applications (Cockpit, Tasklist, Admin)
-
-### XLTS for AngularJS
-
-The Operaton web applications use a set of third-party libraries referred to as *XLTS for AngularJS* (technical names: `angular`, `angular-animate`, `angular-cookies`, `angular-loader`, `angular-mocks`, `angular-resource`, `angular-route`, `angular-sanitize`, `angular-touch`). XLTS for AngularJS follows a proprietary license called *EULA for the downstream recipient of XLTS for AngularJS* (short *XLTS for AngularJS – EULA*) that you can find [here](https://xlts.dev/angularjs/downstream-eula).
-
-This license imposes restrictions around distributing and reverse-engineering XLTS for AngularJS independently of Operaton artifacts. The license does otherwise not restrict how you can use and distribute the Operaton artifacts that include XLTS for AngularJS. You can find our rationale for using this library in [our blog post on ensuring the long-term maintenance of Operaton](https://camunda.com/blog/2022/02/ensuring-continuous-support-of-angularjs-in-operaton-platform-7-17/).

docs/documentation/reference/bpmn20/custom-extensions/extension-attributes.md

@@ -823,7 +823,7 @@ The following attributes are extension attributes for the `camunda` namespace `h
   <tr>
     <th>Possible Values</th>
     <td>
-      An expression which evaluates to a <code>java.util.Date</code>, <code>java.util.String</code> (<a href="http://en.wikipedia.org/wiki/ISO_8601">ISO 8601</a> formatted) or <code>null</code>, e.g., ```${dateVariable```
+      An expression which evaluates to a <code>java.util.Date</code>, <code>java.util.String</code> (<a href="https://en.wikipedia.org/wiki/ISO_8601">ISO 8601</a> formatted) or <code>null</code>, e.g., ```${dateVariable```
     </td>
   </tr>
   <tr>
@@ -1112,7 +1112,7 @@ The following attributes are extension attributes for the `camunda` namespace `h
   <tr>
     <th>Possible Values</th>
     <td>
-      An expression which evaluates to a <code>java.util.Date</code>, <code>java.util.String</code> (<a href="http://en.wikipedia.org/wiki/ISO_8601">ISO 8601</a> formatted) or <code>null</code>, e.g., ```${dateVariable```
+      An expression which evaluates to a <code>java.util.Date</code>, <code>java.util.String</code> (<a href="https://en.wikipedia.org/wiki/ISO_8601">ISO 8601</a> formatted) or <code>null</code>, e.g., ```${dateVariable```
     </td>
   </tr>
   <tr>

docs/documentation/reference/bpmn20/events/timer-events.md

@@ -39,7 +39,7 @@ Example:
 
 ### Time Duration
 
-To specify how long the timer should run before it is fired, a timeDuration can be specified as a sub-element of timerEventDefinition. It is possible to define the duration in two different [ISO 8601 Durations](http://en.wikipedia.org/wiki/ISO_8601#Durations) formats:
+To specify how long the timer should run before it is fired, a timeDuration can be specified as a sub-element of timerEventDefinition. It is possible to define the duration in two different [ISO 8601 Durations](https://en.wikipedia.org/wiki/ISO_8601#Durations) formats:
 <ul>
   <li>PnYnMnDTnHnMnS</li>
   <li>PnW</li>
@@ -55,7 +55,7 @@ Example (interval lasting 10 days):
 
 ### Time Cycle
 
-Specifies repeating intervals, which can be useful for starting process periodically, or for sending multiple reminders for overdue user tasks. A time cycle element can be in two formats. One option is the format of recurring [time duration](#time-duration), as specified by the [ISO 8601 Repeating Intervals](http://en.wikipedia.org/wiki/ISO_8601#Repeating_intervals) standard.
+Specifies repeating intervals, which can be useful for starting process periodically, or for sending multiple reminders for overdue user tasks. A time cycle element can be in two formats. One option is the format of recurring [time duration](#time-duration), as specified by the [ISO 8601 Repeating Intervals](https://en.wikipedia.org/wiki/ISO_8601#Repeating_intervals) standard.
 
 Example (3 repeating intervals, each lasting 10 hours):
 
@@ -71,7 +71,7 @@ Additionally, you can specify a time cycle using cron expressions, the example b
 0 0/5 * * * ?
 ```
 
-Please see the <a href="http://www.quartz-scheduler.org/documentation/quartz-2.1.7/tutorials/tutorial-lesson-06.html">CronTrigger Tutorial</a> for additional information about using cron expressions.
+Please see the <a href="https://www.quartz-scheduler.org/documentation/quartz-2.1.7/tutorials/tutorial-lesson-06.html">CronTrigger Tutorial</a> for additional information about using cron expressions.
 
 Note: The first symbol denotes seconds, not minutes as in normal Unix cron.
 

docs/documentation/reference/cmmn11/custom-extensions/operaton-attributes.md

@@ -386,7 +386,7 @@ The following attributes are extension attributes for the `operaton` namespace `
   <tr>
     <th>Possible Values</th>
     <td>
-      An expression which evaluates to a <code>java.util.Date</code>, <code>java.util.String</code> (<a href="http://en.wikipedia.org/wiki/ISO_8601">ISO 8601</a> formatted) or <code>null</code>, e.g., ```${dueDate```
+      An expression which evaluates to a <code>java.util.Date</code>, <code>java.util.String</code> (<a href="https://en.wikipedia.org/wiki/ISO_8601">ISO 8601</a> formatted) or <code>null</code>, e.g., ```${dueDate```
     </td>
   </tr>
   <tr>

docs/documentation/reference/forms/embedded-forms/controls/date-inputs.md

@@ -41,7 +41,7 @@ The Form SDK itself does not provide any custom components or widgets. As such i
 Inside Operaton Tasklist, datepicker support is provided through Angular UI.
 :::
 
-You can use the [Angular UI datepicker](http://angular-ui.github.io/bootstrap/)
+You can use the [Angular UI datepicker](https://angular-ui.github.io/bootstrap/)
 directive to offer a datepicker for the date input field. The complete markup of the input field
 including the datepicker button is shown below.
 

docs/documentation/reference/forms/embedded-forms/integrate/full-examples.md

@@ -10,7 +10,6 @@ menu:
 
 ---
 
-Full examples of how to integrate the Forms SDK in a custom application can be found in the [Operaton Examples Repository](https://github.com/operaton/operaton-bpm-examples) on GitHub.
+Current form examples are maintained in the [Operaton Examples Repository](https://github.com/operaton/operaton-examples) on GitHub.
 
-* [Example for standalone usage of the SDK](https://github.com/operaton/operaton-bpm-examples/tree/master/sdk-js/browser-forms)
-* [Example for standalone usage of the SDK with AngularJS Integration](https://github.com/operaton/operaton-bpm-examples/tree/master/sdk-js/browser-forms-angular)
+* [User task forms example](https://github.com/operaton/operaton-examples/tree/main/examples/user-task-forms)

docs/documentation/reference/forms/embedded-forms/integrate/getting-a-distribution.md

@@ -10,19 +10,14 @@ menu:
 
 ---
 
-# Manual Download
+# Source
 
-The Forms SDK library can be downloaded from
-[GitHub](https://github.com/operaton/bower-operaton-bpm-sdk-js/releases).
+The Forms SDK source is maintained in the
+[Operaton repository](https://github.com/operaton/operaton/tree/main/webapps/frontend/operaton-bpm-sdk-js).
 
-
-# Bower
-
-Alternatively, the Forms SDK can be installed using the Bower package manager:
-
-```
-bower install operaton-bpm-sdk-js --save
-```
+Operaton does not currently publish a standalone Bower package or a separate Bower release repository.
+Use the SDK files from your Operaton distribution, or build them from the source tree when embedding
+forms in a custom application.
 
 
 # Dependency Management

docs/documentation/reference/rest/overview/authentication.md

@@ -6,7 +6,7 @@ sidebar_position: 10
 ---
 
 
-The REST API ships with an implementation of [HTTP Basic Authentication](http://en.wikipedia.org/wiki/Basic_access_authentication). By default it is switched off, but can be activated by adding a servlet filter as follows:
+The REST API ships with an implementation of [HTTP Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication). By default it is switched off, but can be activated by adding a servlet filter as follows:
 
 ```xml
 <filter>
@@ -38,7 +38,7 @@ The authentication provider is exchangeable. You can implement the interface `or
 
 The authentication filter works fine whenever the JAX-RS application containing the REST API is deployed as a servlet. This is not necessarily the case. One such case we are aware of is with some types of RESTEasy deployments:
 
-RESTEasy allows deployment of a JAX-RS application as a servlet filter (see the [RESTEasy docs](http://docs.jboss.org/resteasy/docs/2.3.5.Final/userguide/html/Installation_Configuration.html#filter)). If you choose this method to deploy the REST API application, which we also do in the Tomcat distribution, the authentication filter requires an extra init-param named `rest-url-pattern-prefix`. The value has to correspond to the servlet path (see [HttpServletRequest#getServletPath()](http://docs.oracle.com/javaee/6/api/javax/servlet/http/HttpServletRequest.html#getServletPath%28%29)) as in the case that the JAX-RS application is deployed as a servlet.
+RESTEasy allows deployment of a JAX-RS application as a servlet filter (see the [RESTEasy docs](https://docs.jboss.org/resteasy/docs/2.3.5.Final/userguide/html/Installation_Configuration.html#filter)). If you choose this method to deploy the REST API application, which we also do in the Tomcat distribution, the authentication filter requires an extra init-param named `rest-url-pattern-prefix`. The value has to correspond to the servlet path (see [HttpServletRequest#getServletPath()](https://docs.oracle.com/javaee/6/api/javax/servlet/http/HttpServletRequest.html#getServletPath%28%29)) as in the case that the JAX-RS application is deployed as a servlet.
 
 Example: If the RESTEasy configuration is