Packaging a single Portlet

Hi,
How do you package a single portlet (in the form of a jar or war) so that it
can be used in other portal application, simply by importing it. Is it possible
to do this kind of reusable component design at portlet level or the entire portal
project has to be bundled in a jar or war?
Thanks,
Nikhil

Similar Messages

Refreshing a single portlet rather than the whole portal page

Ok, here's my situation.
I have two pdk portlets on my portal that communicate through page parameters. Portlet A has a bunch of search fields, a customer drop-down list, parts drop-down list, division, etc. Portlet B takes those parameters, queries the database, and displays the results. I would like to be able to refresh portlet B without reloading the whole portal page.
I have onchange events on all of my drop-downs that will do a javascript post back to portal, which will in turn set my page parameters, and I see there is a 'refreshPortlet' function in a javascript file that portal provides that will refresh a single portlet based on a portletReferenceId. It is normally called when a refresh button is clicked in the portlet header, but I don't see any reason I can't call it after my javascript post, that is, if I had the portletReferenceId for the other portlet. I thought about making a hidden html table on the page that, I could fill with the portlet names and ids for each portlet as they load, that way I could reference that list from any portlet. The problem is I can't figure out where the ids are coming from. Based on the code behind the button, the function is looking for something like this 646_701285_646_1_701271, but the closest thing I can come up with is this 676114_POSTCONTENTPORTLET_467414915 which I got from PortletRenderRequest.getPortletInstance().getInstanceName(). As you can see, it's not even close. Does anyone know where the correct id could be coming from? It's got to be available to me somewhere, doesn't it?
The only other option I can think of to accomplish my goal is to use straight up ajax to display portlet B, but that kind of defeats the purpose of portal doesn't it?
Any help would be greatly appreciated.
Thanks,
Doug

You can use Ctrl+F4 to close the current tab. I don't think that you can change the Alt+F4 action with Keyconfig.

Ways to put Multiple discoverer worksheets in a single Portlet

Hi all
Can anybody suggest me ways to put Multiple discoverer worksheets in a single Portlet. (10G release 2)
- Out of the box (no coding option)
- Java Beans options
Note:- the discoverer sheet portlet allows only 1 workseet.
Would appreciate any pointers/help in this regard
Cheers!!
Puneet

No - you don't need data in the same portlet to display them together.
A given page holds many portets - dependent as well as independent. That's the purpose of a portal, Oracle as other vendors - to bring together information from different systems (and the same system) and put it together on the same page to give a general picture of the situation.
Make two portlets - and make a page where you can add portlets side by side (either use two regions, or have one region that groups the portlets in columns) and place the two porlets there. They'll appear to the user on ONE page.
If you want the users to be able to place the two porlets indepently of your design, but always place them together, make a simple page where you do the layout and publish the page as a porlet. The users then get access to this porlet.
The simpler the porlets, the more of them, the more flexible and better performing website you get (remember, porlets are rendered in PARALLEL by Portal).

Ways to put Multiple discoverer worksheets in a single Portlet. (10G releas

Hi all
Can anybody suggest me ways to put Multiple discoverer worksheets in a single Portlet. (10G release 2)
- Out of the box (no coding option)
- Java Beans options
Note:- the discoverer sheet portlet allows only 1 workseet.
Would appreciate any pointers/help in this regard
Cheers!!
Puneet

Hi Puneet,
Discoverer portlets do not require any knowledge of code, Java beans, HTML, or any other programming construct. They are probably the simplest and easiest to use business intelligence portlets in the market today, and most customers I show these to are simply amazed at their power and user friendliness.
Anyway, to answer your question:
- You can choose to have one table (or crosstab) and one graph in one Discoverer portlet.
Note that since a Discoverer portlet is published on a Portal page, you do not have to worry about having or not having the capability to publish more than one Discoverer worksheet to a single portlet. By adding multiple Discoverer portlets to a single (or multiple) Portal pages you can achieve the same effect.
Discoverer is a portlet provider to Oracle Portal. This means that any Discoverer worksheet - table, crosstab, or any of the 50+ graph types - can be published to an Oracle Portal page without any coding. This is the Discoverer Worksheet portlet.
A second Discoverer portlet is the List of Worksheets portlet, which allows you to publish a list of worksheets to a Portal page as a portlet.
The third Discoverer portlet type is the Gauge portlet. This allows you to publish a Discoverer crosstab worksheet as a Gauge (dial) visualization, allowing you to create dashboards.
For more information take a look at the "Oracle® Business Intelligence Discoverer Publishing Workbooks in Oracle Application Server Portal" doc, 10g Release 2 (10.1.2.1), Part No B14465-02
Thanks
Abhinav
Oracle Business Intelligence Product Management
BI on Oracle: http://www.oracle.com/bi/
BI on OTN: http://www.oracle.com/technology/products/bi/
Discoverer: http://www.oracle.com/technology/products/discoverer/
BI Software: http://www.oracle.com/technology/software/products/ias/devuse.html
Documentation: http://www.oracle.com/technology/documentation/appserver1012.html
BI Samples: http://www.oracle.com/technology/products/bi/samples/
Blog: http://oraclebi.blogspot.com/

Q: How to disable cache for a single portlet ?

Due to performance reasons I need to set the full page cache. But I have just one custom portlet on the home tab page which will count the logins. But the cache will prevent this portlet from getting the right value out of the DB. It would be pretty sad when I have to disable the full page cache because of this single portlet. I know that there's a way to set cache calls on portlet level. Can anyone shed a light on it. Thanks.

Hi Amjad,
I want to remove cache completely for a portlet. Is there any easy way of doing this. I tried to disable from Administer --> Cache. No luck.
I want to load the page every time from server. Please help me.
Thanks
Satyapal

Merge package into single PDF file

Hi, I am using Acrobat Professional 8 with Windows Vista.
How do I merge a PDF package into a single PDF file? Basically, I would like to convert a pdf package file into a "regular" PDF file. Thanks!
- Patrick

No solution here, but sounds like my similar problem. I converted a number of individual files to pdf format in hopes of converting it all to one pdf report. I can not seem to figure it out. I looked for the insert page approach but those items do not appear on the Acrobat 8 package. What am I doing wrong? If you are given a solution, please let me know. This effort has been ridiculous, there must be an easy solution that I am overlooking.

Multi packages or single package? Which is good?

we have a database (oracle 9) , 20-30 tables, we need create package, one suggestion is for each object create a package , each package have their own sp/function like new,delete,update... , thus will have 10-20 packages , another suggestion is create one package and include all sp/function in it, so the sp name will like object1_new,object1_delete,object2_delete,object2_update...
Which is more practise? what's the pro and cons between those 2?
Thanks!

Unless you're dealing with a tool that is automatically generating these APIs for every table, I'd go with neither of the above.
A package ought to contain a set of related methods that are used for similar business purposes. In general, that tends to mean that you'll have some packages that are just interfaces to a single table, some packages that provide interfaces to a number of related tables, and some tables that are manipulated by multiple packages. Where and how you draw those lines really depends on how your tables are used and how they relate to each other-- blindly creating a package per table is probably less than ideal here. On the other hand, creating a single package that's going to have hundreds of methods is clearly the worst option of all.
This question is conceptually very similar to the question of how long a procedure/ function/ method should be. There isn't going to be a fixed answer-- it's really going to depend on the situation.
Justin

Accessing a single portlet using an URL in a browser window

Is there a way to access a portlet alone using a URL and render it in a browser? Am able to access a service request form similarly using its service request id in the URL. But i don't find an URL for portlet to access it separately in a browser. I need to have a link in a page, which when clicked would open up the portlet in another tab of the browser.
Is this something possible?
Thanks,
Anish

Are you using the same extensions on both computers?
Start Firefox in <u>[[Safe Mode]]</u> to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).
* Don't make any changes on the Safe mode start window.
* https://support.mozilla.com/kb/Safe+Mode
* [[Troubleshooting extensions and themes]]

Multiple upgrade packages from single serial

This may be a strange question. I have a machine running Final Cut Studio 2 (upgrade copy) and I want to expand to another machine. Can I purchase a couple of upgrade copies of the new FCStudio and upgrade both my original machine and my new one from my single FCS 2 upgrade license?

Don't think so, but you can have fcp installed on both a desktop and laptop from one license (but you're not supposed to run them at the same time)

Step 1. Writing The Package Specification For Portlet Provider

I get this message when I try...
$ sqlplus user/passwd@tnsname
ERROR:
ORA-06401: NETCMN: invalid driver designator
The same is true for trying to connect via srvmgrl. Tnsping and Net8 Assistant can connect with the database fine.
The client is Mandrake 7.1 with Oracle 8.1.6 and the server I'm trying to connect to is 8.1.5 on WinNT 4.0.
Any ideas would be greatly appreciated.
Thanks,
Don Farland

http://ee-staff.ethz.ch/~oetiker/webtools/mrtg/users.html

Is it possible inscribe all the packages into a single package ??

Hi,
In Oracle 10g , Is it possible inscribe all the packages into a single package ??
Because, my PM Is asking me to inscribe all the Packages into Single Package and give same reference to the .Net developers.
I have tried a lot, but i am not finding out the right solution for this ., and even i am bit confused whether is this possible or not.
Can any one please suggest me how to achieve this it it's possible in Oracle.

You mean something like...
-- First package with functions in it...
SQL> create package mypack1 as
2    function myfunc1 return number;
3 end;
4 /
Package created.
-- assume a package body is created for this as well
-- Second package with functions in it...
SQL> create package mypack2 as
2    function myfunc2 return number;
3 end;
4 /
Package created.
-- assume a package body is created for this as well
-- One package encompassing other packages...
SQL> create package allpacks as
2    function myfunc1 return number;
3    function myfunc2 return number;
4 end;
5 /
Package created.
SQL> create package body allpacks as
2    function myfunc1 return number is
3    begin
4      return mypack1.myfunc1;
5    end;
6
7    function myfunc2 return number is
8    begin
9      return mypack2.myfunc2;
10    end;
11 end;
12 /
Package body created.
SQL>;)

JSR168 portlet packaging?

