[
https://issues.apache.org/jira/browse/SLING-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795515#comment-13795515
]
Carsten Ziegeler commented on SLING-3167:
-----------------------------------------
Yes, you're right of course with the listener. The idea of the current log api
is to get brief information about the job, so it shouldn't be too extensively
used :) For example if you have an import of 1 million products, you probably
shouldn't log every single product import. I think it would rather make sense.
if something goes wrong to log this
Therefore I tend to leaving this up to SLING-3170, it's correct that this will
rule out a common nice UI that fits everyones needs, but I have the feeling
that this stuff really varies from user to user heavlly and a specialized UI is
needed anyway.
[[email protected]] If you agree that we leave this to SLING-3170, I'll
update the javadocs and then close this one :)
> Job Logging
> -----------
>
> Key: SLING-3167
> URL: https://issues.apache.org/jira/browse/SLING-3167
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Event 3.3.0
>
>
> This is a follow up from SLING-3028 based on comments by Stefan Seifert:
> Job.getProcessLog() - is it a good solution to use a String[] type for this?
> as i see this is currently through all the implementation that every writing
> of a log message reads gets the existing string array, copies it to a new
> array and adds the new log message. the reason is that its easy then to store
> it in a JCR compatible value map. i'm just thinking if its a good idea if a
> job produces thousands of log messages. perhaps its acceptable overall. if
> you think about and admin GUI which refreshes every second to show the log
> messages of a job currently running... perhaps it would be nice to have a
> listener interface for such log messages as well.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
