Migration to version 0.1.17

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.

  • API changes
    1. The components of the WSRF stack were moved to a separate module. This is done in order to enable implementations to use the WSAG4J engine also with other WSRD stacks, such as Globus or WSRF-Lite. You can also use it with other remoting techniques.
    2. The name of the packages org.ogf.graap.wsag.server.wsrf.* has changed to org.ogf.graap.wsag.wsrf.*. This is part of the separation of WSAG4J engine and WSRF stack. If you want to migrate an older wsrf-engine.config file, you should adjust the FactoryImplementation configuration section to point to the class org.ogf.graap.wsag.server.engine.GenericAgreementFactory. If you have changed the web.xml you need also to change the implementation class of the WSAG4J servlet to org.ogf.graap.wsag.wsrf.bootstrap.Bootstrap. A general search for the string org.ogf.graap.wsag.server.wsrf could also help you to find the configuration files that are affected by this API change.

Migration to version 0.1.15

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.

  • Refactoring of the client API

    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.

  • New EPR address of WSAG4J engine

    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.

  • API changes
    1. The AgreementFactoryLocator was renamed to AgreementFactoryRegistryLocator.
    2. org.ogf.graap.wsag.server.exceptions.ActionInitializationException was moved to org.ogf.graap.wsag.server.api.ActionInitializationException
      • Streamlined creation of WSAG4J API types

        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.

      • Configuration changes
        1. Updated wsag4j-velocity.properties (replace it with current version)