Password Input Field
Description
The password field allows masked user input to accept password values. Normally, a spec is created with 2 'pwd' elements to allow equality validation (below) and ensure the user typed the password correctly. The password field also allows multiple validators (see below). This is a very powerful feature for chaining validation operations based on user input.
Example
<field type="password" align="left" variable="the.password">
<spec>
<pwd txt="The Password:" size="25" set=""/>
<pwd txt="Retype Password:" size="25" set=""/>
</spec>
</field>Comments
The validation and therefore the update of the field values will not take place at leafing of the password field but only on prior advancement to the next panel. You could run the database connection test within a panel validation for example, that would prevent advance to a followup panel if it fails for example.
I just needed an implementation with a db connection check on my button, and if the check was not true, the user could still go further.
I found a solution to add dependency with clsass
com/izforge/izpack/panels/userinput/gui/password/GUIPasswordGroupField
where Overridea ddComponent
public void addComponent(JComponent component, Object constraints) {
// Check if the component being added is the one we're interested in.
if (component instanceof JPasswordField) {
JPasswordField passwordField = (JPasswordField) component;
// Add our listener to update the variable on focus loss.
passwordField.addFocusListener(new FocusAdapter() {
@Override
public void focusLost(FocusEvent e) {
// The source of the event is the password field itself.
JPasswordField sourceField = (JPasswordField) e.getSource();
String currentPasswordValue = new String(sourceField.getPassword());
// getField() is a public method from our grandparent class (GUIField).
// setValue() updates the IzPack variable associated with this field.
// We only care about the first password field for the variable value.
getField().setValue(currentPasswordValue);
}
});
}
// IMPORTANT: We must call the super method to ensure the component
// is actually added to the panel layout.
super.addComponent(component, constraints);
}However, I do not know if this is a good decision or not.
Hello.
I have a password type input field and a button that checks connection in db after clicking. In the code, in debugging mode, the value installData.GetVariable("db.password") has the old value, not what I wrote in the input field, but field "text" have new value
<field type="text" variable="db.user"> <description txt="User:"/> <spec txt="User:" size="20" set="${db.user}"/> </field> <field type="password" variable="db.password"> <description txt="password:"/> <spec> <pwd txt="pasword:" size="20" set="${db.password}"/> </spec> </field> <field type="button"> <spec id="connection.test.button" successMsg="connection.test.success"> <run class="com.tir.izpack.actions.check.DatabaseConnectionTestAction"> <msg name="error" id="db.test.error"/> </run> </spec> </field>