Skip to content

GPMONGODB-34: All finders returning collections of domain objects actually return collections of BasicDBObject #489

@graemerocher

Description

@graemerocher

Original Reporter: nugsie
Environment: Ubuntu Linux 10.10, Java 6, Grails 1.3.7, Gorm Plugin 1.0-M5 (and latest git master clone)
Version: 1.0.0-M5
Migrated From: http://jira.grails.org/browse/GPMONGODB-34

Essentially the same problem I reported in GPMONGODB-19 and GPMONGODB-24. Unfortunately I thought this was fixed as part of GPMONGODB-10, but my original testcase still fails on the latest release and libraries/plugin built from latest git clone. HOWEVER, the same tests when applied within the context of the gradlew test cycle seem to pass!

I've been trying to work through and understand why this might be the case but still have no idea why this should be failing in a standalone app with plugin and jar dependencies built from git but work ok within a testcase from the command-line build. I imagine this is why it has appeared to be fixed when running through the test suite but why it keeps getting raised back here.

I've attached a demo testcase which actually uses the GormDatastoreSpec in exactly the same way as the bundled tests but which fails with the response I'm experiencing - hopefully this is more in line and testable/reproducible than the previous bug report.

Please let me know if there's anything more I can do to help resolve this as we'd really love to be able to continue forward using the plugin for our current project!

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions