RELEASE-NOTES.md

Release Notes

0.1.3 (xxxx-xx-xx)

0.1.2 (2017-02-21)

• New features:
  • A REST filter feature has been introduced in terrestris#216 which allows basic/simple filtering based on primitve fields of (arbitrary) entities.
• Changes:
  • Connection pooling has been replaced by HikariCP. Beside that HikariCP outperforms c3p0 insofar as performance is concerned, the major advantage is that there are less (required) parameters to tweak which makes the configuration of the connection pooling much simpler. Please take care of differing artifactId depending on your Java version
  • The HttpUtil now offers the possibility to add custom HTTP headers to requests: terrestris#218
  • The Shogun2PermissionEvaluator can now be configured to use the plain Principal object from the spring security context (instead of always fetching a full SHOGun2-database user object): terrestris#229
• Upgrade notes to get projects based on v0.1.1 running with v0.1.2:
  • Copy file hikari.properties from here to src/main/resources/META-INF/ in your existing project.
  • Replace the c3p0-based shogun2DataSource in the {{your-project}}-context-db.xml file (under src/main/resources/META-INF/spring/) by the one based on hikari as it is defined in the archetype. Make sure also to add the bean hikariConfig from the archetype.

0.1.1 (2016-10-26)

• New features:
  • Some tree models have been introduced. See terrestris#208 for details.
  • HttpUtil methods can now also be called with intances of Credentials interface
  • A new web interface for the easy creation of ExtJS locale JSON files (based on CSV files) has been added. See this PR for details: terrestris#213

0.1.0 (2016-09-05)

• Changes:
  • Permission.WRITE has been renamed to Permission.UPDATE
  • A new permission Permission.CREATE has been introduced
  • The saveOrUpdate method of the AbstractCrudService now has a more secure permission/authorization annotation. The CREATE case is currently not respected in the permission evaluators of SHOGun2 and should be handled in project specific implementations.
  • The saveOrUpdate method of the services are now void. Existing projects that are using this method may need some simple adaptions like changes from PersistentObject newObject = object.saveOrUpdate() to object.saveOrUpdate()
  • The webapp-archetype has been extended to demonstrate how custom permission evaluators for project specific solutions can be used.
  • All Response-interceptors from the package de.terrestris.shogun2.util.interceptor now have a new parameter MutableHttpServletRequest request. This makes sense as the request object contains basic information that may be necessary in custom implementations of a response interceptor.
• New features:
  • All PersistentObjects now have a set of user and group permissions, i.e. all entities can be protected if needed. In this context, the permission evaluators have been overhauled. The database structure has changed here, which means that existing projects are affected by this change and would need a data migration if they can not boot in a vanilla state (with hibernate.hbm2ddl.auto=create).
  • An AbstractPermissionAwareCrudService has been introduced. This service provides useful methods to add and remove permissions for certain objects. PermissionCollections will be persisted in the database when using these methods. All services should extend the abstract service mentioned above. There is only one exception: The PermissionCollectionService does NOT extend this service as the AbstractPermissionAwareCrudService gets the PermissionCollectionService injected, which would not work when the PermissionCollectionService would try to inject itself. On top of that it does not make sense to secure PermissionCollections with PermissionCollections and so on...

Existing projects (that were possibly created with an old version of the webapp archetype) need adaptions regarding the following points:

• Adapt the pom.xml of your existing SHOGun2 project
  • Remove the dependency with the artifactID shogun2-web
• Adapt the existing {{your-project}}-context-initialize-beans.xml file (under src/main/resources/META-INF/spring/) according to the new structure as it is defined in the archetype
• Adapt the existing {{your-project}}-context.xml file (under src/main/resources/META-INF/spring/) according to the new structure as it is defined in the archetype
• Add the missing geoServerNameSpaces.properties file to src/main/resources/META-INF/, like the one in the archetype
• Remove all occurences of <property name="type" value="Tile" /> in the {{your-project}}-context-initialize-beans.xml file (under src/main/resources/META-INF/spring/)
• Add http.timeout=30000 to the {{your-project}}.properties file (under src/main/resources/META-INF/)
• If there are already custom implementations of one of the response interceptors from the package de.terrestris.shogun2.util.interceptor in your project, these methods need the new parameter MutableHttpServletRequest request in their signature.

0.0.6 (2016-04-06)

• All EXT-Direct related stuff has been removed. Existing projects (that were possibly created with an old version of the webapp archetype) need adaptions regarding the following points:
  • Remove all annotations of type ch.rasc.extclassgenerator.Model
  • In the file src/main/resources/META-INF/spring/{{your-project}}-context.xml:
    • The package ch.ralscha.extdirectspring can be removed from the <context:component-scan> element.
    • <bean id="modelPackageCandidates" class="java.util.ArrayList"> can be removed
  • In the file src/main/webapp/WEB-INF/{{your-project}}-servlet.xml, the package ch.ralscha.extdirectspring can be removed from the <component-scan> element.
  • In the file src/main/webapp/WEB-INF/log4j.properties, the config for log4j.logger.ch.ralscha.extdirectspring can be removed
  • In the file src/main/webapp/WEB-INF/web.xml, the <servlet-mapping> with <url-pattern>/action/*</url-pattern> can be removed
• Existing projects should (once) boot with the hibernate.hbm2ddl.auto property set to UPDATE or CREATE to make use of the new tables ABSTR_LAYERS_USERPERMISSIONS and ABSTR_LAYERS_GROUPPERMISSIONS (#155).