sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konrad Windszus (Jira)" <>
Subject [jira] [Closed] (SLING-9219) Invalid Comments in JSON Configuration
Date Mon, 06 Apr 2020 11:19:00 GMT


Konrad Windszus closed SLING-9219.

> Invalid Comments in JSON Configuration
> --------------------------------------
>                 Key: SLING-9219
>                 URL:
>             Project: Sling
>          Issue Type: Bug
>          Components: Installer
>    Affects Versions: File Installer 1.2.0, JCR Installer 3.2.0
>            Reporter: Dan Klco
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: JCR Installer 3.2.2, File Installer 1.2.2
> With the latest version of JCR Installer, I'm seeing an exception when saving OSGi Configurations
from the console:
> {{18.03.2020 19:57:44.565 *WARN* [JcrInstaller.2]
Cannot create InternalResource (resource will be ignored):InstallableResource, priority=200,
Unexpected character '#' (Codepoint: 35) on [lineNumber=2, columnNumber=77, streamOffset=76].
Reason is [[Expected structural character or digit or 't' or 'n' or 'f' or '-']]}}{{at org.apache.johnzon.core.JsonStreamParserImpl.uexc(}}{{at
org.apache.johnzon.core.JsonStreamParserImpl.uexc(}}{{at org.apache.johnzon.core.JsonStreamParserImpl.defaultHandling(}}{{at}}{{at}}{{at
org.apache.johnzon.core.JsonReaderImpl.parseObject(}}{{at org.apache.johnzon.core.JsonReaderImpl.readValue(}}{{at}}{{at org.apache.felix.configurator.impl.json.JSONUtil.parseJSON(
[]}}{{at org.apache.felix.configurator.impl.json.JSONUtil.readJSON(
> The problem appears to be that the files are in JSON format, but contain a prefix comment:
" # Configuration created by Apache Sling JCR Installer"
> This is due to the JCR Installer changing to write the configuration files in JSON format,
but still including the comment from when the configurations were persisted as text files:
> []
> The question [~kwin] it looks like there was a revert commit, so should the config files
revert to TXT format or remove the comment and have the configurations in JSON format?

This message was sent by Atlassian Jira

View raw message