[ 
https://issues.apache.org/jira/browse/OFBIZ-9558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16119057#comment-16119057
 ] 

Jacques Le Roux commented on OFBIZ-9558:
----------------------------------------

Nicolas,

bq. For my view, it's only when you deprecate a service that your replace 
directly on the service definition
Yes that's what I mean. We should write a deprecate policy in the wiki, not 
[only for 
Entities|https://cwiki.apache.org/confluence/display/OFBIZ/General+Entity+Overview#GeneralEntityOverview-DeprecatedEntities].
 We would also write when the depecated code is removed...

> Manage deprecated service on the ModelService
> ---------------------------------------------
>
>                 Key: OFBIZ-9558
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-9558
>             Project: OFBiz
>          Issue Type: New Feature
>          Components: framework
>    Affects Versions: Trunk
>            Reporter: Nicolas Malin
>            Priority: Minor
>         Attachments: OFBIZ-9558.patch, OFBIZ-9558.patch
>
>
> Following the thread 
> https://lists.apache.org/thread.html/ce4f9899d811208b8ecbc0a6bdc99a47057dfcd354f932a879aa947b@%3Cdev.ofbiz.apache.org%3E
>  on how manage the deprecated service we started on the idea :
> * create a new element deprecated on services.xsd with attribute
> * * use-instead : what service replace the current
> * * since
> * * and content element as reason of the deprecation
> * alert in log warning each call on this service
> * set "@deprecated" on the service List in webtools and inform on detail 
> service page.
> The patch contains this feature



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to