Does JSF 1.2 treat client ID's differently? The reason that I ask is that the file upload component is not working in JBoss Portal (which comes with JSF 1.2) but it is working in Liferay (using JSF 1.1).

When I look at the rendered out HTML of the two and compare, it appears that the client ID supplied by the <ice:portlet> tag is rendered all the way down the tree in Liferay. For example, in Liferay the <ice:portlet> renders out to:

...
<div id="_components_fileUpload_WAR_componentshowcase_INSTANCE_mbUk_">
...

and then later, when the iframe for the file upload is rendered, the hidden input that identifies the fileupload section looks like this:

...
<input type="hidden"
       name="ice.component"
       value="_components_fileUpload_WAR_componentshowcase_INSTANCE_mbUk_:ifSub:iceform:icepnltabset:0:inputFileName"/>
...

Now if we look at exactly the same thing running under JBoss Portal, we get this from the <ice:portlet> tag:

...
<div id="jbpns_2fdefault_2fShowcase_2fFile_20Uploadsnpbj">
...

And this is the hidden input:

<input type="hidden"
       name="ice.component"
       value="j_id2:ifSub:iceform:icepnltabset:0:inputFileName"/>

So you see that the portlet component's id is not pre-pended. It's generated some default one. The whole thing is failing in our UploadServer where it calls the D2DViewHandler logic in findComponent the result is always "null" and I assume it's because of this ID discrepancy. Anyone able to educate me on why this is?