jyotiverma0310 / burningimage

Automatically exported from code.google.com/p/burningimage
0 stars 0 forks source link

Burning image plugin fails with mongodb gorm plugin #16

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Install MongoDB gorm plugin (http://www.grails.org/plugin/mongodb)
2. Install burning image plugin (http://www.grails.org/plugin/burning-image)
3. Run application with grails run-app

What is the expected output? What do you see instead?

Expected application to start up, but got attached exception instead.

What version of the product are you using? On what operating system?

Grails 1.3.7/ burning image 0.5.0 / mongodb gorm 1.0-M5

Please provide any additional information below.

Problem is related to MAX_IMAGE_SIZE in pl.burningice.plugins.image.ast.Image 
constraints closure on data. Remove MAX_IMAGE_SIZE and hardcode constraint or 
make it public and access it as Image.MAX_IMAGE_SIZE within the constraints 
closure.

Original issue reported on code.google.com by dpoli...@gmail.com on 19 Apr 2011 at 9:50

Attachments:

GoogleCodeExporter commented 9 years ago
Exactly the same error appears if using the redis plugin instead of mongo. 
Could it be that burningimage does not comply with the Grails persistence 
interceptor concept, which is required for mongo/redis plugins to work 
correctly?
Anders

Original comment by and...@turkino.net on 13 May 2011 at 12:42

GoogleCodeExporter commented 9 years ago
http://grails.org/doc/latest/guide/7.%20Validation.html

From section 7.1

A word of warning - referencing domain class properties from constraints
It's very easy to reference instance variables from the static constraints 
block, but this isn't legal in Groovy (or Java). If you do so, you will get a 
MissingPropertyException for your trouble.

Original comment by dpoli...@gmail.com on 13 May 2011 at 11:59