Overview Middleware4j: Difference between revisions
No edit summary |
No edit summary |
||
| (7 intermediate revisions by the same user not shown) | |||
| 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. | [[Category:Middleware4j]] | ||
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: | [[file:Middleware4j_animated.gif|800px]] | ||
Latest revision as of 13: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.
