On a recent Oracle Portal-based project, I wanted to use JSR-168 portlets. Both because it’s always good to follow the standard if there is one, and because Oracle is not quite clear about whether JPDK portlets will be supported in Oracle WebCenter 11g.
Being used to Oracle portlets, where we’ve had parameters forever, I was much surprised to discover that JSR-168 portlets are completely stand-alone and do not take parameters. This feature only comes in JSRT-268, which is still being finalized.
JDeveloper 10.1.3 and later will build JSR-268 portlets (using Oracle’s understanding of the standard), but Oracle Portal 10.1.4 doesn’t understand the WSRP 2.0 communication used by JSR-268 portlets.
So there is still a place for JPDK portlets…
|PL/SQL||PL/SQL||Oracle Portal only||Yes|
|JPDK||Java||Oracle Portal only||Yes|
|JSR-168||Java||All standard portals||No|
|Java||All standard portals||Yes|