| Summary: | Make GaServiceImpl extensible | ||
|---|---|---|---|
| Product: | [Modeling] Graphiti | Reporter: | Karsten Thoms <karsten.thoms> |
| Component: | Core | Assignee: | Project Inbox <graphiti-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | michael.wenz |
| Version: | 0.8.0 | Flags: | michael.wenz:
juno+
|
| Target Milestone: | 0.9.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | Juno M6 Theme_round_offs | ||
|
Description
Karsten Thoms
Influenceing the default text is a reasonable request and should be opened up. On the other hand we need also to make sure that we do not complicate stuff for the default usecase and the case of using styles. Needs some closer look to ensure that. I have move GaServiceImpl to an API package and opened it up for subclassing. Since I don't think that besides the 2 methods you mentioned there is anything that's needed to be changed by clients, I made all methods final except for the 2 you requested for change. Opening up lateron in case of need is of course still an option. You are now free to create an instance of a subclass of the Graphiti services class, but you are responsible by yourself for the creation of that class and how you make it available for usage throughout your tool. Checked-in and pushed to Eclipse: commit 4c4be0c960a6affa3cfd82061969cdc6601a51c2 Author: mwenz <michael.wenz@sap.com> 2012-03-15 17:14:28 Committer: mwenz <michael.wenz@sap.com> 2012-03-15 17:14:28 Parent: 48900bb913c380a8ff8d0a2704d6b79244262b6d (Corrected merge error) Branches: origin/master, master Corrected milestone: it's part of M6, not M5 Bookkeeping: Set target release Part of Graphiti 0.9.0 (Eclipse Juno) |