You can deploy JSR168 portlet within Glassfish/OpenSource Portlet Container
Saturday Dec 16, 2006
Right now there is a huge momentum around JSR 168 portlet development environment in the Open Source World.
Many users of the open source GlassFish Java EE 5 application server want to use the server when developing and testing portlets. Portlets are designed to run in the context of a portal, which GlassFish does not provide directly. Although it is possible to execute and test a portlet without a portal in deploying it on Glassfish within an Open Source Portlet Container.
-
Developing the portlet JSR 168 with Netbeans 5.5 with the Netbeans Plugin For Portlets and Sun Java Portal Server
-
Testing the portlet JSR 168 on Glassfish/ Open Source Portlet Container
-
Deploying the portlet JSR 168 on JES-Portal 7
Open Source Portlet Container provides Webapps deployed on Glassfish to perform the following actions
-
to manage your JSR168 portlet (register/unregister un the portlet container)
-
to test your JSR168 portlet
Screenshots from OpenSource JSR168 portlet container
When your portlet is OK, just switch the RunTime target to JES-Portal 7 to integrate the portlet into your portal.
Sample Architecture Information
This portlet is calling 2 SAP R/3 BAPIs exposed as WebServices and returned « live » data from SAP back-end :
-
BAPI_PERSDATA_GETDETAILEDLIST
-
HRWPC_RFC_EP_READ_PHOTO_URI
The WSDL have been retrieved from the SAP R/3 WebServices Browser.
The webservice clients have been generated with NetBeans5.5 through JAX-RPC 1.6 and JAW-WS 2.0 interface.
This portlet project has been tested with Glassfish/OpenSource JSR168 Portlet Container and JES-Portal7.
--Patrice










