[
https://issues.apache.org/jira/browse/ACE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903995#comment-13903995
]
Herko ter Horst commented on ACE-456:
-------------------------------------
Jan Willem, if there's a better place to put it, that's perfectly fine with me,
I can move it and resubmit a patch if you want.
However, I don't think it should be a sub-bundle of o.a.a.client.rest
specifically. I don't think it has anything to do with the REST-part of the ACE
client. The way I look at it, the Workspace is generic client functionality
that can be used (as a service) by different "manifestations" of the client
(i.e. REST, script-based, even the Vaadin client could potentially re-use it to
maintain its "dirty" state on the server side).
Perhaps it could be combined with for example the o.a.a.client.automation
services into o.a.a.client.services or something similar? What do you think?
> Refactor client workspace to make it more reusable
> --------------------------------------------------
>
> Key: ACE-456
> URL: https://issues.apache.org/jira/browse/ACE-456
> Project: ACE
> Issue Type: Improvement
> Components: Client Repository
> Affects Versions: 1.0.0
> Reporter: Herko ter Horst
> Assignee: Marcel Offermans
> Priority: Minor
> Labels: patch
> Attachments: ACE-456.patch
>
>
> To improve separation of concerns and promote re-use (in our use-case: for
> scripted access to the client), I've created a separate bundle for the
> "Workspace" functionality that was previously included in the REST client.
> The functionality to create and remove Workspaces was moved to a separate
> WorkspaceManager.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
