If you chose the Facelet aspect for your WLP project in 10.3.2, your portlets will use the “native” (i.e., WLP-only) portlet bridge rather than the “JSR-329” (i.e., crystal ball) bridge. In case you need to reuse your portlets in another portal framework.
I haven’t had time to try it out, but in theory one could write the .portlet file by hand and still get the best of both worlds.
If you see:
java.lang.ClassCastException: com.bea.portlet.container.ActionRequestImpl
Try adding the following:
import javax.portlet.ActionRequest;
…
ActionRequest actionRequest = (ActionRequest) ctx.getExternalContext().getRequest();
HttpServletRequest httpRequest = (HttpServletRequest) actionRequest.getAttribute(“javax.servlet.request”);
Go to Oracle WebLogic Portal 10gR3 (10.3.2) for the download.
From the description on the product page, this is a new version of WebLogic Workshop, but without the WebLogic Portal tools. WLP has a new release due out soon, and Oracle is focusing on their other IDE, so this makes sense, even if it doesn’t make old-time WebLogic developers feel all warm and fuzzy (or remembered).
I ran across this while working on tweaking some of my own flows. As luck would have it, I never got a chance to test it out, but wanted to keep a note on it just in case I run across it again: