[
https://issues.apache.org/jira/browse/OFBIZ-9558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16118856#comment-16118856 ]
Nicolas Malin commented on OFBIZ-9558:
--------------------------------------
Hello Jacques,
Yes instead change the html, I just add @deprecated but it's easier to set both before commit this patch
{quote}I note that Scott also suggested:
I think it would be a good idea to replace the attribute definitions on the old service to use the "implements" element which would point to the new service. It would help keep them aligned with each other for future changes without duplication.
{quote}
For my view, it's only when you deprecate a service that your replace directly on the service definition. I haven't planned to do this on the modelService that could be introduce some complexity and perhaps a confusion between service definition and attributes loaded
> 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)
Locked
