[jira] [Created] (KARAF-7778) CommandExtension doesn't handle correctly bundles with a package that includes the word class
Joao Assuncao created KARAF-7778:
Summary: CommandExtension doesn't handle correctly bundles with a
package that includes the word class
Key: KARAF-7778
URL: https://issues.apache.org/jira/browse/KARAF-7778
Project: Karaf
Issue Type: Bug
Components: karaf
Affects Versions: 4.3.6
Reporter: Joao Assuncao
If a bundle marked with the header Karaf-Commands includes a package starting
with the word ".class" it will fail to load the class and log something like
this:
{noformat}
Inspection of class
com.atobe.ort.events.combiner.providerification.RmtaClassifier failed.
java.lang.ClassNotFoundException:
com.atobe.ort.events.combiner.providerification.RmtaClassifier not found by
eventscombiner-provider [235]
{noformat}
In this case the package in question is
"com.atobe.ort.events.combiner.provider.classification"
This is caused by the regex in CommandExtension:
{noformat}
...
className = className.replace('/', '.').replace(".class", "");
...{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (KARAF-7289) Provide config property name completion using MetaType information
Joao Assuncao created KARAF-7289: Summary: Provide config property name completion using MetaType information Key: KARAF-7289 URL: https://issues.apache.org/jira/browse/KARAF-7289 Project: Karaf Issue Type: Improvement Components: karaf Reporter: Joao Assuncao When using config:edit to create a new configuration, or edit an existing one, it can be useful to have property name completion include properties defined in the metadata (if available). Currently it only includes the names of properties already present in the configuration. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (KARAF-7155) Deleting a factory configuration doesn't delete the associated json file
[ https://issues.apache.org/jira/browse/KARAF-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joao Assuncao resolved KARAF-7155. -- Fix Version/s: 4.3.3 Resolution: Cannot Reproduce > Deleting a factory configuration doesn't delete the associated json file > > > Key: KARAF-7155 > URL: https://issues.apache.org/jira/browse/KARAF-7155 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.3.2 >Reporter: Joao Assuncao >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.3.3 > > > Deleting a factory configuration created with json as the file type will > leave the respective json file in the file system. This occurs either via > config:delete or webconsole. If Karaf is restarted, the configuration will > be recreated. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (KARAF-7155) Deleting a factory configuration doesn't delete the associated json file
[ https://issues.apache.org/jira/browse/KARAF-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17451768#comment-17451768 ] Joao Assuncao commented on KARAF-7155: -- Unable to reproduce in 4.3.3. > Deleting a factory configuration doesn't delete the associated json file > > > Key: KARAF-7155 > URL: https://issues.apache.org/jira/browse/KARAF-7155 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.3.2 >Reporter: Joao Assuncao >Assignee: Jean-Baptiste Onofré >Priority: Major > > Deleting a factory configuration created with json as the file type will > leave the respective json file in the file system. This occurs either via > config:delete or webconsole. If Karaf is restarted, the configuration will > be recreated. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (KARAF-7155) Deleting a factory configuration doesn't delete the associated json file
[ https://issues.apache.org/jira/browse/KARAF-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17407115#comment-17407115 ] Joao Assuncao commented on KARAF-7155: -- Not in front of a computer but from what I can remember I was creating the configs via web console. I think it also occurred when creating config via config: edit. Those wouldn't have the felix file install property I think. > Deleting a factory configuration doesn't delete the associated json file > > > Key: KARAF-7155 > URL: https://issues.apache.org/jira/browse/KARAF-7155 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.3.2 >Reporter: Joao Assuncao >Assignee: Jean-Baptiste Onofré >Priority: Major > > Deleting a factory configuration created with json as the file type will > leave the respective json file in the file system. This occurs either via > config:delete or webconsole. If Karaf is restarted, the configuration will > be recreated. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KARAF-7165) config:meta doesn't work for factory PIDs
Joao Assuncao created KARAF-7165: Summary: config:meta doesn't work for factory PIDs Key: KARAF-7165 URL: https://issues.apache.org/jira/browse/KARAF-7165 Project: Karaf Issue Type: Bug Components: karaf Affects Versions: 4.3.2 Reporter: Joao Assuncao Using config:meta to print or create a default configuration for a factory will fail with a "No meta type definition" error message . Apparently factory Pids are skipped in the getMetatype method. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KARAF-7157) Editing a factory config lacking a FILEINSTALL_FILE_NAME prop. produces a file with incorrect filename
Joao Assuncao created KARAF-7157: Summary: Editing a factory config lacking a FILEINSTALL_FILE_NAME prop. produces a file with incorrect filename Key: KARAF-7157 URL: https://issues.apache.org/jira/browse/KARAF-7157 Project: Karaf Issue Type: Bug Affects Versions: 4.3.2 Reporter: Joao Assuncao Using config:edit to edit a factory configuration that lacks a FILEINSTALL_FILE_NAME property will result in the creation of a file with a filename that does't follow the convention:-.cfg. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KARAF-7155) Deleting a factory configuration doesn't delete the associated json file
Joao Assuncao created KARAF-7155: Summary: Deleting a factory configuration doesn't delete the associated json file Key: KARAF-7155 URL: https://issues.apache.org/jira/browse/KARAF-7155 Project: Karaf Issue Type: Bug Components: karaf Affects Versions: 4.3.2 Reporter: Joao Assuncao Deleting a factory configuration created with json as the file type will leave the respective json file in the file system. This occurs either via config:delete or webconsole. If Karaf is restarted, the configuration will be recreated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KARAF-6924) Configurations created via web console are always persisted as JSON
Joao Assuncao created KARAF-6924: Summary: Configurations created via web console are always persisted as JSON Key: KARAF-6924 URL: https://issues.apache.org/jira/browse/KARAF-6924 Project: Karaf Issue Type: Bug Components: karaf Affects Versions: 4.3.0 Reporter: Joao Assuncao Creating a new configuration using the web console will be persisted as a json file instead of a cfg file. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KARAF-6789) Reference filtering doesn't work for shell commands
Joao Assuncao created KARAF-6789: Summary: Reference filtering doesn't work for shell commands Key: KARAF-6789 URL: https://issues.apache.org/jira/browse/KARAF-6789 Project: Karaf Issue Type: Bug Components: karaf Affects Versions: 4.2.9 Reporter: Joao Assuncao The filter is ignored in SingleServiceTracker when requesting a service reference from the BundleContext. If at least one service matches the filter, SingleServiceTracker.findMatchingReference will return the first service matching the service class. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KARAF-5469) Installation of a non blueprint feature triggers the installation of the blueprint compatibility bundle
[
https://issues.apache.org/jira/browse/KARAF-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355161#comment-16355161
]
Joao Assuncao commented on KARAF-5469:
--
Probably because I'm not using the default cxf-http-jetty feature.
When I installed the regular cxf-http-jetty (3.1.10) feature I would end with
two different jetty versions installed. As an workaround I created a
cxf-http-jetty_fix feature with the cxf-rt-transports-http-jetty bundle.
Probably I should have mention that I'm using a custom karaf distro.
What I find odd, is the fact this blueprint installation only happens when I
install this particular feature.
> Installation of a non blueprint feature triggers the installation of the
> blueprint compatibility bundle
> ---
>
> Key: KARAF-5469
> URL: https://issues.apache.org/jira/browse/KARAF-5469
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
>Affects Versions: 4.1.3
>Reporter: Joao Assuncao
>Priority: Major
> Attachments: wiring.txt
>
>
> In Karaf 4.1.3 when installing some custom made features karaf triggers the
> installation of the org.apache.aries.blueprint.core.compatibility bundle
> causing a refresh of all bundles and a Karaf shutdown.
> None of the bundles in the feature uses blueprint and the more exotic thing
> is that one of the bundles uses a Contional-Package instruction.
> The feature I'm trying to install:
> {code}
> karaf@root()> feature:info paybox-io-modbus
> Feature paybox-io-modbus 0.1.0.SNAPSHOT
> Description:
> Modbus I/O implementation
> Feature has no configuration
> Feature has no configuration files
> Feature has no dependencies.
> Feature contains followed bundles:
> mvn:pt.brisa.common/common-service-core/1.3.0
> mvn:pt.brisa.paybox/io-api/0.1.0-SNAPSHOT
> mvn:pt.brisa.paybox/io-modbus/0.1.0-SNAPSHOT
> mvn:pt.brisa.paybox/io-commands/0.1.0-SNAPSHOT
> Feature has no conditionals.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KARAF-5469) Installation of a non blueprint feature triggers the installation of the blueprint compatibility bundle
Joao Assuncao created KARAF-5469:
Summary: Installation of a non blueprint feature triggers the
installation of the blueprint compatibility bundle
Key: KARAF-5469
URL: https://issues.apache.org/jira/browse/KARAF-5469
Project: Karaf
Issue Type: Bug
Components: karaf-core
Affects Versions: 4.1.3
Reporter: Joao Assuncao
In Karaf 4.1.3 when installing some custom made features karaf triggers the
installation of the org.apache.aries.blueprint.core.compatibility bundle
causing a refresh of all bundles and a Karaf shutdown.
None of the bundles in the feature uses blueprint and the more exotic thing is
that one of the bundles uses a Contional-Package instruction.
The feature I'm trying to install:
{{
karaf@root()> feature:info paybox-io-modbus
Feature paybox-io-modbus 0.1.0.SNAPSHOT
Description:
Modbus I/O implementation
Feature has no configuration
Feature has no configuration files
Feature has no dependencies.
Feature contains followed bundles:
mvn:pt.brisa.common/common-service-core/1.3.0
mvn:pt.brisa.paybox/io-api/0.1.0-SNAPSHOT
mvn:pt.brisa.paybox/io-modbus/0.1.0-SNAPSHOT
mvn:pt.brisa.paybox/io-commands/0.1.0-SNAPSHOT
Feature has no conditionals.}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
