Move and rename server classes which go into the compatibility package
* Use com.vaadin.v7
* Use the same class name as in Vaadin 7
* Use a "vaadin7-" declarative prefix for Vaadin 7 components
Change-Id: I19a27f3835b18980b91a4f8f9464b2adde1a5fd5
Form was deprecated in Vaadin 7 when FieldGroup was introduced.
In Vaadin 8, FieldGroup is deprecated in favor of Binder. Having three
different "forms" would be very confusing.
Change-Id: I17775c922940edc5df7dd5bdc80bfe9652588270
Eliminate the redundant method Validator.isValid(). Validator.validate()
does the same but throws an exception including the validation error
message.
Migration:
- replace implementations of isValid() with internalIsValid() in custom
subclasses of AbstractValidator
- use Validator.validate() and catch exceptions rather than call
Validator.isValid()
- note that AbstractField still provides an isValid() method that is
internally based on validate()
Eliminate many generics related warnings in tests.
Most of the warnings eliminated are related to generics for
Property, Field or field factories. Not all such warnings are eliminated
in this changeset.
The toString() method should not be used on a property to get its value.
Added getStringValue() to AbstractField, Label etc. Using them
where applicable. Added comments to some problematic locations where
Property.toString() is known to be used.
AbstractField.toString() and Label.toString() still return the same
values as before, but it will throw an exception in future revisions.
Migration needed: Replace explicit and implicit uses of
Property.toString() with use property.getValue() and its
string representation.
Alternatively, use AbstractProperty.getStringValue() and
AbstractField.getStringValue() instead of Property.toString() during
migration.
TestSerialization used ByteOutputStream instead of ByteArrayOutputStream. This is most probably a mistake as ByteOutputStream is an internal sun implementation class. Corrected.