[jira] [Commented] (ACE-224) Make resource processors manageable

["Marcel Offermans (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ACE-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922520#comment-13922520 ] 

Marcel Offermans commented on ACE-224:
--------------------------------------

We now have Gogo commands that allow you to manage resource processors:

{code}
w = (cw)
$w lrp
{code}

That checks out a workspace, and lists all resource processors that are available in the workspace. The work in ACE-373 already gave us the option to upgrade resource processors (which is simply a matter of uploading a new version of a resource processor) so if you see multiple versions being listed, the highest one is used. If you want to delete resource processors, they are just artifacts, so you can simply remove them. For example:

{code}
w = (cw)
each ($w lrp) { $w da $it }
{code}

Will iterate over all the available resource processors and delete them.

I'm leaving this issue open though as a Vaadin UI issue, because there we don't have this capability yet.

> Make resource processors manageable
> -----------------------------------
>
>                 Key: ACE-224
>                 URL: https://issues.apache.org/jira/browse/ACE-224
>             Project: ACE
>          Issue Type: Wish
>          Components: Architecture, UI
>    Affects Versions: 0.8.0-incubator
>            Reporter: Bram de Kruijff
>
> As discussed on the mailing list a while back. Resource processors are not handled as regular artifacts making it cumbersome dealing with them. Most notably you can create processor artifacts through webui/rest, but you will never see them. As a result as a client you can never know what processors are available and you can only delete available once if you know the exact uri.
> [0] http://www.mail-archive.com/ace-dev@incubator.apache.org/msg01336.html
> [1] http://www.mail-archive.com/ace-dev@incubator.apache.org/msg01346.html



--
This message was sent by Atlassian JIRA
(v6.2#6252)