Grails

Provide a way to render views outside of controllers and taglibs.

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Duplicate
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None

Description

This comes up quite often and many plugins implement their own version of this. It's not as trivial as it might appear at first glance as their are certain considerations such as encoding, stream copying and request binding to take care of.

First thoughts on API would be a new bean (e.g. gspRenderer) that exposes a render() method that has similar semantics to the render() method available on controllers.

Plugins such as mail, rendering etc. that write their own version of this should be encouraged to use this new API.

Issue Links

duplicates

New Feature - A new feature of the product, which has yet to be developed. GRAILS-3818 Make rendering operations (views, templates etc.) possible on non request threads and from services and other beans

  • Blocker - Blocks development and/or testing work, production could not run.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
is related to

Improvement - An improvement or enhancement to an existing feature or task. GRAILS-5560 GroovyPagesTemplateEngine does not cache compiled templates for several variants of createTemplate

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Luke Daley added a comment -

These two issues are related in that pragmatically only one of them needs to be implemented.

If it is not practical to render views without a request environment, there should be a centralised, supported, way of doing this on non request threads.

There are several plugins that do this (quartz, mail, rendering) and they ALL do it wrong.

Show
Luke Daley added a comment - These two issues are related in that pragmatically only one of them needs to be implemented. If it is not practical to render views without a request environment, there should be a centralised, supported, way of doing this on non request threads. There are several plugins that do this (quartz, mail, rendering) and they ALL do it wrong.
Hide
Permalink
Juri Kuehn added a comment -

Are there any specific plans on how to implement this? If you say "provide a way to render views", does it also imply any other taglib usage?

In jobs and services without a bound web-request i usually need to

  • render gsp files
  • create links, resolve i18n messages
  • change locale before calling those taglib methods (sending multiple localized emails for example)

A "gspRenderer" bean has been proposed. I suggest to call it grailsTaglibManager or alike (something like this already exists?). It would then provide methods to:

  • retrieve specific taglibs
  • easily change the locale

Before returning a taglib, it could check for a web-request, if there is none, setup a working environment. Taglib methods that need a real web-request would throw an exception if there is none.

These two issues are related in that pragmatically only one of them needs to be implemented.

+1 for merging GRAILS-6809 and GRAILS-3818

Show
Juri Kuehn added a comment - Are there any specific plans on how to implement this? If you say "provide a way to render views", does it also imply any other taglib usage? In jobs and services without a bound web-request i usually need to render gsp files create links, resolve i18n messages change locale before calling those taglib methods (sending multiple localized emails for example) A "gspRenderer" bean has been proposed. I suggest to call it grailsTaglibManager or alike (something like this already exists?). It would then provide methods to: retrieve specific taglibs easily change the locale Before returning a taglib, it could check for a web-request, if there is none, setup a working environment. Taglib methods that need a real web-request would throw an exception if there is none. These two issues are related in that pragmatically only one of them needs to be implemented. +1 for merging GRAILS-6809 and GRAILS-3818
Hide
Permalink
Graeme Rocher added a comment -

Bulk closing bunch of resolved issues

Show
Graeme Rocher added a comment - Bulk closing bunch of resolved issues

People

  • Assignee:
    Unassigned
    Reporter:
    Luke Daley
Vote (9)
Watch (6)

Dates

  • Created:
    Updated:
    Resolved: