Exploit : faire une opposition widget / portlet en oubliant que les portlets c'est à la base le modèle Yahoo!. Chapeau.Portlets are used mainly in intranets, to provide a collection of enterprise apps on a single web page for employees (e.g. a news feed, calendar, expense forms, bug reports, etc.).
JSR-168 is a collection of Java APIs for portlet developers. There are a number of reasons to design JSR-168 portlets that adhere to the specification. Portability is an obvious benefit. Code written according to the specification will be easier to move to among portal servers. The majority of Java-based portal servers support JSR-168 portlets. Another benefit is easier federation. Exposing JSR-168 Portlets via Web Services for Remote Portlets (WSRP) producers is easier when portlets adhere to the JSR-168 specification. WSRP provides a standard to federate portlet content via Web services. JSR-168 and WSRP 1.0 portlet capabilities are tightly coupled. JSR-168 to WSRP portlet bridges utilize JSR-168's URL rewriting APIs. This article illustrates best practices for developing JSR-168 portlets for portability.
A year ago, the article Asynchronous Rendering of Portlet Content With Ajax Technology demonstrated how to apply Asynchronous JavaScript and XML (Ajax) to portlets. Since then, Ajax has become increasingly popular in the software arena and many new Ajax technologies have emerged. Examples are JavaScript libraries and toolkits, such as the Dojo Toolkit, the Yahoo! UI Library, the Google Web Toolkit, Script.aculo.us, and DHTML Goodies. In addition, new standards bodies like Open Ajax and the Dojo Foundation are key players. In light of the many developments in the past year and the host of feedback on how to use Ajax in portlets, this article describes several helpful tips and practices on how best to exploit Ajax in portlets that comply with the Java Specification Request (JSR) 168: Portlet Specification.
]]>
]]>
An collection of very good javascript, ajax, flash widgets. There is a multiple file upload with flash and a jquery portlet.
The PortletBridge Portlet project creates a JSR-168 Portlet that can proxy and rewrite content from a downstream web site. Currently, the portlet supports: Getting content from a downstream site, Proxy configuration (including NTLM and Basic authentication), NTLM and Basic authentication as preferences, Using an xsl stylesheet to rewrite the content from the downstream site, Proxying of remote resources (e.g. images, flash etc.), Pluto 1.0.1 rc2, JBoss Portal 2.0, LifeRay Professional 3.6.0, XSL Stylesheets packaged as part of the portlet or remote (URL based), Rewriting CSS urls, Moving javascript and css links out of the head, Hiding of downstream URLs and configurable scope, Back button and refresh support
What is the PortletBridge Portlet? The PortletBridge Portlet is a JSR 168 compliant portlet that allows a downstream web site to be proxied as a portlet. By default it only displays the content of the BODY but custom XSLT can be used to transform the data from the downstream site. What is the difference between the PortletBridge Portlet and an IFrame There are several differences between using an IFrame and the PortletBridge Portlet. Probably the biggest advantage to using an IFrame is that it is simpler than the PortletBridge Portlet and the downstream site will often be more faithfully rendered. There are however several advantages to using the PortletBridge Portlet.
]]>
What is the PortletBridge Portlet? The PortletBridge Portlet is a JSR 168 compliant portlet that allows a downstream web site to be proxied as a portlet. By default it only displays the content of the BODY but custom XSLT can be used to transform the data from the downstream site. What is the difference between the PortletBridge Portlet and an IFrame There are several differences between using an IFrame and the PortletBridge Portlet. Probably the biggest advantage to using an IFrame is that it is simpler than the PortletBridge Portlet and the downstream site will often be more faithfully rendered. There are however several advantages to using the PortletBridge Portlet.
StringbeansTM is a platform for building enterprise information portals. The platform is composed of three components: a portal container/server, a Web Services platform, and a process automation engine. At this time we have released the portal server and Web services platform. The process automation engine will be released in the near future.
This article describes the first steps a team would typically take when starting a new project to implement a portal using IBM® WebSphere® Portal. It also provides some basic tools that can help you with these first steps. It discusses issues that teams typically face when starting a new portal project, and suggests some approaches to dealing with them. It describes various types of portals and how the type of portal you choose can influence your planning process. Finally, it introduces several tools, or work products, which you can use to plan and set up your own portal. This article is the first in a multiple-part series Creating a new portal.
]]>1. Introduction 2. Installing Eclipse 3. Installing JBoss Portal 2.2 4. Creating the project 5. Classpath settings 6. portlet.xml 7. web.xml 8. Hello World! 9. xwork.xml 10. JBoss Portal descriptors 11. Deployment 12. Next step 13. Re-deployment
Vous l'avez probablement constaté, en ce moment, les portails ont le vent en poupe. Ca tombe bien, depuis quelques temps, je suis plutôt versé sur WebSphere Portal, et ce n'est pas pour me déplaire après 3 ans & demi consacrés quasi-exclusivement au développement Lotus Domino (avec un peu de PHP entre les deux). Toutefois, c'est un univers vaste et très différent de ce dernier, et la bête n'est pas forcément facile à dompter ni même à aborder. Voici quelques liens que j'ai recueilli au fil de mes aventures et qui pourraient intéresser ceux qui débutent dans le domaine : ...
]]>
UWA is the new Netvibes API. Through it, your Netvibes widgets will be available on every widget platforms or blog systems: Netvibes of course, but also Google IG, Apple Dashboard and many more...
Orbeon Forms also provides the Orbeon Forms Portlet, which supports the implementation of standard Java portlets that can be deployed within any portal or portlet container compatible with the Java Portlet specification. This specification is also known as JSR-168.
]]>
]]>
JSR 168 defines portlets as Java-based Web components, managed by a portlet container, that process requests and generate dynamic content. Portals use portlets as pluggable user interface components that provide a presentation layer to information systems.
This article will walk through the development of a simple portlet application to demonstrate the inner workings of a compliant portlet.
]]>
Portlet Frequently Asked Questions (FAQ) - a collection by Punit Pandey