Skip to content

Conversation

@hhund
Copy link
Member

@hhund hhund commented Nov 25, 2025

closes #400
closes #397
closes #395
closes #393
closes #391
closes #388
closes #387
closes #385
closes #383
closes #382
closes #378
closes #373
closes #372
closes #367
closes #365
closes #353
closes #349
closes #347
closes #346
closes #344
closes #341
closes #338
closes #332
closes #331
closes #325
closes #317
closes #315
closes #309
closes #307
closes #301
closes #297
closes #296
closes #292
closes #284
closes #281
closes #271
closes #270
closes #268
closes #241
closes #239
closes #210
closes #209
closes #208
closes #207
closes #206
closes #205
closes #204
closes #203
closes #202
closes #201
closes #200
closes #197
closes #177
closes #81
closes #78

hhund added 30 commits September 5, 2025 17:59
issue/346_347_ProcessPluginDefinition_Access_-_BPMN_Activity_Beans
'origin/issue/346_347_ProcessPluginDefinition_Access_-_BPMN_Activity_Beans'
into develop_2
issue/349_Data_Compression_Service
* mockito-core configured as java agent for tests
Fixed inconsistent StructureDefinition snapshot handling. Internal
resource created and updated events now always include snapshots. HTTP
responses include snapshots if the StructureDefinition resource in the
POST or PUT request included a snapshot. New integration test to verify
behavior.
* New dsf-common-oidc maven module with base oidc client
* Reworked bpe server oidc client to be based on common base client
* Reworked BackChannelLogoutAuthenticator and BearerTokenAuthenticator
to used common oidc client, authenticators now also support tokens
sigend with EC keys
* New config parameter to set oidc token audience (aud) to validate
bearer tokens, default uses oidc client-id
@implNote is used in the JDK and not standardized
* Code changes to switch from classes in org.camunda packages to
org.operaton.
* Added special class loader for API v1 process plugins compiled against
camunda classes. Implementation uses ASM to rewrite class byte code
before defining classes.
* maven-plugin-plugin workaround, included ASM dependency does not
support Java 25, manually configured dependency to use ASM version 9.8
* impsort-maven-plugin workaround, included
com.github.javaparser:javaparser-core dependency does not support Java
25, set ignoreParseErrorsBelowImports option to true
* removed async logging during test execution, no performance advantage
and removes deprecated used of sun.misc.Unsafe warning during build
* Upgrade from azul/zulu-openjdk:21-jre-headless to
azul/zulu-openjdk:25-jre-headless
* Hats off to the Azul team for making Java 25 docker images available
just 24 hours after its official release
* Changed unused variables to unnamed variables (underscore)
* Some code cleanup
hhund added 21 commits November 20, 2025 23:44
- New dsf-bpe-process-api-v1-base and dsf-bpe-process-api-v1-operaton
modules.
- Modules dsf-bpe-process-api-v1 and dsf-bpe-process-api-v1-operaton
have dependencies to dsf-bpe-process-api-v1-base.
- Code with dependency to Operaton or Camunda now lives in
dsf-bpe-process-api-v1 and dsf-bpe-process-api-v1-operaton respectively,
code without Operaton or Camunda dependency in
dsf-bpe-process-api-v1-base.
- The dsf-bpe-process-api-v1-base module is shaded into
dsf-bpe-process-api-v1 and dsf-bpe-process-api-v1-operaton.
- Added rewrite of
org.camunda.bpm.model.bpmn.instance.UserTask.getCamundaFormKey() to
org.operaton.bpm.model.bpmn.instance.UserTask.getOperatonFormKey().
Method is used in DefaultUserTaskListener and thus may also be used
special code written by process plugin developers.
- Rewrite not needed for DefaultUserTaskListener as it lives in
dsf-bpe-process-api-v1-operaton module.
Not upgrading to HAPI 8.6.0: NullPointerException while validating due
to bug in cache code.
- Change does not make a difference in validation but improves DSF
implementation guide readability
- Added special case to BundleGenerator for ignoring hl7 base profiles
during cycle detection
issue/400_1.9.0_to_2.0.0_Transition
'origin/issue/400_1.9.0_to_2.0.0_Transition' into develop
Process models in DSF 1.x where deployed without the process API version
as tenant-id. If an process is updated on DSF 2.x it is deployed with
the process API version as tenant-id. The "getProcessDefinition" method
select the process definition with the highest internal version but
needs to sort by tenant-id first to preferentially select processes with
tenant-id.
Except CodeSystem urn:ietf:bcp:13 and ValueSet
http://hl7.org/fhir/ValueSet/mimetypes both dates based on last update
from IANA
@hhund hhund added this to the 2.0.0 milestone Nov 25, 2025
@hhund hhund requested a review from schwzr November 25, 2025 19:03
@hhund hhund self-assigned this Nov 25, 2025
Copy link

@github-advanced-security github-advanced-security bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CodeQL found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.

@hhund hhund marked this pull request as ready for review November 25, 2025 19:06
version management for outdated HAPI dependency nimbus-jose-jwt
@hhund hhund merged commit aaaab0f into main Nov 26, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment