Version 0.1.17 contains some changes in the API and configuration. This guide should help you in adopting these changes to existing wsag4j implementations.
Version 0.1.15 contains significant changes in the API and configuration. This guide should help you in adopting these changes to existing wsag4j implementations.
The client API has moved to the wsag4j-api module. By that, the package names have changed to org.ogf.graap.wsag.api.client. In general, implementations need to update the imports accordingly.
The URL used to access a WSAG4J server has changed to the URL of the installed web-application. It is not required anymore to add the "/services" suffix to the web-application URL when creating a EPR to lookup the agreement factories of a WSAG4J service. This behavior is more intuitive for new users, since they can check the correctness of WSAG4J installation via the Axis2 status pages and use the same URL to access the WSAG4J server.
This also affects the configuration of the WSAG4J engine. The gateway URL configured for a WSAG4J engine must not contain the trailing "/services" anymore.
The instantiation of the WSAG4J API was refactored in order to have a more consistent procedure to instantiate types from the org.ogf.graap.wsag.api.types package. In general, these types are instantiated by passing the corresponding XML types to their constructor. Internally a new copy of the base XML type is created. You can retrieve the internal XML representation of the object by calling the getXMLObject() method.