Overview Middleware4j: Difference between revisions
Created page with "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 file:middleware_animation1.gif" |
No edit summary |
||
| Line 2: | Line 2: | ||
[[file:middleware_animation1.gif]] | [[file:middleware_animation1.gif]|800px] | ||
Revision as of 14:33, 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
[[file:middleware_animation1.gif]|800px]