own datasource definition.
The Karaf JDBC module provides what is not in Aries: management of
datasource, JDBC service, MBean and shell commands.
So it's not different, it's a complement.
Regards
JB
On 01/18/2014 09:40 AM, Benjamin Graf wrote:
Hi,
actually a lot of JDBC stuff has been done
, Benjamin Graf wrote:
Hi JB,
what I'm missing is a link to aries transaction jdbc which is in my
opinion the better template to provide out of the box. I think it's
worth thinking about a closer integration of this feature rather than
doing dbcp stuff for example. Well, of course that is a personally
a pooling (using the Aries
ConnectionManagerFactory). That's true. But again, we can add a
template Aries DataSource that wrap a XADataSource to create a
pooled datasource. But you need the XADataSource ;)
Regards
JB
On 01/18/2014 03:22 PM, Benjamin Graf wrote:
Hi JB,
well, I'm looking
Just to clarify even the 3.0.x branch is one r5 yet (since KARAF-2860). :-)
Regards
Benjamin
On 18.06.2014 20:06, Jean-Baptiste Onofré wrote:
It sounds good to me.
Regards
JB
On 06/18/2014 08:02 PM, Guillaume Nodet wrote:
I'd like to have a release or karaf 2.4 and a 4.0 beta during july.
I
Hi,
I think this discussion shows that karaf needs an actual release and
maintenance plan. Don't forget we still have 2.3.x and 2.x branch used and
developed. 2.4 will be an OSGi r5 release too. Well, that's really confusing.
;-)
Regards
Benjamin
On 19. Juni 2014 21:24:53 MESZ, Jean-Baptiste
Hi,
maybe create another branch (3.1.x) for r5? It's a bit odd that 2.4 will
be r5 ready but no 3.x version. :-)
Regards
Benjamin
*Gesendet:* Montag, 30. Juni 2014 um 13:47 Uhr
*Von:* Jean-Baptiste Onofré j...@nanthrax.net
*An:* Karaf Dev dev@karaf.apache.org
*Betreff:* [INFO] Apache Karaf
What about upgrading to Felix 4.4.1 first before releasing 2.4.0?
Benjamin
On 09.07.2014 17:24, Guillaume Nodet wrote:
Now that Aries releases are done, I'd like to discuss a 2.4.0 release asap.
I think it's in a good shape, but i'll do a bit more testing and I would
welcome any additional
Hi together,
I actually face the same problem with the just released 2.3.6 version on
Win7x64 JDK7u65. 2.3.5 does still work so there must be a change done
which causes this issue.
Regards
Benjamin
On 30.07.2014 20:30, nseb wrote:
Hi Jean Baptiste,
Have you found the problem?
Best
update:
https://issues.apache.org/jira/browse/KARAF-3056
I'm working on it. I will send an update on the mailing list as
soon
as I
have details (and eventually a new quick release to fix that).
Regards
JB
On 08/03/2014 08:45 PM, Benjamin Graf wrote:
Hi together,
I actually face the same
Hi,
but it has been done in the past from Karaf 2.3.3 to 2.3.4 for cm version 1.0.1
to 1.0.3. Since it is only a minor bug fix it's worth thinking about for 2.3.7
or 2.3.8.
Benjamin
On 03.09.2014 19:55, Jean-Baptiste Onofré wrote:
Unfortunately, no, Karaf 2.3.x is a maintenance release, and we
Hi,
Actually it is hard getting messaging systems working with Karaf if they
are using different version of the jms API (1.1 vs 2.0) like ActiveMQ
Artemis or IBM WebsphereMQ > 8. Therefor I would suggest to add a
jms-spec feature for either 1.1 version and 2.0 version. This allows to
add it for
Hi Grzegorz,
is there a reason why the plugin goal for generateConsistencyReport does
not filter the features that were chosen in custom distributions? Using
the report that way generates many "false friends" that are actually not
needed to resolve. Maybe it should also interact with more than
Hi JB,
that's the error of the ActiveMQ feature file I reported last year. The
corrected feature file is not releases yet. It may also be a problem in the
resolvement algorithm used by involved components mainly outside Karaf I think
pax-url if I remember right.
Regards
Benjamin
Am 8.
Hi JB,
do I understand right that pax-logging 1.11 or 2.0 won't be OSGi R6 for karaf
4.2.x anymore? Or does Grzegorz and you plan a next "small" release for 4.2
branch, too? Most improvements done in the near past are not in den 1.10.x
branch of pax-logging.
Regards
Benjamin
Gesendet:
org.apache.karaf.security.providers =
org.bouncycastle.jce.provider.BouncyCastleProvider. Something to be
solved before 4.3RC2?
Regards,
Benjamin
On 15.01.2020 17:00, Robert Varga wrote:
> On 15/01/2020 16:25, Benjamin Graf wrote:
>> Hi,
>>
>> I'm actually playing around with the
Hi,
I'm facing a issue while starting under Windows 10 and JDK 11:
It seems there is a strange issue added in karaf.bat between 4.2.7 and
4.2.8. Some error also on actual 4.3 SNAPSHOTS.
Regards,
Benjamin
On 12.01.2020 12:34, Jean-Baptiste Onofré wrote:
> Hi all,
>
> I submit Apache Karaf
for Karaf 4.2.9 and provide a workaround in the mean time.
>>
>> Regards
>> JB
>>
>> On 15/01/2020 08:26, Benjamin Graf wrote:
>>> Hi,
>>>
>>> I'm facing a issue while starting under Windows 10 and JDK 11:
>>>
>>> It seems there is a stra
JB
>
> On 15/01/2020 08:26, Benjamin Graf wrote:
>> Hi,
>>
>> I'm facing a issue while starting under Windows 10 and JDK 11:
>>
>> It seems there is a strange issue added in karaf.bat between 4.2.7 and
>> 4.2.8. Some error also on actual 4.3 SNAPSHOTS.
>
Hi,
I'm actually playing around with the latest 4.3.0-SNAPSHOT. I recognize
that the ssh bundle is using bouncycastle for reading pem files right
now (KARAF-6383). The "issue" I'm facing is that if I like to set
bouncycastle as the security provider via
"org.apache.karaf.security.providers =
-1
Update to ASM 8 has negativ impact to aries-proxy
org.objectweb.asm;resolution:=optional;version="[5,8)",org.objectweb.asm.commons;resolution:=optional;version="[5,8)"
On 19.05.2020 18:39, Jean-Baptiste Onofre wrote:
> Hi everyone,
>
> I submit Apache Karaf runtime 4.2.9 release to your
+1 (non-binding)
Regards
Benjamin
On 05.06.2020 14:48, Jean-Baptiste Onofre wrote:
> Hi everyone,
>
> I submit Apache Karaf runtime 4.2.9 release to your vote (take #2 where we
> fixed the ASM update).
>
> This is a maintenance release on the 4.2.x series bringing fixes, updates and
>
Hi JB,
it seems we have an issue in latest 4.3.0 with aries-proxy which does
not use ASM 9.0, yet. Feature and bundle are unfortunately not in sync.
Regards,
Benjamin
On 30.10.2020 08:16, Jean-Baptiste Onofre wrote:
Hi everyone,
This vote passed with the following result:
+1 (binding):
Hi,
just tried to run pax-transx-tm-narayana in plain Felix 7 on JDK11 and
still the same Exception trace.
Regards
Benjamin
On 20.05.2021 18:16, Benjamin Graf wrote:
Hi Grzegorz,
Of course do I remember issue #50. And I think it's not a bug in
pax-transx because everything is fine
Grzegorz Grzybek
czw., 20 maj 2021 o 18:00 Benjamin Graf napisał(a):
Hi Grzegorz,
the same error with pax-transx 0.5.1
- feature:repo-add pax-transx 0.5.1
- feature:repo-add pax-transx 0.5.1
Regards
Benjamin
On 20.05.2021 17:43, Grzegorz Grzybek wrote:
Hi
Did you try `mvn clean install
) ?
Regards
JB
Le 20 mai 2021 à 08:17, Benjamin Graf a écrit :
Hi,
it seems there is a bug with embedded resources. I think it is caused by Felix
and not Karaf itself.
How to reproduce:
- Clean start of plain Karaf 4.3.2
- feature:install pax-transx-tm-narayana
Result:
2021-05-20T08:16:02,787
2021 o 17:40 Benjamin Graf napisał(a):
Hi JB,
I use JDK 11 as runtime environment. There is no code to compile to
reproduce this bug just plain Karaf and pax-trans-tm-narayana from Maven
central.
Regards
Benjamin
On 20.05.2021 10:32, Jean-Baptiste Onofre wrote:
Hi Ben,
Are you using JDK 11
] - Race condition in unget service from service factory
Should be the cause IMHO. Any Felix expert on the list?
Regards,
Benjamin
On 20.05.2021 19:00, Benjamin Graf wrote:
Hi,
just tried to run pax-transx-tm-narayana in plain Felix 7 on JDK11 and
still the same Exception trace.
Regards
27 matches
Mail list logo
