Dependency injection not working in webflows

I am having the same issue. My flow is:

    def runJobFlow = {
        create  {
            def myCurrentUser = springSecurityService.getCurrentUser()
            on("submit").to "setJobParams"
        }

        setJobParams {

        }
    }

A NPE is thrown on the springSecurityService use. The same exception is thrown when called outside of the start state block.

While in a non webflow action on the same controller

    def testJob = {
        def myCurrentUser = springSecurityService.getCurrentUser()
        render "Hello ${myCurrentUser.username} and ${scriptEngine}"
    }

that works just fine.

Scriptengine above was a resource in the springbeans resources.groovy that also does that same thing.

This is on grails 1.3.6 with webflow 1.3.7. Total show stopper for my use.

This is a blocking issue for me too... any ideas on where to begin trying to debug this? Can anyone who worked on this plugin shed some light?

This is a major issue for me as it completely breaks webflow. Has there been any update on this issue at all? I am using grails 1.3.7 and webflow 1.3.7

Are you using customized bean names or overriding the wiring on your controller?

The webflow plugin has a strange behavior where it overrides the delegate resolution on your closure. Any property references within your flow actually get resolved first to getBean() calls against the ApplicationContext, not actually to the wired properties of the controller. They'll only hit controller variables if that getBean() call fails. (This made altering the dependencies for integration testing purposes rather difficult for us.)

I am not doing anything unusual. my service bean is called eisService and the class name is EisService. If I call the injected service from an action it works perfectly but I get an NPE if I call it from within the webflow.

I was wondering was their any update on this issue. I cannot use the webflow plugin in its current state.

Also having issues with this so adding my vote to raise the priority... Is this only an issue with the latest version of the plugin? It seems like a fairly important requirement to have working. Is there a work around of any sort?

A workaround is to make your controller an InitializingBean with "implements InitializingBean {"

And then you can use a method like this:
def flowService
def service
def flowController

void afterPropertiesSet()

in your flow you should be able to access flowService, which will be what should be injected for "service"

This is what worked for us using grails/webflow 1.3.7

I marked springSecurityService as transient and all my custom services as flow scoped.

class SubscribeController {
    // NOTE: Needs to be transient to exist in webflow.   -tak May 2011
    def transient springSecurityService

    // injection of account info API  (service is static scope="flow")
    def accountService

    // injection of subscription API  (service is static scope="flow")
    def subscribeService

    /**
     *  Join/Subscribe Flow - usher the user through some data collection and finally trigger a user creation
     *  and subscription purchase
     *
     */
    def joinFlow = {
    ...
       firstPage { ...  }
       on("submit") {
          ...
          def isLoggedIn = springSecurityService.isLoggedIn()
          ...
       }
    ...
    }

this seems to avoid springSecurityService being NPE'd inside the flow.

I'm using this workaround

class CheckoutController {

    def checkoutFlow = {

        action {
            ShoppingService shoppingService = grailsApplication.mainContext.getBean('shoppingService')
        }
    }
}