Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I tried the Bean Fields plugin and got the error described here.
http://jira.grails.org/browse/GPBEANFIELDS-37
Does anyone know if this has been resolved? If not, I believe the author definitely needs to update the description of the plugin, to save people time from studying it and attempting to use it.
The Bean-Fields plugin is not broken – Groovy shipped with Grails 1.3.7 contains a bug. There is no workaround that I am aware of, and the problem only affects bean:field.
I was unable to get clarification of the root cause of the bug so was unable to craft a workaround. I spent a lot of time on this already.
Bean-Fields works well enough – just don’t use bean:field in Grails 1.3.7, that’s what we had to do in our projects.
The new field rendering mechanisms for Grails 2 are in progress, using new code taking the best ideas of Bean Fields and taking it to the next level. No ETA yet, but this is being worked on by members of the GPC.