All OpenMRS ID accounts have been reset.

Read more and change your password before signing in.
Icon

EXTENDED: OMRS14 Proposals due 30 April! Read more and submit a proposal at OpenMRS Talk.

Skip to end of metadata
Go to start of metadata

Create a module portlet controller

Module portlet controllers, along with form controllers, are typically put in the omod/src/main/java/web.controller folder and have names ending with PortletController.  Portlet controllers should extend PortletController. If there are actions that need to be taken when the portlet is referenced, override the populateModel method.  Any property added to the model in the populateModule method is available UNDER the "model" property.  So if you add "myvar" to the model object, in your portlet jsp you access it with ${model.myvar}.  Here is an example:

Make sure the following line exists in your ModuleApplicationContext.xml file, substituting your module name for ModuleID.  It typically is put just above the </beans> tag at the end.

Create the module portlet jsp

Module portlets are defined in the omod/src/main/webapp/portlets folder.  In our example, the portlet would be named this.jsp.  The code inside of a portlet shouldn't have to differ from a standard OpenMRS portlet, meaning that it looks exactly like a jsp (or part of a jsp).

Use the portlet in another jsp page

Portlets are included in a jsp by using the following tag:

Note that you must specify moduleId="...", which differs from using a portlet in core code.

1 Comment

  1. Post Spring 2.5, we don't need the wiring to be manual(inclusion in the xml files). In our custom portlet controller we need to include annotation such as 

    @Controller
    @RequestMapping("**/thismodulesportlet.portlet")

    This will automatically wire the controller and the portlet.