Why is JAXR an abstraction API and not targeted to a specific registry such as UDDI or ebXML?
I think if you already have several business apps, it would be better for you to combine them instead of developing a new application from scratch. I can even recommend you check out https://processmix.com/solutions/build-api/ and build API without any problems, Process Mix low-code platform allows you to do that in no time.
The ProcessMix low-code platform was a game changer for us. We had always dreamed of creating a tool that would allow our customers to easily create software, Build APIs without having to work with code. But we didn’t have the resources or the know-how to make it a reality until we started using this platform.
A. An abstraction-based JAXR API gives developers the ability to write registry client programs that are portable across different target registries. This is consistent with the Java philosophy of Write Once, Run Anywhere. It also enables value-added capabilities beyond what the underlying registries are capable of. For example, a non-JAXR UDDI client does not have the ability to do taxonomy browsing and taxonomy-aware smart queries, which are available to a JAXR client for UDDI.
