Now pass the actual Object contextValue into the DisplayEvent, instead of the String value of that object.

TRUNK
Subversion 20864
icefaces\component\src\com\icesoft\faces\component\paneltooltip\PanelTooltip.java

icefaces-ee-1.8.2
Subversion 20865
icefaces\component\src\com\icesoft\faces\component\paneltooltip\PanelTooltip.java

Verified with success on ICEfaces-ee-1.8.2 revision 20874 using Tomcat 6 + FF3.5 and IE8

Test app is checked into repo\qa\trunk\Regression\ICE-5351

Found in nightly regression test that the test application throws NullPointerException on Tomcat 5, while it's working fine on Tomcat 6.

Test app is available at C:\repo\qa\trunk\Regression\ICE-5351, which can be built for Tomcat 5 using: ant clean tomcat5.x

Found out that with JSF 1.1 + JSP, the tags are executed and rendered as they go, without a separate render call once the tree is fully in place, like Facelets and JSF 1.2 + JSP do. That has the side-effect that you can't use panelToolip, menuPopup, for, or any other attribute that refers to another component, and have that component later on (lower) in the component tree, since the component won't exist yet. Changed the test to work with JSF 1.1 + JSP by moving the panelTooltip component to be before (above) the panelGroup that refers to it.

Next, we made the test cover both the scenario of using a String value, and the scenario of using a complex data-type as the contextValue.

Thanks to Mark. It has been verified that it's a test application issue rather than ICEfaces.
The test app has been adjusted and tested successfully on both Tomcat 5, 6 using FF3.5 and IE8.

Updated test app and selenium test scripts have been committed.