Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.3.7
-
Fix Version/s: 2.0-M2
-
Component/s: None
-
Labels:None
Description
If a plugin defines command objects or @Validateable classes, the application does not evaluate these as validateable by default and the result can be very confusing error messages about missing properties as the "constraints" property remains a Closure instead of a constrainedProperties map.
Example: plugin that has command objects and uses bean-fields. After installing this plugin the plugin's forms will not work and show obscure error about missing property.
Recommendation: either during plugin packaging time or plugin compile time, plugin artefacts are always scanned/info put into metadata such that the application author does not need to update their Config grails.validateable.packages to make plugins work.
Issue Links
- is related to
-
GRAILS-7377
@Validateable should not be Spring beans
-
- relates to
-
GRAILS-6586
Plugins cannot use command objects without user or plugin author jumping through hoops
-
Marc,
I think this is has been inadvertently fixed because of
GRAILS-7377. Do you concur?