product-apim VS mustangserver

The paradox situation is that there is an overwhelming amount of work, not because everything is so hard, but because everything is so easy. There is still a lot to learn, and to do, our Dockerfile is a mess. API management wise I only just had a glance at WSO2, which looks really promising).

ZUGFeRD (more info)  is an e-invoice standard and has been renamed to Factur-X after the french also adopted it. I'm Jochen and I call myself "Mustangproject.org Chief ZUGFeRD Amatuer"Factur-X is an open European standard for B2G, B2B and B2C invoices embedding machine-readable XML invoices into human-readable PDF files. And yes, that's EN16931 compliant, i.e. eligible for European B2G invoices.     To support that in my Java accounting application, I had created an open-source library called Mustangproject. That library evolved into a toolkit and now also has a command line application . In 2019, I also published an open-source proof of concept to test the feasibility of a Java framework called Dropwizard  as a REST API server for Mustang, which was then still 1.x. Dropwizard allows you to create REST APIs in Java, so that your functionality can be accessed over the network, centrally maintainable and basically independent of the client development language. The results were promising, even transferring whole files was possible, which was necessary to extract from PDFs and merge PDFs and XML. This article is about how easy it is to write APIs in Java if you already have some functionality to publish.