7. Upgrading from 5.1

Up one level

GRIA 5.1 to 5.2 developer kit migration guide

This guide is for people who developed services using the 5.1 developer kit and who wish to update their services to use the 5.2 framework.

Note that GRIA is compatible at the SOAP layer between these versions, so there is no need to upgrade just to interoperate with the newer services. However, upgrading may simplify your code or give access to new features.

If your service was developed using the 5.0.1 developer kit, then please first follow the 5.0.1 to 5.1 migration guide.

Renaming (classes and jars)

REQUIRED

Some of the support jars and poms have been renamed.

1. The top-level dev-kit pom's parent should be changed from org.gria:gria to org.gria:infra, and the version changed to 5.2.
   
2. The org.gria:gria-client-staterepos jar no longer exists (it is now included in infra-common). Any dependencies on it in pom.xml files should be removed.
   

Atom feed

REQUIRED

To support some oddities in Microsoft's Internet Explorer browser, the XHTML generated for the Atom feed should no longer have an "x:" prefix before the elements.

Web administration

REQUIRED

In 5.1, the web interface used an iframe for the main part of the page. This caused problems with MSIE. In 5.2, iframes are not used and each page should instead <jsp:include> the header and footer jsps. See the sample JSP pages for an example.

Also, your web.xml file must add a new listener. This is for the new JBoss support, but it is required even when not using JBoss:

  <listener>
    <listener-class>uk.ac.soton.itinnovation.grid.service.utils.ContainerListener</listener-class>
  </listener>

Signallable interface

OPTIONAL

If your service had methods whose only action was to send signals to PBAC, these can be removed and the new Signallable interface implemented instead. See Other modifications for details.