Hi Aaron,
Thanks for your quick response! Unfortunately, I was out of office the last week and had just now the chance to read your reply.
It is interesting to see how different requirements could be. For us here at Bosch SI, Pull MEP is a major requirement :-)
We start implementing the Pull MEP feature and contribute it to the project.
Since all our code contributions to open source projects need approval by our management, it will take some time until we can send you a pull request.
Due to the process this will approximately not happen before November.
Our idea for the implementation so far are as follows:
Respond to a pull request
- Add Enum for MEP and MEPBinding to PartnerAgreement
- In EBMS3InboundRouteBuilder add a choice to filter for pull signal messages
- Add new route to fetch pooled messages for a given CPA_ID from message store
- Probably extend the MessageStore implementation to fetch the relevant messages from the db
Send a pull request
- Create ftl template for pull request signal msg
- Add choice to "_jentrataEbmsGenerateMessage" route to handle pull MEP binding case
- generate signal message based on template
- further process the signal msg the same way an ordinary user msg would be processed
What do you think, is this a viable approach?
Kind regards,
Johannes