...
...
...
...
...
...
...
...
...
...
Jasig-Recommended Portlet Technologies
Jasig portlets targeted for uPortal 4 typically use Spring PortletMVC 2.5.x, a JSP view layer, and are built with Maven.
...
- portlet defineObjects tag extension — The portlet tag library includes a tag called . This tag establishes three objects; renderRequest, renderResponse and portletConfig for use in included portlet JSP pages. Although you can certainly access some useful information through these objects using the JSTL tag library, accessing scoped variables and the like will require the use of scriptlets. JSTL users are used to having access to scoped variables via the JSTL implicit objects (requestScope, sessionScope, ap
Struts
- Struts Bridge — This document will explore how a Struts application can be modified to work as a JSR168 compliant portlet. It will hopefully serve as a useful reference guide for those planning to install the Struts Bridge into their existing Struts applications. As an example we'll use the iBATIS version of Petstore application, the Petstore is a commonly implemented demonstration of a fictitious e-commerce site. The iBATIS version of Petstore is built with the Struts framework and incidentally also provides a
Using other development frameworks
While Jasig strives to develop consistent software development practices, portlet developers are welcome to use other development frameworks to match their personal preferences or institutional standards. Portlets may generally be developed with any backend framework that supports the JSR-168 standard. Portlet view layers may use any JavaScript library that is compatible with jQuery in noConflict mode.