Evict GrailsParameterMap objects before building flow execution url #311

Merged
merged 1 commit into from Jan 13, 2013

Conversation

Projects
None yet
2 participants
@robbugh
Contributor

robbugh commented Jan 10, 2013

The webRequest params used to build the flow execution url can contain nested GrailsParameterMap objects if the "params" attribute (of a redirect call in a controller, for instance) contains structured keys, e.g., a redirect to the "customerFlow",

redirect(action:customer, params: ['customer.id': 123])

In this case, when the params attribute is parsed a synthetic GrailsParameterMap object will be created and added to the controller's params map with the key/value, customer: [id:123]. These synthetic GrailsParameterMap parameters should not be included in the resulting flow execution URL as they can interfere with the original parameters, 'customer.id' in this case, when the flow execution URL is parsed by the flow execution engine.

graemerocher added a commit that referenced this pull request Jan 13, 2013

Merge pull request #311 from robbugh/master
Evict GrailsParameterMap objects before building flow execution url

@graemerocher graemerocher merged commit 3d1a7c8 into grails:master Jan 13, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment