JSF don't find component in view root with the form id

Question

I have a t:inputFileUpload inside the form, in the html of the display page the id of this component is form:inputFile but when I tried to get the component from the view root using "form:inputFile" the return is null, but when the "form:" is removed the return is the component. The component don't set the value in my managed bean, someone have this problem?

EDIT:

<h:form id="form" enctype="multipart/form-data">
<t:inputFileUpload id="inputFile" size="40" value="#{managedBean.inputFile}"/>
</h:form>

In the managed bean:

    private UploadedFile inputFile;

with the gets and sets provided by Eclipse.

//This method scans the view root and returns the component with the id passed as parameter
findComponentInRoot("form:inputFile");

This returns null, but when I use:

   //This method scans the view root and returns the component with the id passed as parameter
    findComponentInRoot("inputFile");

The return is the component I'm looking for, but when I use the View Source in Internet Explorer the id of this component is "form:inputFile".

I don't know if this is related, but the component don't set the value in my managed bean and it's strange the fact that the id of the component is different from the HTML source. I'm using JSF 1.2 Mojarra. Someone else has this problem? Or know why this happens?

EDIT2: Okay, I'm very stupid, aparently the build wasn't working correctly and when the build was changed to other task from the Ant it worked (still don't know why, but simply worked). Sorry for the trouble.

Answer 1

I guess findComponentInRoot is this (a minor detail you should've shared).

Anyway, using findComponent(..) or getChildren(..) always return the id of the components as defined in the page. The html id is something different that consists of the naming container:id.

Answer 2

You should use component binding or UIViewRoot#findComponent(). But that won't solve the problem of the uploaded file not being set. To fix it, first step is to ensure that you definied and configured the ExtensionsFilter properly as per the Tomahawk documentation, since it is the one responsible for parsing the multipart/form-data request and putting all the parameters among with the uploaded file back in the request parameter map, so that the FacesServlet can apply them and update the model values.