[DOCU-440] Autopopulate rendering model from request settings Created: 22/Jul/13 Updated: 13/Aug/13 Resolved: 13/Aug/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Roman Kovařík | Assignee: | Antti Hietala |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
When rendering, RenderingModel instances are populated with request parameters. That is, if the model has a setFoo(String) method, it will be called with the value of the foo request parameter: class MyModel implements RenderingModel { private String someParameter; public void setSomeParameter(String someParameter) { this.someParameter = someParameter; } public String getSomeParameter() { return someParameter; } } request: /somePage.html?parameter=value 4.5.10 introduces enabling/disabling of this automatic populating of models:
|
| Comments |
| Comment by Roman Kovařík [ 22/Jul/13 ] |
|
Please do not set to Open or work on this until |
| Comment by Zdenek Skodik [ 29/Jul/13 ] |
|
It'd be nice to have such things also aggregated at some performance tips page. |
| Comment by Roman Kovařík [ 31/Jul/13 ] |
|
|
| Comment by Antti Hietala [ 13/Aug/13 ] |
|
Documented in Populating the rendering model with request parameters. |