Re: Unable to deploy jna 4.3.0 in Karaf 4.1.1 or 4.0.9

[Shyalika Benthotage]

Hi JB,

For our application we deploy it through a feature file. But we can
recreate the issue by getting a  fresh karaf 4.1.1 and directly coping the
bundle jna 4.3.0 to deploy folder there. The log I had attached was from
this scenario. Note the karaf startup logs at the end, it kind of
automatically started karaf too.

Please let me know if you need any more information.

Thanks,

Shyalika

On Fri, Jun 2, 2017 at 3:26 PM, Jean-Baptiste Onofré 
wrote:

> Hi,
>
> do you directly deploy the JNA bundle ?
>
> Can you describe a bit the steps you do ?
>
> Thanks !
> Regards
> JB
>
>
> On 06/02/2017 07:10 AM, Shyalika Benthotage wrote:
>
>> Hi,
>>
>> We have been using 3.0.3 for some time now and trying to migrate to karaf
>> 4.x. As a part of our application, when I try to deploy jna 4.3.0 or 4.4.0
>> it sometimes just stay in the 'starting' state or undeploys everything
>> including the shell, causing it to exit.
>>
>> I have attached the log here.
>>
>> Can anyone shed some light on what's happening here?
>>
>> Thanks,
>>
>> Shyalika
>>
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Unable to deploy jna 4.3.0 in Karaf 4.1.1 or 4.0.9

[Jean-Baptiste Onofré]

Hi,

do you directly deploy the JNA bundle ?

Can you describe a bit the steps you do ?

Thanks !
Regards
JB

On 06/02/2017 07:10 AM, Shyalika Benthotage wrote:

Hi,

We have been using 3.0.3 for some time now and trying to migrate to karaf 4.x. 
As a part of our application, when I try to deploy jna 4.3.0 or 4.4.0 it 
sometimes just stay in the 'starting' state or undeploys everything including 
the shell, causing it to exit.


I have attached the log here.

Can anyone shed some light on what's happening here?

Thanks,

Shyalika


--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Karaf-4346 JIRA

[Guillaume Nodet]

The difference between 4.1 and 4.2 is that with 4.2, both cfg and config
files can hold typed or untyped configurations and karaf will switch to a
typed configuration automatically if needed.  The syntax will be the same
however.  And there's currently no ETA defined.

2017-06-01 23:21 GMT+02:00 Leschke, Scott :

> *From your answer I gather this will be fully sussed out in 4.2, i.e. .cfg
> will be supported and the syntax may change somewhat. Is there an ETA on
> that release?*
>
>
>
> *From:* Guillaume Nodet [mailto:gno...@apache.org]
> *Sent:* Thursday, June 01, 2017 4:11 PM
> *To:* user 
> *Subject:* Re: Karaf-4346 JIRA
>
>
>
> First, it has to be xx.config not xx.cfg.  Before 4.2, both are handled
> differently.
>
> So in 4.1, you need to use the config syntax:
>
>   myInts = i[ "10", "5", "4" ]
>
>
>
> See the syntax description:
>
>   https://github.com/apache/felix/blob/trunk/configadmin/
> src/main/java/org/apache/felix/cm/file/ConfigurationHandler.java#L53-L61
>
>
>
> 2017-06-01 22:38 GMT+02:00 Leschke, Scott :
>
> The status of this is listed as fixed as of 4.1 but I can’t seem to get it
> to work.  I’m trying to set an int[] neither of the following worked. I get
> a NumberFormatException complaining about input string “{15,10,5}” or
> alternatively “[15,10,5]”;
>
>
>
> myInts = {10,5,0};
>
> myInts = [10,5,0];
>
>
>
> There’s discussion in the JIRA about the filter needing to be updated to
> support .cfg files but it’s looks like that change was made. So if this was
> in fact fixed, what’s the correct syntax?  I would think it would be the
> first. It works for defining the default in the config. def interface.
>
>
>
> Scott
>
>
>
>
>
>
>
>
>
> --
>
> 
> Guillaume Nodet
>
>
>



-- 

Guillaume Nodet

RE: Karaf-4346 JIRA

[Leschke, Scott]

From your answer I gather this will be fully sussed out in 4.2, i.e. .cfg will 
be supported and the syntax may change somewhat. Is there an ETA on that 
release?

From: Guillaume Nodet [mailto:gno...@apache.org]
Sent: Thursday, June 01, 2017 4:11 PM
To: user 
Subject: Re: Karaf-4346 JIRA

