|
|
In a world of increasingly interactive and responsive web applications, WebLogic Portals need to be designed and updated to keep pace with users’ expectations. Browser-based development technologies such as Ajax, JavaScript, and JSON, web-based APIs for accessing data, architectural patterns such as REST, and client-side development toolkits such as Dojo, enable web developers to create web applications that approach the responsiveness of desktop applications.
This guide is for WLP developers who want to integrate these client-side technologies into their portals. This chapter introduces the client-side portal development topics and technologies that are discussed in this guide.
Disc (Dynamic Interface SCripting) is a client-side JavaScript framework that handles the asynchronous updating of portlets, portlet events, and the retrieval of portal context objects.
To get started using Disc, see The WLP Disc Framework.
Client-side developers using WLP can use their favorite toolkits for DHTML and JavaScript browser programming. Dojo, for instance, works well for portlet development and for extending the WLP rendering framework.
To get started using Dojo for WLP client-side development, see Configuring JavaScript Libraries in a Portal Web Project.
Traditionally, portlets have been confined to use within a portal application. This traditional model required an application server running a portal container to surface portlets. Portlet Publishing makes portlets available to any web application over HTTP and allows portlets to be surfaced in any web page. With Portlet Publishing, for example, you can render portlets within a Struts or Spring application, or any other non-portal web page.
For detailed information on publishing your portlets, see Portlet Publishing..
WebLogic Portal provides a set of web-based, REST-style APIs for retrieving, modifying, creating and updating portal data dynamically from the client.
For detailed information on the REST API, see The WebLogic Portal REST API.
To get a feel for the possibilities of client-side portal development, we recommend that you run the Dynamic Visitor Tools (DVT) sample application. This sample application shows what is possible using the Disc and REST APIs to create a rich, interactive web application.
For detailed information on running the DVT sample, see the WLP Samples Guide.
| Note: | The DVT Sample is not supported for a production environment. The DVT sample is intended to illustrate how the WLP client-side development technologies such as the REST and Disc APIs and the external Dojo toolkit, can be used to enhance a portal’s interactivity. |
|