I am still having issues with loading a document from the database that has an association, editing it, and saving it back. It fails trying to persist a BSONObject. If I manually delete the associated document from Mongo, it proceeds. I assume it's doing eager fetching and the associated document is left as its raw type when brought in by the driver?

Dynamic finders are also not working with properties mapped with 'attribute'. I know this one is undocumented but I thought I would throw it out there.

Great work on the improvements though! Embedded documents and dynamic properties are nice additions.

Thanks for the update!
Unfortunately, it breaks down the code.

1) Read-only properties like spring-security-core User code lead to compile errors:

Set getAuthorities() {
UserRole.findAllByUser(this).collect { it.role } as Set
}

I've added the setter to allow compilation go ahead:

void setAuthorities(Set authorities){
authorities.each {
UserRole.create(this, it)
}
}

2) For some reason

assert Domain.("hasMany" property).contains("object it really do contain")

always leads to a failure. Changed to .any{it.id==obj.id}.

3) Transactions doesn't work.

Exception Message: Already value [org.springframework.datastore.mapping.transactions.SessionHolder@ba117b] for key [org.springframework.datastore.mapping.mongo.MongoDatastore@380f83] bound to thread [http-8080-3]
Caused by: Could not open Datastore Session for transaction; nested exception is java.lang.IllegalStateException: Already value [org.springframework.datastore.mapping.transactions.SessionHolder@ba117b] for key [org.springframework.datastore.mapping.mongo.MongoDatastore@380f83] bound to thread [http-8080-3]

So I've added

static transactional = false

to all my services. Also I have commented all "Domain.withTransaction" statements.

4) Even after that I'm able to run tests and run project in development environment, but cannot deploy. Using Tomcat 7, Grails 1.3.6.

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'messageSource': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mongoTransactionManager': Cannot resolve reference to bean 'mongoDatastore' while setting bean property 'datastore'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mongoDatastore': FactoryBean threw exception on object creation; nested exception is java.lang.NoSuchMethodError: org.springframework.data.document.mongodb.MongoTemplate.execute(Lorg/springframework/data/document/mongodb/DbCallback;)Ljava/lang/Object;

Thou I'd better revert to M1 version. Or am I just doing something wrong?

@Dimitry you can find how to use Spring security core and mongodb here : https://github.com/lgaches/grails-mongospringsecurity

Many thanks, now I don't have to mess with that dynamic properties plugin! I think this really unleashes the power of a schema-less database when you can persist dynamic stuff.

@grocher, my issues appear to be IDE related. I switched to IntelliJ from STS as of my last post and the issue goes away even using the same project directory.

