Replies: 2 comments 1 reply
-
|
Hi @Ainges , Regarding your main pain point: the cibseven/cibseven:wildfly-2.1.0 Docker image apparently lacks the HTTP connector needed for using the REST API to deliver messages to the engine from outside a process. The Tomcat variant is very reliable for both the classic webapps and the full REST API, including the HTTP connector that enables straightforward access to the REST endpoints (e.g., for message correlation from external clients). On Quarkus
Docs for Quarkus integration (including REST usage): https://docs.cibseven.org/manual/latest/user-guide/quarkus-integration/ |
Beta Was this translation helpful? Give feedback.
-
|
Hi @Ainges, Just a quick update/follow-up on this topic: with the recent update for CIB seven 2.2.0-SNAPSHOT version, the HTTP connector is now working in the WildFly distribution. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Description:
Hi! I'm evaluating CIB Seven for my new project and I've run into a documentation gap. I've added the CIB Seven Quarkus Extension as a dependency and successfully deployed the engine. However, I cannot locate the UI endpoints.
Situation:
cibseven/cibseven:wildfly-2.1.0What I've tried:
http://localhost:8080/webapp/Questions:
Environment:
Beta Was this translation helpful? Give feedback.
All reactions