I haven't been able to successfully deploy the attached portlet on Apache Pluto 2.0.2. I'm able to add the portlet to a page, but when I try to view the page I get this exception, displayed right on the browser:

Error rendering portlet 1.
javax.portlet.faces.BridgeException: javax.faces.FacesException: Expression Error: Named Object: com.liferay.faces.portlet.component.renderurl.RenderURL not found.
	at com.liferay.faces.bridge.internal.BridgePhaseRenderImpl.execute(BridgePhaseRenderImpl.java:105)
	at com.liferay.faces.bridge.internal.BridgeImpl.doFacesRequest(BridgeImpl.java:131)
	at javax.portlet.faces.GenericFacesPortlet.doView(GenericFacesPortlet.java:263)
	at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:348)
	at javax.portlet.faces.GenericFacesPortlet.doDispatch(GenericFacesPortlet.java:212)
	at javax.portlet.GenericPortlet.render(GenericPortlet.java:253)
	at org.apache.pluto.driver.services.container.FilterChainImpl.doFilter(FilterChainImpl.java:163)
	at org.apache.pluto.driver.services.container.FilterChainImpl.processFilter(FilterChainImpl.java:91)
	at org.apache.pluto.driver.services.container.FilterManagerImpl.processFilter(FilterManagerImpl.java:105)
	at org.apache.pluto.container.driver.PortletServlet.dispatch(PortletServlet.java:340)
	at org.apache.pluto.container.driver.PortletServlet.doGet(PortletServlet.java:261)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	...

I tried to simplify the portlet to make it only display the dateTimeEntry component, but I keep getting the same exception.

I followed the steps exactly as they appear in the description. Am I missing a step or do I need to add a library or something else to Pluto?

After being able to test the portlet, this seems to be a more general issue with the bridge. The same javascript error occurs when entering text in the other text fields in the form, such as 'First Name', and then tabbing out.

I traced the error, and it occurs at the fixAlreadyNamespacedOptions() function, called from the fullSubmit() function. The error occurs when trying to get the length of the 'parameterPrefix' argument, which is undefined on Pluto, whereas, on Liferay, it's an empty string.

Perhaps, this could be fixed by modifying the first line of fixAlreadyNamespacedOptions() from...

var length = parameterPrefix.length;

to...

var length = parameterPrefix ? parameterPrefix.length : 0;

...or maybe this new line should be inserted first, since parameterPrefix is used later on

parameterPrefix = typeof parameterPrefix != 'undefined' ? parameterPrefix : '';

When you get an opportunity, please let me know what part of the ICEfaces source code is responsible for rendering the <span>...</span> you mentioned.

org.icefaces.impl.event.BridgeSetup class, line 157.

Are you saying that the script is getting rendered in Liferay Portal but not in Pluto?

No, Liferay will not render the script tag. But at least it renders its content in a different place:

<div id="bottomJS">
    .....
</div>
<script type="text/javascript">
.....ice.setupBridge("_1_WAR_icefaces4portlet_INSTANCE_vV75ldMObRSc_:vv20q4nh4_icefaces_config","v20q4nh4","jdiky5fkvu",{reloadOnUpdateFailure:!1,deltaSubmit:!1,focusManaged:!0,disableDefaultErrorPopups:!1,standardFormSerialization:!1,sendDisposeWindow:!1,blockUIOnSubmit:!1,clientSideElementUpdateDetermination:!1,parameterPrefix:""}); .......
</script>

Is it OK that it Liferay renders it at the bottom of the page? That is a Liferay-only optimization that we have in the bridge. If it is not rendered at all in Pluto, then that means we have a bug in the bridge and this issue can be closed.

Yes, it's fine if the script is rendered at the bottom of the page. I'll close the issue then.

This is not an issue with ICEfaces. See above.

This issue is a bug in Liferay Faces. We have created FACES-2615 to track the issue, and I hope to commit a fix today.