命名（地图）构造函数在 grails.gsp.PageRenderer 中不起作用

Question

When I use a map constructor like:

Person p = new Person(name: "Bob")

through something that is called via a grails.gsp.PageRenderer, the field values are not populated. When I use an empty constructor and then set the fields individually like:

Person p = new Person()
p.name = "Bob"

it succeeds. When I use the map constructor via a render call, it also succeeds.

Any ideas as to why this is the case?

Sample project is here in case anyone wants to dig deeper: https://github.com/danduke/constructor-test/

Actual use case, as requested by Jeff below:

• I have a computationally expensive view to render. Essentially it's a multi-thousand page (when PDF'd) view of some data.
• This view can be broken into smaller pieces, and I can reliably determine when each has changed.
• I render one piece at a time, submitting each piece to a fixed size thread pool to avoid overloading the system. I left this out of the example project, as it has no bearing on the results.
• I cache the rendered results and evict them by key when data in that portion of the view has changed. This is why I am using a page renderer.
• Each template used may make use of various tag libraries.
• Some tag libraries need to load data from other applications in order to display things properly (actual use case: loading preferences from a shared repository for whether particular items are enabled in the view)
• When loaded, these items need to be turned into an object. In my case, it's a GORM object. This is why I am creating a new object at all.

There are quite a few opportunities for improvement in my actual use case, and I'm open to suggestions on that. However, the simplest possible (for me) demonstration of the problem still does suggest that there's a problem. I'm curious whether it should be possible to use map constructors in something called from a PageRenderer at all. I'm surprised that it doesn't work, and it feels like a bug, but obviously a very precise and edge case one.

Answer 1

"Technically it is a bug" (which is the best kind of bug!), and has been reported here: https://github.com/grails/grails-core/issues/11870

I'll update this if/when additional information is available.