problem by getting values from h:form

i'll make it short:

i have this jsp with a form:

<hx:viewFragment id="registration">
<hx:scriptCollector id="scriptCollector1">
<div
style="margin: 20px; padding: 10px; border: 2px dashed #aaa; background-color: #eee"
id="WebDiagramContributions"><span
style="font: bold 12pt sans-serif">Register for access to the
TEC Solution Manager.</span><span style="font:  10pt sans-serif">.</span><br>
<br>
Enter the registration data...<br>
 
<h:form styleClass="form" id="form">
<table>
<tr>
<td>Lastname:</td>
<td><h:inputText id="lastname" value=""></h:inputText></td>
</tr>
<tr>
<td>Firstname:</td>
<td><h:inputText id="firstname" value=""></h:inputText></td>
</tr>
<tr>
<td>Username:</td>
<td><h:inputText id="username" value=""></h:inputText></td>
</tr>
<tr>
<td>E-Mail:</td>
<td><h:inputText id="email" value=""></h:inputText></td>
</tr>
<tr>
<td><br>
</td>
<td></td>
</tr>
<tr>
<td>Password:</td>
<td><h:inputSecret id="password1" styleClass="inputSecret"
value=""></h:inputSecret></td>
</tr>
<tr>
<td>Confirm Password:</td>
<td><h:inputSecret id="password2" styleClass="inputSecret"
value=""></h:inputSecret></td>
</tr>
</table>
<br>
<hx:commandExButton value="Submit"
action="#{pc_Register.doRegistration}" styleClass="commandExButton"
id="button1"></hx:commandExButton>
<br>
</h:form></div>
 
 
 
</hx:scriptCollector>
</hx:viewFragment>

now i'm trying to get for example the username like this:

this.getFacesContext().getExternalContext().getRequestParameterMap().get("registration:scriptCollector1:form:username");
i just get null.

with this call i get an array with all the parameters from the form.
this.getFacesContext().getExternalContext().getRequestParameterMap().values().toArray();
[ January 17, 2008: Message edited by: Chrigi Pfister ]

got it!

this.getFacesContext().getExternalContext().getRequestParameterMap().get("subview1:registration:form:username");

I hope there was a good reason for all this. If you'd just mapped the properties of a backing bean to the form, the'y be pushed into the bean via its property setters automatically and you wouldn't have had to code arcane JSF service calls. Or, for that matter, any calls at all.

no, there was no good reason ;-)

i was not aware of the possibilities with JSF, now i know better.

Here's a good rule for JSF:

Any JSF problem that results in a complex solution probably has a much cleaner and simpler one.

And its corollary:

The best JSF code is code that doesn't include any explicit JSF references in it at all.