search

iay / mdq-server

Metadata Query Protocol server implementation using Shibboleth MDA
6 stars 6 forks source link

use different HTML template for /entities endpoint #16

Closed iay closed 10 years ago

iay commented 10 years ago

At the moment, when rendering results for a browser, we use the same template (queryResult.tpl). This means that, for example, the full signed XML document is included when returning the "everything" aggregate.

It would make more sense to use different HTML templates for each endpoint, and make the one for the "everything" aggregate not include the rendered metadata (perhaps always, perhaps if it exceeds a certain length).

It should also be possible to override each of the HTML templates from outside the executable bundle.

iay commented 10 years ago

It should also be possible to override each of the HTML templates from outside the executable bundle.

Looks like it is difficult to arrange for these to be individually overridden because the classpath resource loader doesn't work the way you might expect with Spring Boot's executable jar format. We may want to move away from using that in the long term, but for now it's easy to override all Groovy templates, though, by putting something like the following in an external application.properties:

spring.groovy.template.prefix=file:templates/

That's probably good enough for now.