I was a bit surprised to run across this issue for the first time in a 10.3.0 installation. According to a post on OTN, it is caused by the actual Beehive library not added correctly in config.xml. However, when I ran across it, it was a different library (the sample projects) that were missing, but the same error occurred.
Go figure.
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”);
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: