ansaurus

Question

Grails 1.2.0 Deployment Problems: org.hibernate.MappingException

Answer 1

A:

Found it. A static mapping block caused the error.

static mapping { contents type 'text' }

ikarous 2010-02-20 01:26:35

Answer 2

A:

I had a similar error. I cleaned my app (grails clean) before generating the war and the problem went away. Maybe there were references to old domain classes, I don't know.

Marcin 2010-03-08 13:24:44

Answer 3

A:

I rain into the same problem, for me it happened once I switched to Grails 1.2. The solution was not so obvious, the stacktrace certainly didn't shed any light on it.

You can't have domain objects w/ relationships such as hasMany declared in the same file. Each domain object should be declared in a separate file.

See http://www.manning-sandbox.com/message.jspa?messageID=80964

rniedzial 2010-03-12 19:06:09

Answer 4

A:

The problem seems to raise in a set of very different conditions.

It happened to me upgrading an application from grails 1.1 to grails 1.2: in this case the trigger was an enum definition in the same file as the domain class using the enum: this didn't cause any problem under 1.1, while in 1.2 I got the infamous:

    Error creating bean with name 'sessionFactory': Invocation of init method failed; 
nested exception is org.hibernate.MappingException: Type [null] is not a basic type or a domain class and cannot be mapped. 
Either specify a type within the [mapping] block or use a basic type (String, Integer etc.)

putting the enum in a separate file solved the problem.

So it seems that grails 1.2 is a bit more picky about what goes in a domain class source file, respect to 1.1 ....

cippirimerlo 2010-03-16 15:54:50

ansaurus

tags:

views:

answers:

Grails 1.2.0 Deployment Problems: org.hibernate.MappingException

related questions