Overview Middleware4j: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Commander4j Middleware was originally designed as a add-on component to the Commander4j core application, however there are no dependencies and it can be used standalone in a traditional middleware role to link to otherwise incompatible systems by translating messages between different formats. See [[Example Configuration]] | Commander4j Middleware was originally designed as a add-on component to the Commander4j core application, however there are no dependencies and it can be used standalone in a traditional middleware role to link to otherwise incompatible systems by translating messages between different formats. See [[Middleware4j Example Configuration|Example Configuration]] | ||
[[file:middleware_animation_800px.gif|800px]] | [[file:middleware_animation_800px.gif|800px]] | ||
Revision as of 14:37, 23 August 2024
Commander4j Middleware was originally designed as a add-on component to the Commander4j core application, however there are no dependencies and it can be used standalone in a traditional middleware role to link to otherwise incompatible systems by translating messages between different formats. See Example Configuration
