Hey there, let's break down this frustrating issue you're hitting while following that 4-year-old Udemy mastering-grails course. That error is a classic sign your Customer domain class isn't being accessed within a properly initialized Grails application context—and given the course's age, version mismatches are almost certainly a key factor here. Here are actionable steps to fix this:

1. Align Your Grails Version with the Course #

Grails has undergone major changes in 4 years (think Grails 3.x vs. 4/5/6). If you're running a newer Grails version than the one the instructor used, core APIs and application lifecycle behavior will differ, even if your code looks identical.

• First, check what Grails version the course uses (the instructor probably mentions it early on, or you can spot it in their terminal/IDE).
• Use a version manager like SDKMAN to install that exact version:

  sdk install grails <course-grails-version>
  sdk use grails <course-grails-version>
  

• Rebuild your project with this version—this alone might resolve the context initialization issue.

2. Ensure You're Calling the Domain Class Within Grails Context #

The error explicitly says the method was used outside a Grails application. Ask yourself:

• Are you trying to run a standalone script or main method that calls Customer queries directly? Grails domain classes rely on the app's persistence context, which isn't available outside the Grails runtime. Move your query code to a Grails service, controller, or the Bootstrap.groovy file (which runs on app startup).
• If you're writing tests: Older Grails courses used deprecated testing mixins like grails.test.mixin.TestFor. Newer versions require proper annotations to initialize the context. For integration tests, add @Integration to your test class; for unit tests mocking domain classes, use @Mock(Customer) alongside the appropriate test annotations.

3. Verify Domain Class Configuration #

Even if your code matches the instructor's, subtle changes in Grails' domain class handling might be tripping you up:

• Double-check that Customer.groovy lives in the grails-app/domain/rewards_grails directory—Grails auto-scans this folder for domain classes, so a misplaced file won't be registered in the context.
• Ensure there are no typos in the package name (rewards_grails) or class name—even a small mistake can prevent Grails from recognizing the domain class.

4. Clean and Rebuild Your Project #

Stale build artifacts can cause weird context issues, especially when switching versions. Run these commands to start fresh:

grails clean
grails compile
grails run-app

5. Temporary: Manually Initialize Context (For Debugging) #

If you need to test queries outside the standard Grails flow (e.g., a quick script), you can manually bootstrap the context (note: this is for debugging only, not production code):

import grails.util.Holders
import rewards_grails.Customer

// Initialize Grails context if not already active
if (!Holders.grailsApplication?.isInitialized()) {
    // Adjust this line based on your Grails version—older versions may use GrailsApp.run()
    grails.util.GrailsUtil.initialize()
}

// Now you can execute your query
def customer = Customer.get(1)
println customer

Since the course is 4 years old, don't be surprised if some of the instructor's workflows are outdated—Grails moves fast! If none of these steps work, try comparing your build.gradle file with the course's (if available) to spot dependency or plugin differences.

内容的提问来源于stack exchange，提问作者NSar