Grails

Cannot locate GORM API implementation when OSIV is being used

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.4-M1, 2.0-M2
  • Fix Version/s: 2.0-RC1
  • Component/s: Testing
  • Labels:
  • Environment:
    Windows 7 x64, grails 1.4.0m1
  • Testcase included:
    yes

Description

I'm using OSIV to allow my DWR service to access live domain objects.

web.xml:
<filter>
<filter-name>hibernateFilter</filter-name>
<filter-class>org.springframework.orm.hibernate3.support.OpenSessionInViewFilter</filter-class>
<init-param>
<param-name>singleSession</param-name>
<param-value>true</param-value>
</init-param>
</filter>

<filter-mapping>
<filter-name>hibernateFilter</filter-name>
<url-pattern>/dwr/*</url-pattern>
</filter-mapping>

Now, Domain.(anymethod) throws the following error in integration tests:

Cannot locate GORM API implementation. You either don't have a GORM implementation installed (such as the Hibernate plugin) or you are running Grails code outside the context of a Grails application.

This is a regression from 1.3.7.

I can reproduce the issue.
If the domain class has id, and version attributes defined, it is causing the above error

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Graeme Rocher added a comment -

Do you actually have hibernate installed? If so please attach an example that reproduces the problem

Show
Graeme Rocher added a comment - Do you actually have hibernate installed? If so please attach an example that reproduces the problem
Hide
Permalink
Stefan Kendall added a comment -

I tried adding plugins

{ compile ":hibernate:$grailsVersion" }

, but my 1.3.7 project upgraded to 1.4.0M1 still fails. I tried to reproduce this issue from a clean application with the minimal amount of configuration, but I can't seem to create a simple failure. Even with the plugin in my other project, I still get IllegalStateException.

Show
Stefan Kendall added a comment - I tried adding plugins { compile ":hibernate:$grailsVersion" } , but my 1.3.7 project upgraded to 1.4.0M1 still fails. I tried to reproduce this issue from a clean application with the minimal amount of configuration, but I can't seem to create a simple failure. Even with the plugin in my other project, I still get IllegalStateException.
Hide
Permalink
Graeme Rocher added a comment -

hmm well without a reproducible example it is kinda hard to say what the problem is

Show
Graeme Rocher added a comment - hmm well without a reproducible example it is kinda hard to say what the problem is
Hide
Permalink
Raviteja added a comment -

Same problem occurs when I upgrade my 1.3.7 project to 2.0.0.M2. I'll try to post a example soon

Show
Raviteja added a comment - Same problem occurs when I upgrade my 1.3.7 project to 2.0.0.M2. I'll try to post a example soon
Hide
Permalink
Raviteja added a comment -

Some help: http://blogs.bytecode.com.au/glen/2011/07/15/yes-i-can-locate-a-gorm-api-implementation.html

Show
Raviteja added a comment - Some help: http://blogs.bytecode.com.au/glen/2011/07/15/yes-i-can-locate-a-gorm-api-implementation.html
Hide
Permalink
Graeme Rocher added a comment -

Can someone attach a reproducible example?

Show
Graeme Rocher added a comment - Can someone attach a reproducible example?
Hide
Permalink
Raviteja added a comment -

Was unable to reproduce the error by creating a new project but it's reproducible on the production code of our project.

grails run-app
| Compiling 1 source files

| Compiling 3 source files.
No external configuration file defined.....
| Compiling 3 source files.....
No external configuration file defined.....
| Running Grails application

Configuring Spring Security ...
Configuring Spring Security LDAP ...
Configuring Spring Security UI ...
| Error 2011-09-28 14:21:56,944 [Thread-9] ERROR context.GrailsContextLoader  - Error executing bootstraps: Error creating bean with name 'messageSource': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transactionManager': Cannot resolve reference to bean 'sessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory': Invocation of init method failed; nested exception is java.lang.IllegalStateException: Cannot locate GORM API implementation. You either don't have a GORM implementation installed (such as the Hibernate plugin) or you are running Grails code outside the context of a Grails application.
   Line | Method
->> 303 | innerRun in java.util.concurrent.FutureTask$Sync
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
|   138 | run      in java.util.concurrent.FutureTask
|   886 | runTask  in java.util.concurrent.ThreadPoolExecutor$Worker
|   908 | run      in     ''
^   662 | run . .  in java.lang.Thread

Caused by BeanCreationException: Error creating bean with name 'transactionManager': Cannot resolve reference to bean 'sessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory': Invocation of init method failed; nested exception is java.lang.IllegalStateException: Cannot locate GORM API implementation. You either don't have a GORM implementation installed (such as the Hibernate plugin) or you are running Grails code outside the context of a Grails application.
->> 303 | innerRun in java.util.concurrent.FutureTask$Sync
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
|   138 | run      in java.util.concurrent.FutureTask
|   886 | runTask  in java.util.concurrent.ThreadPoolExecutor$Worker
|   908 | run      in     ''
^   662 | run . .  in java.lang.Thread

Caused by BeanCreationException: Error creating bean with name 'sessionFactory': Invocation of init method failed; nested exception is java.lang.IllegalStateException: Cannot locate GORM API implementation. You either don't have a GORM implementation installed (such as the Hibernate plugin) or you are running Grails code outside the context of a Grails application.
->> 303 | innerRun in java.util.concurrent.FutureTask$Sync
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
|   138 | run      in java.util.concurrent.FutureTask
|   886 | runTask  in java.util.concurrent.ThreadPoolExecutor$Worker
|   908 | run      in     ''
^   662 | run . .  in java.lang.Thread

Caused by IllegalStateException: Cannot locate GORM API implementation. You either don't have a GORM implementation installed (such as the Hibernate plugin) or you are running Grails code outside the context of a Grails application.
->>  24 | doCall   in <SOME_CLASS>$__clinit__closure1
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
|   303 | innerRun in java.util.concurrent.FutureTask$Sync
|   138 | run . .  in java.util.concurrent.FutureTask
|   886 | runTask  in java.util.concurrent.ThreadPoolExecutor$Worker
|   908 | run . .  in     ''
^   662 | run      in java.lang.Thread
Show
Raviteja added a comment - Was unable to reproduce the error by creating a new project but it's reproducible on the production code of our project. grails run-app | Compiling 1 source files | Compiling 3 source files. No external configuration file defined..... | Compiling 3 source files..... No external configuration file defined..... | Running Grails application Configuring Spring Security ... Configuring Spring Security LDAP ... Configuring Spring Security UI ... | Error 2011-09-28 14:21:56,944 [Thread-9] ERROR context.GrailsContextLoader - Error executing bootstraps: Error creating bean with name 'messageSource': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transactionManager': Cannot resolve reference to bean 'sessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory': Invocation of init method failed; nested exception is java.lang.IllegalStateException: Cannot locate GORM API implementation. You either don't have a GORM implementation installed (such as the Hibernate plugin) or you are running Grails code outside the context of a Grails application. Line | Method ->> 303 | innerRun in java.util.concurrent.FutureTask$Sync - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | 138 | run in java.util.concurrent.FutureTask | 886 | runTask in java.util.concurrent.ThreadPoolExecutor$Worker | 908 | run in '' ^ 662 | run . . in java.lang.Thread Caused by BeanCreationException: Error creating bean with name 'transactionManager': Cannot resolve reference to bean 'sessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory': Invocation of init method failed; nested exception is java.lang.IllegalStateException: Cannot locate GORM API implementation. You either don't have a GORM implementation installed (such as the Hibernate plugin) or you are running Grails code outside the context of a Grails application. ->> 303 | innerRun in java.util.concurrent.FutureTask$Sync - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | 138 | run in java.util.concurrent.FutureTask | 886 | runTask in java.util.concurrent.ThreadPoolExecutor$Worker | 908 | run in '' ^ 662 | run . . in java.lang.Thread Caused by BeanCreationException: Error creating bean with name 'sessionFactory': Invocation of init method failed; nested exception is java.lang.IllegalStateException: Cannot locate GORM API implementation. You either don't have a GORM implementation installed (such as the Hibernate plugin) or you are running Grails code outside the context of a Grails application. ->> 303 | innerRun in java.util.concurrent.FutureTask$Sync - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | 138 | run in java.util.concurrent.FutureTask | 886 | runTask in java.util.concurrent.ThreadPoolExecutor$Worker | 908 | run in '' ^ 662 | run . . in java.lang.Thread Caused by IllegalStateException: Cannot locate GORM API implementation. You either don't have a GORM implementation installed (such as the Hibernate plugin) or you are running Grails code outside the context of a Grails application. ->> 24 | doCall in <SOME_CLASS>$__clinit__closure1 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | 303 | innerRun in java.util.concurrent.FutureTask$Sync | 138 | run . . in java.util.concurrent.FutureTask | 886 | runTask in java.util.concurrent.ThreadPoolExecutor$Worker | 908 | run . . in '' ^ 662 | run in java.lang.Thread
Hide
Permalink
Graeme Rocher added a comment -

Right, that doesn't really help though. Without valid steps to reproduce we're unable to prioritize this issue.

Show
Graeme Rocher added a comment - Right, that doesn't really help though. Without valid steps to reproduce we're unable to prioritize this issue.
Hide
Permalink
Raviteja added a comment -

Please find the report attached

Show
Raviteja added a comment - Please find the report attached
Hide
Permalink
Raviteja added a comment -

Hi, so did you get a chance to look at the example and figure out what was wrong?

Show
Raviteja added a comment - Hi, so did you get a chance to look at the example and figure out what was wrong?
Hide
Permalink
Graeme Rocher added a comment -

Which zip should be tested application-1.3.7-bug-report-28092011-min.zip?

Show
Graeme Rocher added a comment - Which zip should be tested application-1.3.7-bug-report-28092011-min.zip?
Hide
Permalink
Graeme Rocher added a comment -

Ok I can reproduce with the min example. The problematic line is 

        load nullable : false

In GenomicBuildInfo which incorrectly tries to call a GORM method instead of applying the constraint to the property

Show
Graeme Rocher added a comment - Ok I can reproduce with the min example. The problematic line is load nullable : false In GenomicBuildInfo which incorrectly tries to call a GORM method instead of applying the constraint to the property

People

  • Assignee:
    Graeme Rocher
    Reporter:
    Stefan Kendall
Vote (2)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: