Replies: 3 comments
-
|
For me the word "plugin" suggests a functional extension to the framework. For things like custom code, configurations, and frontend-end, etc. perhaps "library" is a better name? I have been experimenting with this library concept for a while now. So far, the most straight forward way I found was to leverage Maven as package manager. This fits well with existing and most commonly used integration project structures. The biggest issue with a library concept at the moment is the lack of a mechanism to define "function blocks" (composite sender) and not being able to define an interface for such a thing (expected input, output, sessionkeys, formats, document behavior, etc.). Also, current tooling is lacking in features that are necessary for proper fine-grained unit-testing of these "funtion blocks". Connectors for things like Kafka, Slack, Keycloak, etc. I can see implemented as plugins. At the same time, I can't think of any good enough reason to offset the added complexity and work that comes with a plugin mechanism. A developer has to do extra configuration work to get something that should be already availabable by default. The only reason I can think of for a plugin mechanism would be to provide an interface for external parties, so that they can implement a connector for their product. |
Beta Was this translation helpful? Give feedback.
-
|
Good idea! We have several database oriented jobs that do delayed error resending or record retention and found ourselves copy-pasting these adapters everywhere. Some weeks ago we've experimented with writing a 'plugin' to do the delayed retry, in order to not relay on EAR deployments, we decided to use a parent classloader to set the required xml files & properties, it works but it took some time to get it working and feels like it should be easier. |
Beta Was this translation helpful? Give feedback.
-
|
You can follow #3270 to see the status of this epic. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We have added the plugin directory, allowing a developer to create a plugin for the Frank!Framework.
Plugins can consist of Frank!Framework configurations, java code and frontend code.
To help developers to create plugins, we will need to have some guidelines and some documentation.
For me, a good start would be:
next steps could be:
Beta Was this translation helpful? Give feedback.
All reactions