[OFBIZ-8013] Move the permission check from implementation level to service defination level

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Implemented
• Affects Version/s: Trunk
• Fix Version/s: 16.11.01
• Component/s: ALL COMPONENTS
• Assignee: Deepak Dixit
• Reporter: Nameet Jain
• Created: 27/Aug/16 08:28
• Updated: 05/Nov/16 11:39
• Resolved: 05/Nov/16 11:39

Description

Checking permission at service definition level is a better approach than checking it at the implementation level.
1. Permission check will be done during service validation.
2. If one want to override the permission for any service then he need not required to override the actual implementation. He will override the permission service.

Issue Links

• relates to: OFBIZ-8738 Add accounting permission service validating while setting payment status or void payment
• relates to: OFBIZ-8824 Add facility generic permission service
• relates to: OFBIZ-8826 Add marketing manager generic permission service
• relates to: OFBIZ-8851 Add the return generic permission service
• relates to: OFBIZ-8875 Add entity sync permission service used when Entity Sync CRUD services

Sub-Tasks

• Improve content service by moving permission at definition level: Closed
• Improve rate amount service my moving the accounting permission service at definition level: Closed
• Check the accounting permission for 'setPaymentStatus' and 'voidPayment' on definition level: Closed
• Improve the work effort services to have generic permission check on defination: Closed
• Improve the facility and related entities CRUD service to check permission at definition: Closed
• Improve the ContactList and TrackingCode CRUD service to check marketing manager permission at definition: Closed
• Improve return and related entities CRUD service to check order permission at definition level: Closed
• Improve the entity sync CRUD services by checking 'entitySyncPermissionCheck' permission at definition: Closed