The traditional Java API for Registries (JAXR) pro- vides a useful way for Java developers to use a single simple abstraction API to access a variety of registries. The unified JAXR information model (Infomodel), which describes content and metadata within registries, provides a simple way to access registries information. However, when a JAXR registry provider implements the OASIS (Organization for the Advancement of Structured Information)/ebXML Registry Services Specification, it internally works with ebXML Registry Information Model (RIM) objects which should be exposed as JAXR Infomodel objects. Furthermore, any application using ebXML RIM objects, before the access to the registry via a JAXR provider, has to convert them to the Infomodel counterpart. To deal with this problem, in this paper we suggest a new tool for the ebXML software development, which focuses on an extension of the traditional JAXR layer, providing the native use of ebXML RIM objects in client side applications with a direct access to the ebXML RIM SOAP service, and avoiding any conversion to/from JAXR Infomodel objects. The proposed approach reduces the developers duty, allowing them to focus exclusively on the ebXML objects use and it considerably speeds up the interactions with every ebXML registries.
JAebXR: a Java API for ebXML Registries for Federated Health Information Systems
Antonio Messina;Pietro Storniolo;Alfonso Urso
2015
Abstract
The traditional Java API for Registries (JAXR) pro- vides a useful way for Java developers to use a single simple abstraction API to access a variety of registries. The unified JAXR information model (Infomodel), which describes content and metadata within registries, provides a simple way to access registries information. However, when a JAXR registry provider implements the OASIS (Organization for the Advancement of Structured Information)/ebXML Registry Services Specification, it internally works with ebXML Registry Information Model (RIM) objects which should be exposed as JAXR Infomodel objects. Furthermore, any application using ebXML RIM objects, before the access to the registry via a JAXR provider, has to convert them to the Infomodel counterpart. To deal with this problem, in this paper we suggest a new tool for the ebXML software development, which focuses on an extension of the traditional JAXR layer, providing the native use of ebXML RIM objects in client side applications with a direct access to the ebXML RIM SOAP service, and avoiding any conversion to/from JAXR Infomodel objects. The proposed approach reduces the developers duty, allowing them to focus exclusively on the ebXML objects use and it considerably speeds up the interactions with every ebXML registries.I documenti in IRIS sono protetti da copyright e tutti i diritti sono riservati, salvo diversa indicazione.


