You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2014/07/10 15:30:06 UTC

[jira] [Resolved] (KARAF-1560) config:update throws ClassCastException when used on a Configuration with boolean fields created in the web console

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

Guillaume Nodet resolved KARAF-1560.
------------------------------------

    Resolution: Fixed

> config:update throws ClassCastException when used on a Configuration with boolean fields created in the web console
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: KARAF-1560
>                 URL: https://issues.apache.org/jira/browse/KARAF-1560
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-config
>    Affects Versions: 2.2.5
>            Reporter: Hugh Rodgers
>            Assignee: Guillaume Nodet
>            Priority: Minor
>             Fix For: 2.4.0, 2.3.6
>
>         Attachments: demo_validation.png, karaf_config_propset.png, karaf_log.png, metatype.xml
>
>
> I am using Karaf v2.2.5 on Windows 7. I start Karaf (using the karaf.bat
> script) and create a configuration that has one or more fields that are
> checkboxes (i.e., Boolean).
> I then go to the Karaf command line console and issue the following
> commands:
> config:edit <PID of configuration just created in Admin Console>
> config:propset <booleanFieldName> true
> config:update
> When I submit the config"update command I get this exception:
> 09:52:19,658 | INFO  | l Console Thread | Console                          |
> araf.shell.console.jline.Console  242 | 14 - org.apache.karaf.shell.console
> - 2.2.5 | Exception caught while executing command
> java.lang.ClassCastException: java.lang.Boolean cannot be cast to
> java.lang.String
>        at
> org.apache.karaf.shell.config.ConfigCommandSupport.persistConfiguration(ConfigCommandSupport.java:161)[41:org.apache.karaf.shell.config:2.2.5]
>        at
> org.apache.karaf.shell.config.ConfigCommandSupport.update(ConfigCommandSupport.java:129)[41:org.apache.karaf.shell.config:2.2.5]
>        at
> org.apache.karaf.shell.config.UpdateCommand.doExecute(UpdateCommand.java:38)[41:org.apache.karaf.shell.config:2.2.5]
>        at
> org.apache.karaf.shell.config.ConfigCommandSupport.doExecute(ConfigCommandSupport.java:63)[41:org.apache.karaf.shell.config:2.2.5]
>        at
> org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:38)[14:org.apache.karaf.shell.console:2.2.5]
>        at
> org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)[14:org.apache.karaf.shell.console:2.2.5]
>        at
> org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[14:org.apache.karaf.shell.console:2.2.5]
>        at
> org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:474)[14:org.apache.karaf.shell.console:2.2.5]
>        at
> org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)[14:org.apache.karaf.shell.console:2.2.5]
>        at
> org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[14:org.apache.karaf.shell.console:2.2.5]
>        at
> org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[14:org.apache.karaf.shell.console:2.2.5]
>        at
> org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[14:org.apache.karaf.shell.console:2.2.5]
>        at
> org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)[14:org.apache.karaf.shell.console:2.2.5]
>        at
> org.apache.karaf.shell.console.jline.Console.run(Console.java:221)[14:org.apache.karaf.shell.console:2.2.5]
>        at java.lang.Thread.run(Thread.java:662)[:1.6.0_29]
> And the configuration is not saved.
> Configuration completely created/updated in the Admin Console work fine.
> Likewise, configurations completely created in the command line console work
> fine. The issue arises only with boolean fields and what mechanism is used
> to initially create the configuration.



--
This message was sent by Atlassian JIRA
(v6.2#6252)