Hi Vince,
you still need do define and register a StringEncryptor service.
Try something like that: (doc: http://www.jasypt.org)
http://www.osgi.org/xmlns/blueprint/v1.0.0";>
Regards
Benjamin
Am 03.10
Hi Vince,
you are mixing up stuff. You're encryptor in this case works as an
extension to the defined property placeholder. Your're trying to decrypt
the properties to initialize the encryptor. Split up the encryptor stuff
and the datasource stuff. Register a osgi service for StringEncryptor as
sh
Hello,
I'm actually playing with integrating ActiveMQ Artemis (1.5-SNAPSHOT)
with Camel (2.17.3) on Karaf (4.0.8-SNAPSHOT). To get some conflicts
workarounded I'm deleting jms 1.1 API bundle from camel-jms feature
(2.17.3) and also from latest spring-jms feature (4.2.5.RELEASE_1). But
the jms bund
les,
> so that they will not be included in any resolution, or use an
> override to automatically use jms 2.0 instead.
>
> 2016-10-06 16:09 GMT+02:00 Benjamin Graf <mailto:benjamin.g...@gmx.net>>:
>
> Hello,
>
> I'm actually playing with integrating ActiveM
Guillaume Nodet:
> I suppose one easy way is to simply blacklist the jms api 1.1 bundles,
> so that they will not be included in any resolution, or use an
> override to automatically use jms 2.0 instead.
>
> 2016-10-06 16:09 GMT+02:00 Benjamin Graf <mailto:benjamin.g...@gmx.ne
Hi Paul,
did you install
mvn:org.apache.aries.spifly/org.apache.aries.spifly.dynamic.bundle/1.2.1?
It's not listed in your feature file.
I think that's all you need.
Regards
Benjamin
Am 26.05.2019 um 06:33 schrieb Jean-Baptiste Onofré:
> Hi,
>
> osgi.serviceloader.registrar package is part of
Hi all together,
just to keep the list informed. Issue is documented and fixed with
https://issues.apache.org/jira/browse/CAMEL-13864.
Regards
Benjamin
Am 13.08.2019 um 16:37 schrieb Benjamin Graf:
> Hi Claus,
>
> Sure ;-)
>
> Will have a look on it. I might create a patch on a
Please ignore, sent to wrong list :-)
Am 15.08.2019 um 12:59 schrieb Benjamin Graf:
> Hi all together,
>
> just to keep the list informed. Issue is documented and fixed with
> https://issues.apache.org/jira/browse/CAMEL-13864.
>
> Regards
>
> Benjamin
>
> Am 13.08.
If I remember right there is a new option to be set since pax-logging 1.11.
Might not be set yet in Karaf 4.2.7
Regards
Benjamin
Am 3. Oktober 2019 13:59:01 MESZ schrieb "J. Brebec" :
>Thanks.
>
>It's probably related to the upgrade to pax-logging too, but when I
>launch Karaf 4.2.7 (on windows
of pax logging.
>
> Thanks
>
> On 2019/10/03 18:01:24, Benjamin Graf wrote:
>> If I remember right there is a new option to be set since pax-logging 1.11.
>>
>> Might not be set yet in Karaf 4.2.7
>>
>> Regards
>> Benjamin
>>
>> Am 3.
might be to change run level of wrap to something
higher than 8. For plain Karaf 4.2.7 it does work with e.g. 10 but you
should't try to activate bundles with wrap with lower run level!
Regards
Benjamin
On 04.10.2019 16:07, Benjamin Graf wrote:
> I th
Hi Gian,
try using aries:services instead of osgi:service for jndi lookup. This
will avoid creating a proxy around.
(https://aries.apache.org/modules/jndiproject.html)
Regards,
Benjamin
On 17.07.2020 10:28, Giamma wrote:
> Hi,
>
> I have an application that tries to access a JavaMail session ov
Hi,
what can I do if wrapping a jar generates import for osgi package
"java.io" which can not be resolved. I recognized this issue with actual
oracle ojdbc11 driver. The same works with sibling ojdbc8.
Thanks for help :)
Regards
Benjamin
OpenPGP_signature
Description: OpenPGP digital si
: Issue with wrapping jar bundle
Hi Benjamin,
You can exclude the java.io import. Anyway, I guess you are not using Karaf 4.3.1: I fixed the issue on this release with https://issues.apache.org/jira/browse/KARAF-7012
Regards
JB
Le 6 mai 2021 à 08:10, Benjamin Graf <benjamin.g...@gmx.net&
try Import-Package=!java.io,* ?
Regards
JB
Le 6 mai 2021 à 10:45, Benjamin Graf <benjamin.g...@gmx.net> a écrit :
Hi JB,
yes still using 4.2.11. What's the correct syntax to exclude the generation of java.io import in wrap:mvn:... feature statement?
Regards
Be
Hi Alexander,
you didn't name your JMS XA resource. Set a name property at
JcaPooledConnectionFactory e.g. amq. That should solve this Exception
Regards,
Benjamin
Am 15.12.2017 um 16:41 schrieb alexander.sah...@brodos.de:
> Hi there.
>
> Following the description on
> http://cxf.apache.org/doc
Hi Scott,
timeout for blacklisting is 5000ms. (see
http://felix.apache.org/documentation/subprojects/apache-felix-event-admin.html)
Regards
Benjamin
Am 13.06.2018 um 17:41 schrieb Leschke, Scott:
> I'm having an issue where events stop getting delivered to a bundle the cause
> of which appear
Hi JB,
if I install pax-jdbc-derby on a fresh Karaf 4.2.3-SNAPSHOT I do not get
a DataSourceFactory registered. I also do not found any code in derby
sources that does anything about that if do not install pax-jdbc to get
the Driver instrumented.
Regards
Benjamin
Am 04.02.2019 um 16:30 schrieb
ple itest (jdbc example) use Derby without problem.
>
> Regards
> JB
>
> On 04/02/2019 20:23, Benjamin Graf wrote:
>> Hi JB,
>>
>> if I install pax-jdbc-derby on a fresh Karaf 4.2.3-SNAPSHOT I do not get
>> a DataSourceFactory registered. I also do not found any c
This way pax-jdbc-derby also need pax-jdbc feature to get installed!
Am 04.02.2019 um 20:57 schrieb Benjamin Graf:
> Hi JB,
>
> I install pax-jdbc-config and pax-jdbc-derby. After installing pax-jdbc
> I got the derby DataSourceFactory. IMHO pax-jdbc is not mandatory to
> inst
gt;
> On 04/02/2019 20:59, Benjamin Graf wrote:
>> This way pax-jdbc-derby also need pax-jdbc feature to get installed!
>>
>> Am 04.02.2019 um 20:57 schrieb Benjamin Graf:
>>> Hi JB,
>>>
>>> I install pax-jdbc-config and pax-jdbc-derby. After instal
your point: in previous version, you also need
> pax-jdbc to get the adapter working.
>
> What are you suggesting ?
>
> Regards
> JB
>
> On 04/02/2019 21:08, Benjamin Graf wrote:
>> Hu JB,
>>
>> Just to summarize:
>>
>> Karaf jdbc installs
ings working.
>
> If you don't mind, I would like to release Karaf 4.2.3 like this (as
> it works fine). In the mean time, I'm creating a Jira at Pax JDBC to
> add the org.osgi.service.jdbc bundle in pax-jdbc-derby feature.
>
> OK ?
>
> Regards
> JB
>
> On
onna investigate the Derby case ;)
>
> Regards
> JB
>
> On 04/02/2019 21:36, Benjamin Graf wrote:
>> Hi,
>>
>> I'm a little bit confused:
>>
>>
>> mvn:org.osgi/org.osgi.service.jdbc/1.0.0
>>
>>
>>
>>
Hi together,
I try to switch JAXB implemantion (API) for custom distribution on Java
8 from version 2.2 to 2.3. One step I need is to update jre.properties
which comes from Karaf framework.kar. Updating via hardcoded
jre.properties at the end of build is the option I would like to avoid!
Actually
Hi,
I'm actually struggling how to use the API from the org.osgi.enterprise
bundle. I actually know that deploying via felix fileinstall fails and
causes karaf dying (KARAF-2006). Installing via feature or install
command is successful. But in my opinion it's not a good solution to
deploy a bundle
4-10-03 10:54 GMT+02:00 Benjamin Graf <mailto:benjamin.g...@gmx.net>>:
>
> Hi,
>
> I'm actually struggling how to use the API from the
> org.osgi.enterprise
> bundle. I actually know that deploying via felix fileinstall fails and
> causes k
ause,
> depending of the OSGi version, the package moved.
>
> Previously, org.osgi.service.jdbc was in osgi-compendium, now it moved
> to osgi-enterprise.
>
> I would create the Jira at OPS4j as it could be exported there.
>
> Regards
> JB
>
> On 10/03/2014 06:35 PM, Benj
Hi all together,
forget about the docs available. A lot of stuff has been added to aries
transaction jdbc in the last months. I suggest to look on the code itself or
usuage of pax-jdbc-config and pax-jdbx-pool-aries. There is a bit of docs on
the pax wiki as far as I remember.
Regards Benjamin
Hi,
I think Christians information about Aries JDBC are a bot out dated.
Aries JDBC ist not only about XADataSource wrapping anymore. It's
purpose is about integration and pooling of XA and non-XA DataSources
with Aries Transaction. It's build on top of Geronimo Connector and
TranQL and therefore
30 matches
Mail list logo
