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
The Property.toString() alternatives combined with the legacyPropertyToString
servlet init parameter was introduced in Vaadin 7.0 to ease migration of
applications written in earlier versions. This is no longer relevant.
Change-Id: I6b20e96408738a2a0d60f230c329ce0b329465a8
* Made it possible to toggle the toString() behavior using the "legacyPropertyToString" init parameter. The default value is "warning" which enables the legacy Property.toString implementation and logs a warning message when it is used. Other supported values are "true" which enables the legacy mode and "false" which disables it.
Change-Id: Ife19352b86590464c8e441b7f82f4fec3b1f3235
Throw exception from Property.toString() implementations.
The default implementations of Property.toString() now throw an
UnsupportedOperationException to help find and eliminate code relying on
Property.toString().
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.
Ahmed Ashour
Ilia Motornyi
Teemu Suo-Anttila
Denis Anisimov
Artur Signell
Mikael Grankvist
Leif Åstrand
Automerge
Artur Signell
Henri Sara
Jonatan Kronqvist
John Alhroos