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/12/14 08:43:07 UTC
[jira] [Comment Edited] (SLING-3282) JobManagerConfiguration refers
to undefined OSGi properties
[ https://issues.apache.org/jira/browse/SLING-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848275#comment-13848275 ]
Carsten Ziegeler edited comment on SLING-3282 at 12/14/13 7:41 AM:
-------------------------------------------------------------------
The reason for not making these properties visible is to avoid web console admins to switch back and force without knowing what they do - while this might be true for other settings as well - I thought it's a good idea. The property can of course be set through an osgi configuration
But I agree that its probably better to make this visible in the web console
was (Author: cziegeler):
The reason for not making these properties visible is to avoid web console admins to switch back and force without knowing what they do - while this might be true for other settings as well - I thought it's a good idea. The property can of course be set through an osgi configuration
> JobManagerConfiguration refers to undefined OSGi properties
> -----------------------------------------------------------
>
> Key: SLING-3282
> URL: https://issues.apache.org/jira/browse/SLING-3282
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Event 3.3.0
> Reporter: Konrad Windszus
> Assignee: Carsten Ziegeler
> Fix For: Event 3.3.2
>
>
> Currently the JobManagerImpl does not expose the properties in the web console. Also the properties being used by JobManagerConfiguration like job.consumermanager.disableDistribution are not even defined.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)