First, it has to be xx.config not xx.cfg.  Before 4.2, both are handled 
differently.
So in 4.1, you need to use the config syntax:
  myInts = i[ "10", "5", "4" ]

See the syntax description:
  
https://github.com/apache/felix/blob/trunk/configadmin/src/main/java/org/apache/felix/cm/file/ConfigurationHandler.java#L53-L61

2017-06-01 22:38 GMT+02:00 Leschke, Scott 
>:
The status of this is listed as fixed as of 4.1 but I can’t seem to get it to 
work.  I’m trying to set an int[] neither of the following worked. I get a 
NumberFormatException complaining about input string “{15,10,5}” or 
alternatively “[15,10,5]”;

myInts = {10,5,0};
myInts = [10,5,0];

There’s discussion in the JIRA about the filter needing to be updated to 
support .cfg files but it’s looks like that change was made. So if this was in 
fact fixed, what’s the correct syntax?  I would think it would be the first. It 
works for defining the default in the config. def interface.

Scott





--

Guillaume Nodet

Re: Karaf-4346 JIRA

[Guillaume Nodet]

First, it has to be xx.config not xx.cfg.  Before 4.2, both are handled
differently.
So in 4.1, you need to use the config syntax:
  myInts = i[ "10", "5", "4" ]

See the syntax description:

https://github.com/apache/felix/blob/trunk/configadmin/src/main/java/org/apache/felix/cm/file/ConfigurationHandler.java#L53-L61

2017-06-01 22:38 GMT+02:00 Leschke, Scott :

> The status of this is listed as fixed as of 4.1 but I can’t seem to get it
> to work.  I’m trying to set an int[] neither of the following worked. I get
> a NumberFormatException complaining about input string “{15,10,5}” or
> alternatively “[15,10,5]”;
>
>
>
> myInts = {10,5,0};
>
> myInts = [10,5,0];
>
>
>
> There’s discussion in the JIRA about the filter needing to be updated to
> support .cfg files but it’s looks like that change was made. So if this was
> in fact fixed, what’s the correct syntax?  I would think it would be the
> first. It works for defining the default in the config. def interface.
>
>
>
> Scott
>
>
>
>
>



-- 

Guillaume Nodet

Karaf-4346 JIRA

[Leschke, Scott]

The status of this is listed as fixed as of 4.1 but I can't seem to get it to 
work.  I'm trying to set an int[] neither of the following worked. I get a 
NumberFormatException complaining about input string "{15,10,5}" or 
alternatively "[15,10,5]";

myInts = {10,5,0};
myInts = [10,5,0];

There's discussion in the JIRA about the filter needing to be updated to 
support .cfg files but it's looks like that change was made. So if this was in 
fact fixed, what's the correct syntax?  I would think it would be the first. It 
works for defining the default in the config. def interface.

Scott

Re: Weird behaviour when uninstalling feature with fragment

[Steinar Bang]

> Steinar Bang :

> Steinar Bang :
> Castor :
>>> That's weird, i'm using the liquibase-slf4j as a fragment for quite
>>> sometime and i don't have this problem. but i'm using Karaf 4.0.8, and
>>> if i'm correct karaf 4.1.x changed some stuff related to logging,
>>> could be the cause of the problem.

>> Could be...? 

>> Should this be reported as a karaf bug?  It should be pretty easy to
>> create a test case (just a maven file or two, to rebundle
>> liquibase-slf4j and create a karaf feature).

> Here's the testcase:
>  https://github.com/steinarb/liquibase-karaf-feature

Here's the bug: https://issues.apache.org/jira/browse/KARAF-5174

Re: Weird behaviour when uninstalling feature with fragment

[Steinar Bang]

> Steinar Bang :

> Castor :
>> That's weird, i'm using the liquibase-slf4j as a fragment for quite
>> sometime and i don't have this problem. but i'm using Karaf 4.0.8, and
>> if i'm correct karaf 4.1.x changed some stuff related to logging,
>> could be the cause of the problem.

> Could be...? 

> Should this be reported as a karaf bug?  It should be pretty easy to
> create a test case (just a maven file or two, to rebundle
> liquibase-slf4j and create a karaf feature).

Here's the testcase:
 https://github.com/steinarb/liquibase-karaf-feature

Actually the above project doubles fine as a what the README says what
it is, if you don't try uninstalling it...;-)

The readme says: This project contains a karaf feature for easily using
Liquibase from OSGi-based applications running in apache karaf.

Karaf 4.0.7 and 4.0.9 don't have the uninstalling issue.