Bug 1016062

Description of problem:
There is input length&content constraint for most of socket binging input fields (user can enter only digits, user cannot enter more the 5 digits). But this constraints are missing for some fields so user can enter "ss" as port number.

Input validation itself is ok (user cannot continue to next screen with "ss" as port number).

Version-Release number of selected component (if applicable):
EAP 6.2.0.ER4

How reproducible:
always

Steps to Reproduce:
 1. On Socket Bindings screen select to "Configure custom port bindings" and "Configure ports for standalone"
 2. Continue to Socket Bindings (ha-standalone) screen
 3. Navigate to "jgroups-mping Multicast-port" and intut "ssssssssss"

Actual results:
 "ssssssssss" string is put into "jgroups-mping Multicast-port" input field

Expected results:
 "" string is put into "jgroups-mping Multicast-port" input field as "s" is not a valid character for port number.

Found violations:
--- Socket Bindings (ha-standalone)
 - jgroups-mping Multicast-Port
 - jgroups-udp Multicast-Port
 - modcluster Multicast-Port
--- Socket Bindings (full-ha-standalone)
 - jgroups-mping Multicast-Port
 - jgroups-udp Multicast-Port
 - modcluster Multicast-Port
 - messaging-group Multicast-Port