Bug 1079936

Description of problem:
In GDTs, if an input field requires the use of a comma, anything is allowed as input. Input is checked in other cases and invalid text is not allowed.

If the "is contained in the (comma separated) list" operator is used, all characters are allowed even for an Integer field (and other numerical types and boolean). 
The '(optional) value list' input field in new condition pop-ups misbehaves in the same way (and as a consequence, makes the default value and cell values invalid too).


Version-Release number of selected component (if applicable):
BPMS 6.0.1 CR1


Steps to Reproduce:
1. Create a POJO Fact with attr. fieldInt of type Integer.
2. Create a new GDT.
3. Create a new Simple Condition column - use Fact as pattern, fieldInt as field, 'equal to' operator.
4. In the same new column pop-up, type 'a,b,c' into the '(optional) value list' input field.
5. Undo the last step, choose 'is contained in the (comma separated) list' operator and use 'a,b,c' as the default value.
6. Remove the default value and click 'Apply changes'.
7. Add a row and edit the cell for the new column - use 'a,b,c' again.


Actual results:
In steps 4, 5, 7, the invalid input is allowed.


Expected results:
In steps 4, 5, 7, the invalid input is not allowed, The invalid characters cannot be typed into the input field.