![]() Portlets are not allowed to make persistent state changes during rendering.You cannot add portlet preferences to remote portlets consumed from a simple producer or from producers that have portal management disabled in the wsrp-producer-config.xml file.For example, the page flow action method shown in Listing 5-2 retrieves from a FormData object a preference set by a user, sets the preferences in a PortletPreferences object, and stores the preferences in the database using the store() method. For instance, a page flow portlet can retrieve an instance of this object from the PortletBackingContext object in an action method. Portlets can also create, retrieve, and modify preferences programatically by obtaining a object. #Jrebel remote portlet registration#See Managing Portlet Instances through Registration for more information. The WSRP registration interface provides a way for producers to keep track of new portlet instances created for remote portlets. Note that the first time a user updates a portlet preference, a new instance of the portlet is created, and the updated preferences are associated with the new instance. ![]() When you modify an instance of a portlet, only that instance is modified. In other words, if the same portlet is used in several desktops, a new instance of the portlet is generated for each use. If you modify an instance (in the Portals folder) only that instance is affected. If you modify a portlet preference in the Library, all subsequent instances of that portlet will include the change. ![]() For instance, you can change the default value for a preference, or make it read-only.Ĭhanges you make to a portlet preference in the Administration Console are scoped either at the Library level or the instance level. A similar interface exists for editing a preference. It is not possible to create or modify portlet preferences in a remote portlet using WorkSpace Studio.įigure 5-6 shows the interface for creating a portlet preference in the WebLogic Portal Administration Console. The Administration Console uses the Portlet Management interface of WSRP to retrieve preferences from the producer and modify them. You can view and modify the portlet preferences for a remote portlet using the WebLogic Portal Administration Console. Other WSRP producer implementations may not support portlet preferences. Portlet preferences are included in the WebLogic Portal implementation of WSRP producers. When you view or modify the preferences in a remote portlet (on a consumer), the consumer must fetch the preferences from the producer, and modifications must be sent back to the producer where they are stored. In a federated configuration, the producer stores and manages portlet preferences. Developers can create preferences in WorkSpace Studio, and administrators can create and edit preferences using the WebLogic Portal Administration Console. As long as a portlet preference is modifiable, and an interface is provided for editing preferences, every user of a portlet can configure his or her own personal view of the portlet.Ī clearly defined API exists for setting and retrieving preferences. The list of stocks is then passed to the server and stored in the database for that particular user. Through a user interface, users select or enter which stocks they want to view in the portlet. ![]() For example, a stock portfolio portlet might allow users to specify which stocks they want to view. When these preference values are retrieved by a portlet, they typically affect the way the portlet is displayed for a given user. Portlet preferences allow portlets to modify, store, and access pre-defined String values. If you are unfamiliar with portlet preferences, see the Portlet Development Guide. #Jrebel remote portlet how to#This section assumes that you are familiar with the concept of a portlet preference and how to create and configure portlet preferences.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |