Hi WangQi,
I have a similar problem with yours.
As far as I remember, there was a message "CascadeValidationToOne" in the stacktrace when I run an original app developped with Grails0.4.2 and upgraded to Grails0.5-snapshot.
Best regards,
Daniel.Sun
===================================================
Error INFO
------------------------------------------------------------------------------------------------------
org.springframework.beans.factory.BeanCreationException: Error creating bean wit
h name 'pluginManager' defined in class path resource [applicationContext.xml]:
Invocation of init method failed; nested exception is groovy.lang.MissingMethodE
xception: No signature of method: Book.bName() is applicable for argument types:
(java.util.HashMap) values: {["blank":false, "size":1..50]}
---------------------------------------------------------------------------------------------------------
according to my debug (with 0.5 snapshot), the problem is the unique constraints. (it seams doesn't work anymore)
in UniqueConstraint.java, line 106, it always throw NullPointException.
the last developer is graeme. can u help on this?
wangqi
james_027 wrote:
Hi,
WangQi wrote:
is that possible to preven cascade validation?
e.g. i want to update category. category related to an categorylog, while categorylog related to an User.
the problem is when i want to perform category.save() the user always report validation error.
how can i prevent it? thanks
wangqi
I have something like that which my problem is the cascade object doesn't report any validation error. I am using grails 0.4.2
james