You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2013/10/24 09:31:13 UTC

[jira] [Closed] (SLING-3170) Complex Job Result Structures

     [ https://issues.apache.org/jira/browse/SLING-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed SLING-3170.
-----------------------------------


> Complex Job Result Structures
> -----------------------------
>
>                 Key: SLING-3170
>                 URL: https://issues.apache.org/jira/browse/SLING-3170
>             Project: Sling
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Event 3.3.0
>
>
> This is a follow up from SLING-3028 based on comments by Stefan Seifert:
> we need a possible to store complex result structures in our jobs, e.g. a subtree of nodes/resources with static and other process infos, definitely too much for a single string. ok, we could build an JSON structure and pass it over as log messages, but this would e really ugly hack. it would be possible to store this structure in the job logic and have an own management gui which can detect this additional result info by job id and display it. but when thinking about a cluster of nodes where the job runs only on one node it would be good to collect this job results centrally. i've not a perfect idea for an API extension for this, perhaps we should create a separate ticket for it.



--
This message was sent by Atlassian JIRA
(v6.1#6144)