Overview Middleware4j: Difference between revisions
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 3: | Line 3: | ||
See [[Middleware4j Example Configuration|Example Configuration]] | See [[Middleware4j Example Configuration|Example Configuration]] | ||
[[file:Middleware4j_animated.gif | |||
[[file:Middleware4j_animated.gif|800px]] | |||
Latest revision as of 14:16, 26 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.
