Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 354849 - Lookup strategy for Permission classes in PermissionService
Summary: Lookup strategy for Permission classes in PermissionService
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Scout (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-16 11:35 EDT by Andi Bur CLA
Modified: 2021-08-19 11:08 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andi Bur CLA 2011-08-16 11:35:22 EDT 
Permission classes are expected to fulfill the following name pattern "*.security.*Permission*". Further, permissions must be placed in a package starting with the hosting plug-in's symbolic name. While the latter is a good convention also used by many Eclipse projects, the former is too restrictive. For example it does not allow putting all aspects of a particular entity into the same package (e.g. service interfaces, FormDatas, LookupCalls and Permissions). Both rules are implemented in org.eclipse.scout.rt.server.services.common.security.PermissionService.

Proposal: extract the class name check into a separate method so that implementers are free to extend the service and to override its default behavior.
Comment 1 Andi Bur CLA 2011-08-16 16:16:13 EDT 
Fixed as proposed: extracted check into method org.eclipse.scout.rt.server.services.common.security.PermissionService.isCandidate(String).
Comment 2 Matthias Zimmermann CLA 2011-10-11 02:31:35 EDT 
shipped with 3.7.1