From the JSR168 spec, (which is similar to how other portals seem to behave
with their proprietary APIs), a JSR168 portlet application appears to be a
WAR with a portlet.xml and web.xml conforming to the requirements of the
spec, that can then be installed in any portal.
From my superficial knowledge based on skimming the WL8.1 portal docs
recently, WL portlet development appears to be done within a Portal WAR such
that the portlet(s) are just components of the portal war itself.
How are these two supposed to work together in the WLP env? Say I develop a
couple JSR168 portlets in my own Java environment (emacs :-) and then WAR
them up and install them into Jetspeed-2 and another 168 compliant portal
when available (eg, IBM's 5.something). I believe those would accept my
portlet WAR and keep them in that WAR and just reference them from their
Portals. How would WL8.1.x handle such development (outside of Workshop/WL)
and deployment to a WL8.1.x portal? Do I have to merge my JSR168 based
portlet WAR (and thus a web.xml and portlet.xml merge) into the Portal WAR
(eg, if I want to ship a script to deploy my portlet WAR into an existing
WL8.1 portal?) or will WL8.1.x be able to reference a Portlet WAR outside of
a Portal WAR?
TIA - a confused potential portlet developer...

I agree with what Joe said...
BTW, I (and I assume Joe) think JSR168 is a good thing - and it's great that
WLP has the first prototype of it out there - don't get me wrong, I like it,
I'd just prefer if it were easier to deploy to given portlets coming in from
multiple sources being added into an existing portal. From Joe's case, he
probably doesn't want to have to merge the portlet.xml files. From my case
as a supplier of portlets, I'd rather not have to have to create different
install tools/docs/procedures for my customers for each portal vendor now
that I can have standard portlets based on JSR168...
"Joe C." <[email protected]> wrote in message
news:[email protected]...
You can always import any arbitrary webapp using the WLW as a portalproject
I'm not sure that solves my problem or the one ISV was talking about(which
I assume is the same).
I am not talking about importing a webapp (containing portlets or nto) and
making it be my portal.
- Assume I'm already developing a portal with some in-house developed
portlets.
- I want to get 3 JSR168 portlets from SAP (just picked a random vendorout
of the air) and add them to my portal.
- I want to get 2 JSR168 portlets from Siebel (ditto)
- And I need one Domino portlet from that other 3 letter vendor (ditto)
- Each of those vendors is likely to build JSR168 portlets that can be
installed/used in any JSR168 compliant portal, so they can stop buildingall
the various per-vendor proprietary API portlets.
- Each of those vendors needs to package up their portlets for
shipping/install.
- Given that JSR168 describes the Web App layout for packaging a portlet,
each of those vendors is likely to package their portlets up in a WAR.
- Some JSR168 compliant portals (I believe) will be able to just install
those WARs and use them as is from the Portal WAR and drop them on pages.
- WLP 8.1 appears to require that I unpack/extract those WARs and mergethe
portlet.xml and contents of each of those WARs with my existing Portal WAR
that I want to add those portlets to. Tell me why this is better?
To your earlier comments made here:
The pitfall of this approach is that webapps depend on each other towork correctly
Well yeah, I expect my portal to depend on my portlets - of course.
which is against the spirit of webapps.I disagree - EARs depend on the WARs within them. Cooperating WARs can
depend on each other too.
A deployer should be able to deploy/undeploy any webapp withoutaffecting the functionality of other
webapps - which would be case in the model you describe.Of course, if you remove a portlet that a portal depends on, I wouldexpect
it to break .
In addition, there are security issues that the deployer must be awareof.
Of course. That's the case with any J2EE deployment no matter how many
EARs/WARs you're deployiing.
"Subbu Allamaraju" <[email protected]> wrote in message
news:[email protected]...
Joe,
You can always import any arbitrary webapp using the WLW as a portal
project, and during that process you'll have the opportunity to
automatically update the descriptors (and also adding the correct jar
files). There is no need to hand-merge descriptors unless you want to.
Subbu
Joe C. wrote:
Please tell me it's going to get better.
That would make sense if one were developing all their own portlets
for
their portals.
But I (and most people I know) as a customer, that needs to aggregate
portlets from multiple (possibly many) 3rd parties, such as the big 4
application vendors, am going to need to know how those standardJSR168
portlets work and are configured so that I can hand-merge them into my
company's portal?
As an end user it doesn't really help me that much that I can developmy
own
portlets to JSR168. The whole point of JSR168 is that portlet vendorsthat
build portlets for others to install into their portals will be able
to
build one set of portlets that can then be installed in any compliant
portal. This limitation seems to prevent that from beingcommonplace/useful
(given how few people are going to know how to do such merges - theyjust
want to install 3rd party portlets and drop them on pages). I reallyhope
Workshop provides a user friendly way to integrate such 3rd party
JSR168
portlets or WLP will be missing the whole point of having such astandard in
the first place. I agree with the ISV that started this
conversation -
please provide a means for me to install 3rd party portlets withouthaving
to hand-merge XML configuration files.
"Subbu Allamaraju" <[email protected]> wrote in message
news:[email protected]...
isv wrote:
From the JSR168 spec, (which is similar to how other portals seem to
behave
with their proprietary APIs), a JSR168 portlet application appears to
be
a
WAR with a portlet.xml and web.xml conforming to the requirements of
the
spec, that can then be installed in any portal.For all practical purposes, a portal app is a web app, with the only
differece being the portlet.xml file. So, a portal app contains
portlets
in addition to things that typically exist in a webapp.
How are these two supposed to work together in the WLP env? Say I
develop a
couple JSR168 portlets in my own Java environment (emacs :-) and thenWAR
them up and install them into Jetspeed-2 and another 168 compliantportal
when available (eg, IBM's 5.something). I believe those would accept
my
portlet WAR and keep them in that WAR and just reference them fromtheir
Portals. How would WL8.1.x handle such development (outside ofWorkshop/WL)
and deployment to a WL8.1.x portal? Do I have to merge my JSR168
based
portlet WAR (and thus a web.xml and portlet.xml merge) into thePortal
>>>
WAR
(eg, if I want to ship a script to deploy my portlet WAR into anexisting
WL8.1 portal?) or will WL8.1.x be able to reference a Portlet WARoutside of
a Portal WAR?For WLP, the unit of development/deployment is a webapp. We're aware
that some implementations (including the ones you mention) follow a
model where portal deployment involves several web apps with portlets
aggregated by a portal deployed in one of those webapps. The pitfall
of
this approach is that webapps depend on each other to work correctly -
which is against the spirit of webapps. A deployer should be able to
deploy/undeploy any webapp without affecting the functionality ofother
webapps - which would be case in the model you describe. In addition,
there are security issues that the deployer must be aware of.
Having said this, if your portlets are already bundled into a WARfile,
you need to merge the portlets into the portal webapp. Or, you couldlet
WL convert your webapp into a portal webapp. We don't intend tosupport
portlet referencing from other webapps.
Subbu

Trying to call Jasper iReport through portlet & getting error

Hi,
I have written the following code which is linked to a button in my portlet.
package com.ext.portlet.drpdwn.action;
import com.liferay.portal.struts.PortletAction;
import com.liferay.portal.util.Constants;
import javax.portlet.WindowState;
import javax.servlet.jsp.PageContext;
import javax.portlet.ActionRequest;
import javax.portlet.ActionResponse;
import javax.portlet.PortletConfig;
import javax.portlet.RenderRequest;
import javax.portlet.RenderResponse;
import org.apache.struts.action.ActionForm;
import org.apache.struts.action.ActionForward;
import org.apache.struts.action.ActionMapping;
import java.io.IOException;
import java.io.PrintWriter;
import java.io.StringWriter;
import java.util.HashMap;
import java.util.Map;
import java.sql.*;
import javax.portlet.PortletException;
import net.sf.jasperreports.engine.*;
import net.sf.jasperreports.engine.design.JasperDesign;
import net.sf.jasperreports.engine.xml.JRXmlLoader;
import net.sf.jasperreports.engine.export.*;
public class QualityReportAction extends PortletAction
     public void processAction(ActionMapping mapping, ActionForm form,PortletConfig config,ActionRequest req, ActionResponse res)
throws Exception
          String typeofreport_val = req.getParameter("types_of_reports").trim();
          System.out.println("Report Name is:" +typeofreport_val);
          JasperReport jasperReport;
          JasperPrint jasperPrint;
          JasperDesign jasperDesign;
          Connection connection = null;
          if ( null == typeofreport_val || "".equals("typeofreport_val"))
               setForward(req,"portlet.ext.drpdwn.error");
          else
               try
                    Class.forName("org.postgresql.Driver");
                    String url = "jdbc:postgresql://10.10.33.39:5432/globus_db?user=postgres&password=marines@123";
                    connection = DriverManager.getConnection(url);
                    // load JasperDesign from XML and compile it into JasperReport
                    jasperDesign = JRXmlLoader.load("C:/testRep/CCQR.jrxml");
                    jasperReport = JasperCompileManager.compileReport(jasperDesign);
                    // fill JasperPrint using fillReport() method
                    jasperPrint = JasperFillManager.fillReport(jasperReport,null,connection);
                    JasperExportManager.exportReportToPdfFile(jasperPrint,"C:/testRep/ccqr.pdf");
               catch (SQLException ex)
                    setForward(req,"portlet.ext.drpdwn.error");
                    System.out.println("-------------------------------------------");
                    while (ex != null)
                         ex.printStackTrace();
                         ex = ex.getNextException();
                    System.out.println("-------------------------------------------");
               catch(Exception e)
                    System.out.println("-------------------------------------------");
                    System.out.println("Exception is --> "+e);
                    System.out.println("-------------------------------------------");
               setForward(req,"portlet.ext.drpdwn.success");
     public ActionForward render(ActionMapping mapping,ActionForm form,PortletConfig config, RenderRequest req,RenderResponse res) throws Exception
          if (getForward(req) != null && !getForward(req).equals(""))
               return mapping.findForward(getForward(req));
          else
               return
               mapping.findForward("portlet.ext.drpdwn.view");
}When I try to run this code I get the following error:
exception javax.servlet.ServletException: Servlet execution threw an exception
     com.liferay.filters.secure.SecureFilter.doFilter(SecureFilter.java:144)
     com.liferay.portal.servlet.filters.virtualhost.VirtualHostFilter.doFilter(VirtualHostFilter.java:136)
     com.liferay.portal.servlet.FriendlyURLServlet.service(FriendlyURLServlet.java:126)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
     com.liferay.filters.strip.StripFilter.doFilter(StripFilter.java:95)
     com.liferay.filters.secure.SecureFilter.doFilter(SecureFilter.java:144)
     com.liferay.filters.compression.CompressionFilter.doFilter(CompressionFilter.java:116)
     com.liferay.filters.doubleclick.DoubleClickFilter.doFilter(DoubleClickFilter.java:138)
     com.liferay.portal.servlet.filters.layoutcache.LayoutCacheFilter.doFilter(LayoutCacheFilter.java:170)
     com.liferay.portal.servlet.filters.autologin.AutoLoginFilter.doFilter(AutoLoginFilter.java:106)
     com.liferay.portal.servlet.filters.virtualhost.VirtualHostFilter.doFilter(VirtualHostFilter.java:136)
