239: the wiki in plain English Shorter sentences, one thought each, and common words, as the section "How we write" of AGENTS.md asks. The meaning, the headings and every link target stay as they were. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lxo4MXbp6VPoDkUrTBNXJ1
docs: what becomes of a shared value, on a page of its own The question "what happens to the values my aggregate shares" is now answered by one page per adapter wiki, with the same four questions in the same order, so two BPMS can be read side by side. This adapter said nothing so far, which let a reader assume it behaves like Camunda 7. The answer here is short and it is an admission: the Process-Engine-API carries a payload as a map and says nothing about how an engine behind it keeps one, so this adapter cannot tell you and cannot warn you either. What is pinned down is the in-memory mock, which hands back the objects it was given. The page ends with the measurement to run against the engine you really use. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RYPiyZ32jQQhqYKx44cw23
docs: the configuration page starts where a newcomer starts The properties and the shape of the BPMN model are what somebody needs who has just added this adapter, so both come first now. Which engine sits behind the API, how the workflow modules are kept apart and what a subscription asks for follow behind them. Nothing was removed; the sections changed places. Every page carries a numbered table of contents. On the configuration page and on Home each entry says what its section answers; on the deviations page it does not, because every heading there is already that sentence. Where a first heading only repeated the page title GitHub prints above the page, it is gone and the page begins with its first sentence. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
docs: a dependency example carries the version you can paste The rule is about prose: a version named in a sentence reads 2.0, the release line without a patch digit. A Maven or Gradle coordinate is not prose - it is copied into a build, where 2.0 resolves to nothing - so the examples carry 2.0.0 again, and the Camunda 8 ones 2.0.0-8.9, with the suffix naming the cluster minor the artifact was built against. The sentence which told the reader to fill in a patch himself is gone with it; where it is useful to know which patches exist, the pages link Maven Central instead. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CvgyhjwTEh834mwbptZZxh
docs: versions in the examples read 2.0 Without a patch digit and without -SNAPSHOT, and Getting started says once what that means for a build. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CvgyhjwTEh834mwbptZZxh
Story 55: trim the wiki to configuration and deviations The wiki now carries only what a user of this adapter needs and the main VanillaBP wiki cannot tell them: how to configure it, how to plug in a real engine, what the BPMN model has to look like, and where the Process-Engine-API does not carry a VanillaBP feature. Workflow-tasks, Message-correlation, Transactional-behavior and Viewing-workflows are gone. Their user-facing parts moved into Configuration, the rest is contributor material which GAPS.md and the README already carry. New page Deviations turns the gaps into one sentence each, linking the GAPS.md entry with the full reasoning. Three of them were missing from the wiki entirely: starts the engine performs itself, the end of a workflow and aggregateChanged.
Make the pages read less like generated text Em dashes in prose replaced by proper punctuation, promotional and filler phrasing removed, boldface reduced to where it aids scanning. Wording only, no statement about the adapter's behavior was changed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
A name-clash-avoidance mode has to be chosen (story 35) The Process-Engine-API offers no isolation of its own, so VanillaBP's default cannot be served here: - Home: the minimal configuration carries the mode, with the reason the boot fails without one; - Configuration: new section "Keeping workflow modules apart" - the mode table (by-adapter unsupported, use-prefix rewrites the deployed BPMN itself because the API has no model type, none scopes nothing) and the note that prefixing is transparent; - Workflow-tasks: with prefixed task definitions the subscriptions are unique per process, so routing a delivered task no longer depends on the 'bpmnProcessId' meta entry.
Document convention over configuration (story 34) The minimal configuration becomes 'add the dependency': adapter, workflow modules and the BPMN location are derived from the classpath. What deviates is documented where it belongs - what makes two adapter ids of this type distinct, and (Camunda 7) the new 'table-prefix' plus the rule that several datasources demand an explicit 'data-source-name'.
Document the viewing API (story 26) New page 'Viewing workflows': the three read-only ProcessService methods, the call-activity drill-down via the secondary history context, the opaque (adapter-namespaced) process definition ids and the guiding errors - linked from Home.
Explain why Quarkus needs at least one property per section The startup now reports the behavior itself, so the caveat says what the message says. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Show the minimal, convention-based configuration An adapter id which IS the adapter type needs neither a 'type' property nor a 'prioritized-adapters' list. Home now shows that variant first and the custom-id variant afterwards. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Document the Process-Engine-API adapter Home now explains what the adapter is, how to add it on Spring Boot and Quarkus, the minimal configuration, and links to the BPMN documentation as well as to the VanillaBP wiki. Added the pages Configuration, Workflow tasks, Message correlation and Transactional behavior carrying the BPMS-specific content moved out of the VanillaBP wiki, plus a custom footer with the VanillaBP logo and the license notice. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Initial Home page