Wednesday Nov 28, 2012

Developing Spring Portlet for use inside Weblogic Portal / Webcenter Portal

The main difference between portlet workflow and servlet workflow is that, the request to the portlet can have two distinct phases:

1) Action phase
2) Render phase.

The Action phase is executed only once and is where any 'backend' changes or actions occur, such as making changes in a database.

The Render phase then produces what is displayed to the user each time the display is refreshed.

The critical point here is that for a single overall request, the action phase is executed only once, but the render phase may be executed multiple times. This provides a clean separation between the activities that modify the persistent state of your system and the activities that generate what is displayed to the user.

The dual phases of portlet requests are one of the real strengths of the JSR-168 specification. For example, dynamic search results can be updated routinely on the display without the user explicitly re-running the search. Most other portlet MVC frameworks attempt to completely hide the two phases from the developer and make it look as much like traditional servlet development as possible - we think this approach removes one of the main benefits of using portlets.
[Read More]

Friday Aug 03, 2012

Weblogic Portal - Create Custom WorkFlow

Please find Creating Custom Workflow documentation. But in the documentation you will not find the code in detail level. Now we are going to see that in detail.

If you are using a WLP repository and library services-enabled, you can enforce a workflow process when users add and publish content in the repository. WLP repositories include one default content workflow. You can create additional content workflows or customize content workflows to suit your business needs.

Refer Adding WorkFlow for adding the custom workflow. Please download the Default Workflow for your later reference. Once you add custom workflow, you may loose the default workflow.

[Read More]

Weblogic Portal - Refresh Single Portlet In Portal Desktop

Over the past few years, Web 2.0 and Ajax have influenced the development of interactive Web applications. You can use Ajax to send asynchronous requests to a server without refreshing the full page. The result is very appealing to the end user because the Web application seems to react immediately, and the user’s experience is similar to what he or she sees when using a desktop application. You can use the Single Portlet Refresh in use cases [Read More]
About

Search

Categories
Archives
« July 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
  
       
Today