root cause java.lang.NoClassDefFoundError: net/sf/jasperreports/engine/xml/JRXmlLoader     com.ext.portlet.drpdwn.action.QualityReportAction.processAction(QualityReportAction.java:59)I have the following necessary files in my class path:
itext-1.3.1.jar
iReport.jar
commons-logging-1.0.2.jar
commons-javaflow-20060411.jar
commons-digester-1.7.jar
commons-collections-2.1.jar
commons-beanutils-1.7.jar
jasperreports-2.0.2.jar
jdt-compiler-3.1.1.jar
log4j-1.2.15.jar
xercesImpl.jar   Please suggest me where I am going wrong.
Thanks & Regards
Saurabh.
Edited by: Saurabh.J on Nov 27, 2007 2:33 PM

Disable your anti-virus, install the update, turn you anti-virus back on

What are the steps to setup JavaMail in JDeveloper for Oracle Portlet??

Dear all,
I had got a problem in using JavaMail in JDeveloper.
I am developing a Oracle portlet (actually, it is an online applicatin form for user submission.).
After user submitted the form, the portlet will send email automatically to someone else for notification. The logic is straight forward.
I faced a problem on how to setup the environment for calling JavaMail API.
As far as I know, JavaMail is included in J2EE platform, so I guess I need to put JavaMail classes in the import directives, i.e.
import="java.util.Properties"
import="javax.mail.*"
import="javax.mail.internet.*"
But, when compile the program, error messages are resulted that JavaMail classes not found.
Can anyone help me?
thanks
George (HK)

