Grails

Interceptors cannot reference services, results in NPE

Details

  • Type: Wish Wish
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 0.4
  • Fix Version/s: 0.6-RC1
  • Component/s: None
  • Labels:
    None

Description

This is a major inconvenience if you want common reloadable code in a service (for example) assigned to an interceptor as you get the interceptor to run even if you implement InitializingBean and init the interceptor there.

You have to make all your code static in the service

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Marc Palmer added a comment -

Rolled over to 0.5.5 to get a stable JavaOne release out

Show
Marc Palmer added a comment - Rolled over to 0.5.5 to get a stable JavaOne release out
Hide
Permalink
Graeme Rocher added a comment -

I believe the issues with this is that interceptors are closures the bindings for which are initialised before the properties are set. The workaround is to use owner.testService instead of testService so that the interceptor asks the owner for the testService rather than binding it locally

We should doc this of course, but i'm not sure if there is much we can do about the real problem

Show
Graeme Rocher added a comment - I believe the issues with this is that interceptors are closures the bindings for which are initialised before the properties are set. The workaround is to use owner.testService instead of testService so that the interceptor asks the owner for the testService rather than binding it locally We should doc this of course, but i'm not sure if there is much we can do about the real problem

People

  • Assignee:
    Graeme Rocher
    Reporter:
    Marc Palmer
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: