[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:
documentation
documents MAGNOLIA-5154 The population of the Model with requ... Closed
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
parameter is automatically set before rendering.

4.5.10 introduces enabling/disabling of this automatic populating of models:

  • globally: Configuration/server/rendering/engine add autoPopualateFromRequest property true/false, default is true
  • on template definition level, overides global setting, separatelly for every single definition: Templating Kit/Template Definitions/pages/stkHome add autoPopulateFromRequest property true/false, default is true


 Comments   
Comment by Roman Kovařík [ 22/Jul/13 ]

Please do not set to Open or work on this until MAGNOLIA-5154 will be closed.

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 ]

MAGNOLIA-5154 is now closed - setting to Open

Comment by Antti Hietala [ 13/Aug/13 ]

Documented in Populating the rendering model with request parameters.

Generated at Mon Feb 12 01:09:07 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.