Dear all,
I switched to use the utl_smtp package for my portlet email function instead of using JavaMail in Portlet.
But, I still want to know the steps and procedures which I need to take in order to invoke JavaMail in Oracle Portlet development. Anyone any ideas?
thanks a lot
George (HK)

Announcing: Developing JSF Portlets with WebLogic Portal Whitepaper

Just Released: Developing JSF Portlets with WebLogic Portal Whitepaper
A supplemental developer's guide has been published to help guide WLP 10.x customers that wish to use JSF as the web framework for building portlets on WebLogic Portal. This is a sizable document (150 pages) that covers a large number of topics. It also coaches developers on best practices and common pitfalls.
Important: It also clarifies the supported configuration of JSF within Portal Web Projects. Workshop for WebLogic by default configures a web project in a configuration that is not supported by WebLogic Portal. The guide explains how to address this:
* Change from the unsupported MyFaces JSF implementation to the supported Sun Reference Implementation (RI)
* Change from the unsupported "client" STATE_SAVING_METHOD to the supported "server"
The guide can be downloaded here:
http://download.oracle.com/technology/products/weblogic/portal/weblogic-portal-jsf-whitepaper.pdf
To help internet searches locate this document, the table of contents is reproduced below:
Introduction
1.1. Prerequisites...................................................................... 8
1.2. Applicable Versions............................................................ 8
1.3. Native Portlet Bridges and Standard Portlet Bridges .......... 8
1.4. JSF Portlet Support Roadmap ........................................... 9
1.5. Whitepaper Structure ....................................................... 10
1.6. Look Before You Leap ..................................................... 10
1.7. For More Information........................................................ 10
Part 1: Converting JSF Applications into Portlets
2. IDE Support for JSF Portlets Chapter ...................................... 12
2.1. Workshop for WebLogic – WebLogic Portal's Supported IDE 12
2.2. Workshop Features for JSF Support in WebLogic Portal.. 12
3. Introduction to JSF Portlets Chapter ........................................ 18
3.1. Creating Your First JSF Portlet......................................... 18
3.2. Essentials of JSF Portlet Views........................................ 21
3.3. WebLogic Portal Artifacts................................................. 22
4. Configuring JSF within WebLogic Portal Chapter..................... 24
4.1. JSF Library Modules in WebLogic Server ........................ 24
4.2. Installing the JSF Libraries into a Portal Web Project ....... 25
4.3. JSF Configuration Settings............................................... 27
4.4. Configuring JSF 1.2 ......................................................... 29
4.5. Building an Unsupported JSF Implementation Library Module 31
4.6. Faces Configuration is Web Application Scoped.............. 31
5. Navigation within a JSF Portlet Chapter................................... 33
5.1. Navigating within a Portlet with the JSF Controller ........... 33
5.2. Redirects.......................................................................... 34
6. Namespacing Chapter ............................................................. 35
6.1. Namespacing Managed Bean Names.............................. 35
6.2. Client ID Namespacing with the View and Subview Components 35
6.3. Client ID Namespacing with the WLP NamingContainer .. 36
7. Logging, Iterative Development, and Debugging Chapter ........ 39
7.1. Logging............................................................................ 39
7.2. Iterative Development ...................................................... 39
7.3. Debugging ....................................................................... 40
8. Custom JavaScript Chapter ..................................................... 42
8.1. DOM Manipulation within a JSF ....................................... 42
8.2. Form Validation within a JSF Portlet ................................ 45
9. Preparing JSF Portlets for Production Chapter ........................ 46
9.1. Configuration.................................................................... 46
9.2. Performance and Scalability............................................. 47
9.3. Security............................................................................ 49
9.4. Localization...................................................................... 50
Part 2: Interacting with the Portal Environment
10. Native Bridge Architecture Chapter ...................................... 54
10.1. Container Architecture Overview.................................. 54
10.2. Container Architecture.................................................. 54
10.3. Container Interactions .................................................. 55
11. Interportlet Communication Chapter .................................... 56
11.1. Using Session and Request Attributes for IPC (Anti-pattern) 56
11.2. Using the WLP Event Facility for IPC with JSF Portlets 56
11.3. Notifications ................................................................. 60
11.4. Comparison of the IPC Approaches ............................. 60
12. Scopes Chapter ................................................................... 62
12.1. Conceptual Scopes for Standard JSF Applications ...... 62
12.2. Conceptual Scopes for Portal Applications................... 63
12.3. Implementation Patterns for Portal Scopes .................. 63
13. State Sharing Patterns Chapter ........................................... 66
13.1. State Sharing Concepts ............................................... 66
13.2. HttpSession Versus HttpServletRequest ...................... 66
13.3. Base Code for HttpSession Patterns ............................ 67
13.4. Single Portlet Pattern ................................................... 68
13.5. Multiple Portlet Patterns ............................................... 69
14. Rendering Lifecycles Chapter .............................................. 77
14.1. WLP and JSF Lifecycles .............................................. 77
14.2. Invocation Order of WLP and JSF Lifecycle Methods... 77
14.3. Accessing WLP Context Objects from JSF Managed Beans 78
15. Portal Navigation Chapter .................................................... 80
15.1. Programmatically Constructing JSF Portlet URLs ........ 80
15.2. Changing the Active Portal Page.................................. 80
15.3. Redirects within a Portal............................................... 83
16. Ajax Enablement Chapter .................................................... 85
16.1. Ajax in JSF Portlets...................................................... 85
16.2. Partial Page Rendering Pattern.................................... 85
16.3. Stateless API Request Pattern ..................................... 86
16.4. Portlet Aware API Request Pattern .............................. 87
16.5. Controlling the WLP Ajax Framework........................... 91
17. Additional WLP Features Chapter........................................ 93
17.2. Portlet Container Features ........................................... 93
17.3. Portal Container Features ............................................ 98
18. Example: Implementing a Login Portlet Chapter .................. 99
18.1. Login Portlet Motivation................................................ 99
18.2. Login Portlet Design..................................................... 99
18.3. Login Portlet Implementation...................................... 101
Part 3: Integrating Third Party Libraries
19. Integration Overview Chapter............................................. 111
19.1. Types of Libraries....................................................... 111
19.2. Roadmap for MyFaces Trinidad and ADF Faces Rich Client 111
20. Using the Facelets View Technology Chapter.................... 113
20.1. Introduction to Facelets .............................................. 113
20.2. Configuring Facelets Support ..................................... 113
21. Using the Apache MyFaces Tomahawk Component Library Chapter 115
21.1. What is Apache MyFaces Tomahawk? ...................... 115
21.2. Support for Tomahawk in WLP................................... 115
21.3. Tomahawk Component List........................................ 116
21.4. Installing and Configuring Tomahawk......................... 119
21.5. Resolving the Duplicate ID Issue................................ 120
21.6. Referring to Resources .............................................. 120
21.7. forceId Attribute.......................................................... 124
21.8. File Upload................................................................. 125
22. Using the Apache Beehive Navigation Controller Chapter . 126
22.1. Apache Beehive Page Flow ....................................... 126
22.2. JSF and Page Flows .................................................. 126
22.3. Configuring the JSF Integration with Page Flows ....... 127
Appendices
23. Appendix 1: Consolidated List of Best Practices ................ 130
24. Appendix 2: Known Issues and Workarounds.................... 132
24.1. CR383659, CR383662 Inconsistent failures with JSF portlets 132
24.2. CR342124: IllegalStateException due to duplicate client-id 132
24.3. CR384916: IllegalStateException due to duplicate client-id when using certain components such as Tomahawk and Trinidad...... 133
24.4. CR361477 Problems with the integration of JSF portlets with Apache Beehive Page Flows.................................................................. 133
24.5. CR377945 JSF 1.2 suffers from a memory leak during iterative development .............................................................................. 134
25. Appendix 3: The JSFPortletHelper Class ........................... 135
26. Appendix 4: The CleanupPhaseListener Class .................. 147

