[
https://issues.apache.org/jira/browse/SLING-6342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15724976#comment-15724976
]
Robert Munteanu commented on SLING-6342:
----------------------------------------
I am not sure this happens very often, but maybe we can detect from the
response that the repository is starting up and simply wait.
> Sling IDE: Better deal with reconfigurations of the sling repository service
> ----------------------------------------------------------------------------
>
> Key: SLING-6342
> URL: https://issues.apache.org/jira/browse/SLING-6342
> Project: Sling
> Issue Type: Bug
> Components: IDE
> Affects Versions: Sling Eclipse IDE 1.1.0
> Reporter: Konrad Windszus
>
> In some cases, e.g. deployment of a configuration for PID
> {{org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl}} the
> sling repository service is restarted in the background which leads to
> temporary failures during publishing like this
> {code}
> Failed publishing path=/content, result=JcrResult[ success:false, exception:
> org.apache.sling.ide.transport.RepositoryException -
> javax.jcr.RepositoryException: AuthenticationSupport service missing. Cannot
> authenticate request.]
> {code}
> The publish client code should check in advance if the relevant
> bundles/services are running.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
