Le 03/09/2012 11:53, Malin Nicolas a écrit :
When changing the name of a field, or deprecating and replacing a
field that does not require deprecation of the entire entity, then
follow the same pattern leaving the old field there: a old prefix
added to the field name, change the original
Also I wanted to remove these sentences in this section
https://cwiki.apache.org/confluence/display/OFBTECH/General+Entity+Overview#GeneralEntityOverview-DeprecatedEntities
change the original first letter to upper case, and specify the column-name for the field so it is the same as the original
Le 03/09/2012 08:27, Jacques Le Roux a écrit :
Also I wanted to remove these sentences in this section
https://cwiki.apache.org/confluence/display/OFBTECH/General+Entity+Overview#GeneralEntityOverview-DeprecatedEntities
change the original first letter to upper case, and specify the
$ find applications/ -name entitymodel*.xml | xargs grep
'name=customMethodId' | wc -l
12
$ find applications/ -name entitymodel*.xml | xargs grep
'name=serviceName' | wc -l
3
Three entities not use customMethod to call a service (on functionnal
framework) : Content, ProductStoreShipmentMeth
This looks better, but I don't like the deprecation note in serviceName
field description. There is no need to deprecate the field - some
developers might PREFER to use a service.
-Adrian
On 9/2/2012 10:46 AM, jler...@apache.org wrote:
Author: jleroux
Date: Sun Sep 2 09:46:20 2012
New
