Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GRAILS-11728: Reloading is broken in Grails 2.4.3 #2773

Closed
graemerocher opened this issue Sep 16, 2014 · 1 comment
Closed

GRAILS-11728: Reloading is broken in Grails 2.4.3 #2773

graemerocher opened this issue Sep 16, 2014 · 1 comment

Comments

@graemerocher
Copy link
Member

Original Reporter: candrews
Environment: Not Specified
Version: 2.4.3
Migrated From: http://jira.grails.org/browse/GRAILS-11728

The original report was made to Stack Overflow at https://stackoverflow.com/questions/25443800/grails-auto-reloading-new-controller-actions

I'm just copying it here for ease of reference:
{quote}
I've

created new Grails 2.4.3 project

created TestController

set grails.reload.enabled = true in BuildConfig.groovy

run application with grails -reloading run-app

My controller action code:
{code}
def index() {
render "test"
}
{code}
When I change the string test to test2- I see in console (in Eclipse):
{noformat}
..................
|Compiling 1 source files
{noformat}
And after reloading page I see test2 - ok.

But when I try to add new method:
{code}
def test3() {
render "test3"
}
{code}
I see:
[^error.png]

Why? Why there isn't even the url?

Example - action does't exist: [^error2.png]

Interesting thing is - when I create a whole new controller the index action of the newly created controller works...

After a while I decided to go with spring-boot and as a matter of fact - there it's not working either. I think that springloaded is the issue here because it doesn't pick up added new method in @controller
{quote}

The issue has been reported to Spring Loaded: spring-projects/spring-loaded#10

It looks like a version bump of Spring Loaded will fix this issue (the latest SNAPSHOT of Spring Loaded does not have this issue).

@graemerocher
Copy link
Member Author

graemerocher said:
I assume this is with forking disabled? If you do -reload with forking enabled it will enable the agent for the build VM not the forked VM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant