Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 2.0-RC1
-
Fix Version/s: 2.2-RC1
-
Component/s: None
-
Labels:None
-
Environment:Lion,JDK6
Description
the original url:
I create a temp project to reproduce this problem,and the step is:
- grails ->enter into the interactive mode
- run-app
- exit ->exit the run-app
- then the exception will throw.
-
Hide
- test-with-bootstrap.zip
- 02/Nov/11 5:58 AM
- 124 kB
- Ford Guo
-
- test-with-bootstrap/.classpath 0.7 kB
- test-with-bootstrap/.project 0.5 kB
- test-with-bootstrap/.../org.codehaus.groovy.eclipse.preferences.prefs 0.1 kB
- test-with-bootstrap/application.properties 0.1 kB
- test-with-bootstrap/.../ApplicationResources.groovy 0.1 kB
- test-with-bootstrap/.../BootStrap.groovy 0.3 kB
- test-with-bootstrap/.../BuildConfig.groovy 2 kB
- test-with-bootstrap/.../Config.groovy 4 kB
- test-with-bootstrap/.../DataSource.groovy 1 kB
- test-with-bootstrap/.../resources.groovy 0.0 kB
- test-with-bootstrap/.../UrlMappings.groovy 0.2 kB
- test-with-bootstrap/.../User.groovy 0.1 kB
- test-with-bootstrap/.../messages.properties 3 kB
- test-with-bootstrap/.../messages_cs_CZ.properties 3 kB
- test-with-bootstrap/.../messages_da.properties 3 kB
- test-with-bootstrap/.../messages_de.properties 4 kB
- test-with-bootstrap/.../messages_es.properties 3 kB
- test-with-bootstrap/.../messages_fr.properties 2 kB
- test-with-bootstrap/.../messages_it.properties 2 kB
- test-with-bootstrap/.../messages_ja.properties 4 kB
- test-with-bootstrap/.../messages_nl.properties 3 kB
- test-with-bootstrap/.../messages_pt_BR.properties 3 kB
- test-with-bootstrap/.../messages_pt_PT.properties 3 kB
- test-with-bootstrap/.../messages_ru.properties 4 kB
- test-with-bootstrap/.../messages_sv.properties 3 kB
- test-with-bootstrap/.../messages_th.properties 6 kB
- test-with-bootstrap/.../messages_zh_CN.properties 2 kB
- test-with-bootstrap/grails-app/.../error.gsp 0.3 kB
- test-with-bootstrap/grails-app/.../index.gsp 3 kB
- test-with-bootstrap/grails-app/.../main.gsp 2 kB
Activity
- All
- Comments
- Work Log
- History
- Activity
- Git Commits
Hide
Graeme Rocher
added a comment -
The destroy event is only invoked after shutting down the application context which is after the session factory has been destroyed. GORM logic cannot be placed into this destroy event, and changing this now would be a breaking semantic change
Show
Graeme Rocher
added a comment - The destroy event is only invoked after shutting down the application context which is after the session factory has been destroyed. GORM logic cannot be placed into this destroy event, and changing this now would be a breaking semantic change
Still not working in 2.0.1. Is there a workaround to do some work which reads from the database before shutdown?