Hi Peter!
First, I wish to thank you for the great work.
We followed your whitepaper and managed to deploy a JSF portlet on WLS.
But we are not able to register it (consume it) as remote portlet in Oracle Portal 10.1.4. The error log is as follows:
An error occurred while trying to refresh the provider. (WWC-43190)
An error occurred during the call to the WSRP Provider:
java.rmi.RemoteException: serialization error: serialization error:
unexpected null value for literal data; nested exception is:
serialization error: serialization error: unexpected null value for literal data
com.sun.xml.rpc.encoding.SerializationException: serialization error:
serialization error: unexpected null value for literal data
com.sun.xml.rpc.encoding.SerializationException: serialization error:
unexpected null value for literal data
Java stack trace from root exception:
unexpected null value for literal data
at
oracle.webdb.wsrp.RegistrationContext_LiteralSerializer.doSerialize(RegistrationContext_LiteralSerializer.java:107)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
at
oracle.webdb.wsrp.GetServiceDescription_LiteralSerializer.doSerialize(GetServiceDescription_LiteralSerializer.java:88)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
at
com.sun.xml.rpc.client.StreamingSender._writeRequest(StreamingSender.java:473)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:62)
at
oracle.webdb.wsrp.WSRP_v1_ServiceDescription_PortType_Stub.getServiceDescription(WSRP_v1_ServiceDescription_PortType_Stub.java:63)
at
oracle.webdb.wsrp.client.design.v1.OraWSRP_v1_ServiceDescription_PortType.getServiceDescription(Unknown
Source)Do you have any idea why this happens? Or you can provide some useful links to WLP -Oracle Portal federation?
Thank you and best regards,
PaKo

Packaging a single Portlet

Similar Messages

Maybe you are looking for