Skip to main content link. Accesskey S
  • Anonymous
  • Log on
  • Help
  • IBM logo
  • IBM Web Experience Factory wiki
  • All Wikis
  • Home
  • Community Articles
  • Product Documentation
  • Learning Center


Search

Advanced Search
IBM Translated Product Documentation...
 Web Experience Factory 8 Documentation

 WebSphere Portlet Factory 7.0.1 Documentation

Tag Cloud

  • 6.1
  • 6.1.2
  • 6.1.5
  • 6.1.5.1
  • 7.0
  • Ajax
  • Alerts
  • Annotations
  • attachment
  • best practices
  • BlackBerry
  • builder
  • builder faq
  • builders
  • charts
  • Code samples
  • Connections
  • css
  • Custom builder
  • CustomBuilder
  • dashboard
  • Data Access
  • data access faq
  • Data and variables
  • Database
  • Databases
  • Debugging
  • demo
  • demo models
  • demo projects
  • demo widget
  • demos
  • deployment
  • deployment faq
  • Deployment scenarios
  • development
  • dojo
  • Domino
  • faq
  • fixpack
  • General FAQ
  • getting started
  • Help
  • HTML
  • html templates
  • ILOG
  • integration
  • iPhone
  • JViews
  • Learning
  • Logging
  • lotus connections
  • Lotus Widget Factory
  • media dashboard
  • media pf
  • media widget
  • mobile
  • mobile smartphone development
  • Model development
  • new
  • Notifications
  • overview
  • page automation
  • Portal
  • Portal Integration
  • portal integration faq
  • Portlet
  • Portlet Factory 7
  • presentation
  • presentation faq
  • Profiling
  • Quickr
  • REST
  • rest faq
  • REST Service Call
  • restructure handler
  • rich ui
  • sample
  • sample application
  • samples
  • schema
  • Security
  • Smartphones
  • SOA
  • social
  • Source Control
  • sql
  • summary and drilldown
  • Team development
  • Troubleshooting
  • ui
  • User Interface
  • video
  • web 2.0
  • Web Experience Factory
  • Web Experience Factory 8
  • Web Services
  • websphere dashboard framework
  • wef
  • wpf
InformationInformation
You are currently viewing machine translated content. IBM translation might be available. Click IBM Translated Product Documentation to see what is available.X


Home > Product Documentation > Objects that the Portlet Adapter builder creates
Rate this article 1 starRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars
(Current editable edition)
Original noneditable edition
Current editable edition
(Original noneditable edition)

Objects that the Portlet Adapter builder creates 

expanded Abstract
collapsed Abstract
This topic describes the objects that the Portlet Adapter builder creates.



This topic describes the objects that the Portlet Adapter builder creates.

Linked Java object (LJO)


A helper LJO is added to the Web application to provide utility convenience methods to supply information about the portlet render request attributes. It has the following name.

portletHelper


You can call the helper LJO from an action list by using the following format.

portletHelper.method_call


You can use the following methods in the LJO.

isPortletActionRequest()
    Returns true if the portlet request is in the action phase.
isPortletRenderRequest()
    Returns true if the portlet request is in the render phase.
setRenderParameter(name,value)
    Set a render parameter with the specified name and value.  This may be used to set a JSR 286 public render parameter in the action phase of one portlet, to be used by other JSR 286 portlets as an incoming request parameter during their render phase.  Both sets of portlets must declare the public render parameters to be shared, using the same name and namespace in the portlet deployment descriptor.  For Web Experience Factory portlets, the supported public render parameters may be declared in the "Public Render Parameters" section of the Portlet Adapter builder inputs.
getNamespace()
    Return the unique namespace for that portlet from the JSR 168 or JSR 286 portlet container, by the portlet API. This can be used to prefix or suffix JavaScript™ with a value unique to that portlet instance if desired and to use as a unique portlet instance value for any other related purpose.

    Note: For JSR 286 portlets, getNamespace() returns the unique namespace id in both action and render phases. However, the JSR 168 portlet API returns only a unique namespace value if you call it during a render request. If you call this convenience method from a JSR 168 render request or a legacy style portlet, it returns null.
Parent topic: Portlet Adapter builder

expanded Article information
collapsed Article information
Category:
Product Documentation, WebSphere Portlet Factory 7.0.1 Documentation,
Tags:

This Version: Version 2 October 25, 2011 10:22:14 PM by Michael Burati  IBMer

expanded Attachments (0)
collapsed Attachments (0)

 


expanded Versions (2)
collapsed Versions (2)
Version Comparison     
Version Date Changed by               Summary of changes
This version (2) Oct 25, 2011 10:22:14 PM Michael Burati   Fix name of setRenderParameter method and description of what it used ...
1 Jun 28, 2011 11:51:05 AM IBM  
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedSubscribe to RSSHelpAbout
  • All Lotus and WebSphere Portal wikis
  • IBM developerWorks
  • IBM Software support
  • IBM Social Business User Experience Blog
  • IBMSocialBizUX on Twitter
  • IBMSocialBizUX on Facebook
  • Lotus product forums
  • IBM Social Business UX blog
  • IBM Collaboration Solutions
  • Recently added feedRecently added
  • Recently edited feedRecently edited
  • Recently added comments feedRecently Added Comments
  • Wiki Help
  • Forgot user name/password
  • Wiki design feedback
  • Content feedback
  • About the wiki
  • About IBM
  • Privacy
  • Contact IBM
  • IBM Terms of use
  • Wiki terms of use