This documents covers changes that need to be made by Sapphire adopters as part of migrating to Sapphire 8 from a prior release. Only changes from the previous major release are covered.
Table of Contents
Before | After |
---|---|
|
|
|
|
This class has been removed. See DefaultValueService migration.
Before | After |
---|---|
|
|
|
|
This class has been removed. See DerivedValueService migration.
Before | After |
---|---|
|
|
|
|
This class has been removed. See EnablementService migration.
Before | After |
---|---|
|
|
|
|
Before | After |
---|---|
|
|
|
|
This class has been removed. See InitialValueService migration.
Before | After |
---|---|
|
|
|
|
This annotation is not longer available and no analog has been provided.
Before | After |
---|---|
|
|
Before | After |
---|---|
|
|
|
The invalid value message must now be in Sapphire EL syntax, rather than in MessageFormat syntax. |
|
|
Before | After |
---|---|
|
|
|
|
|
|
|
|
|
This simpler migration can be used in many cases where complex heuristics are not required. Note that the invalid value message must be in Sapphire EL syntax, rather than in MessageFormat syntax. |
|
The invalid value message must now be in Sapphire EL syntax, rather than in MessageFormat syntax. Each of these properties has a default value, so typically only a subset needs to be set explicitly. Collation is now specified separately from the possible values, either through @Collation annotation or through CollationService. |
|
Collation is now specified separately from the possible values, either through @Collation annotation or through CollationService. |
Before | After |
---|---|
|
|
Before | After |
---|---|
|
|
This class is not longer available and no analog has been provided.