M4 really allows deployment without compile fails. But it's still not production-ready.
- Sometimes Mongo objects are returned instead of domains (in production mode). In my case, it is simple "hasMany" association. In development it's okay.
- Transactions doesn't work. When in UserDetailsService I type
User.withTransaction { status ->
It fails with session error:

org.springframework.transaction.CannotCreateTransactionException: Could not open Datastore Session for transaction; nested exception is java.lang.IllegalStateException: Already value [org.springframework.datastore.mapping.transactions.SessionHolder@2eb89c06] for key [org.springframework.datastore.mapping.mongo.MongoDatastore@7248989f] bound to thread [http-8080-3]

at org.springframework.datastore.mapping.transactions.DatastoreTransactionManager.doBegin(DatastoreTransactionManager.java:148)

Caused by: java.lang.IllegalStateException: Already value [org.springframework.datastore.mapping.transactions.SessionHolder@2eb89c06] for key [org.springframework.datastore.mapping.mongo.MongoDatastore@7248989f] bound to thread [http-8080-3]
at org.springframework.transaction.support.TransactionSynchronizationManager.bindResource(TransactionSynchronizationManager.java:179)
at org.springframework.datastore.mapping.transactions.DatastoreTransactionManager.doBegin(DatastoreTransactionManager.java:129)
… 79 more

Hope production-ready plugin will be available soon. All of us need it so much.
And one question. Is there any method to get all possible keys of a domain object? For [...] syntax.

Thanks for a fast bug-fixing!

I have created a JIRA issue with delete http://jira.codehaus.org/browse/GRAILSPLUGINS-2886

Hope that helps.

I'm not really sure, does the unique constraint should work?

Should I create a JIRA issue….

Thanks for the plugin

@Octavian

Hi, thanks for the information

Even it works the mapping, the constraints in the Domain Model, it seems it does not works…

When I do
import org.bson.types.ObjectId

class Foo {

ObjectId id
String name

static constraints = {
name nullable:false, blank:false, matches:"[\\d] ", unique:true
}

static mapping = {
name index:true, indexAttributes:[unique:true, dropDups:true]
}
}

def f = new Foo(name:"456")
f.validate() //it's always true

So, should I create a JIRA issue?

From the mongodb website regarding null values which I am currently having problems with :
Are null values allowed?
For members of an object, yes. You cannot add null to a database collection though as null isn't an object. You can add {}, though.

Perhaps the GORM api needs to be updated to set the value to {}?

@German Yes GORM for db4o is possible based on the existing infrastructure we have. Contributions welcome

when is version 5 going to be available?

Thanks! I've tried the new features, which is exactly what I was looking for. Well done!

Another question:
In your article's dynamic property demonstration, the object must be initialized with properties defined in Domain class to enable further dynamic properties:
1 def p = new Plant(name:"Pineapple")
2 p['color'] = 'Yellow'
3 p['hasLeaves'] = true

I tried to directly add dynamic properties to an object constructed without any parameter, like:
1 def p = new Plant()
2 p['color'] = 'Yellow'
3 p['hasLeaves'] = true

Executing above code failed, resulting in an exception:
java.lang.IllegalStateException: Cannot obtain DBObject for transient instance, save a valid instance first
at org.grails.datastore.gorm.mongo.MongoGormInstanceApi.getDbo(MongoGormEnhancer.groovy:120)
at org.grails.datastore.gorm.mongo.MongoGormInstanceApi$getDbo.callCurrent(Unknown Source)
at org.grails.datastore.gorm.mongo.MongoGormInstanceApi.putAt(MongoGormEnhancer.groovy:81)
at org.grails.datastore.gorm.GormEnhancer$1.call(GormEnhancer.groovy:93)

The fundamental problem is that I need to supply all the dynamic properties, which have been configured in another Domain class, together with pre-defined ones to create.gsp, so that user can input all the data items. Now it seems that dynamic properties can only be injected after pre-defined ones' values being set. Any solutions? Many thanks!

can save the List(no basic types) as embed documents?
like:
class User{
String firstName
List authorities
static embedded = ['authorities']
}

class Role{
String authority
}

I´m trying to use the GORM´s example to embedded documents.

class Person {

static mapWith = "mongo"

Address homeAddress
Address workAddress
static embedded = ['homeAddress', 'workAddress']
}
class Address {

static mapWith = "mongo"
String number
String code
}

However, I get an error like : Cannot resolve reference to bean 'mongoMappingContext' while setting bean property 'mappingContext'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mongoMappingContext': FactoryBean threw exception on object creation; nested exception is org.springframework.datastore.mapping.model.IllegalMappingException: Mapped identifier [id] for class [Address] is not a valid property

I have the M6 version of mongoDB plugin for grails…

When I try to assign my own id instead of generated id, the save fails with the following exception. Am I missing something here.
I tried save(insert:true).. no joy.

class Product {
String id;
String description;
String internalName;
String brandName;

static mapping = {
id generator:'assigned'
}
}

java.lang.NullPointerException
at org.grails.datastore.mapping.mongo.engine.MongoEntityPersister.isDirty(MongoEntityPersister.java:541)
at org.grails.datastore.mapping.core.AbstractSession.isDirty(AbstractSession.java:257)
at org.grails.datastore.mapping.engine.NativeEntryEntityPersister.persistEntity(NativeEntryEntityPersister.java:603)

jzhwu, I had the same problem that you did. If you initialize the object with a throwaway value from the domain class (I chose "name" and set it to a value that will never be referenced), then the object will work. This seems like a bug, but the workaround is so simple that I'm unlikely to log it.