Hello jbonofre,
Thanks for your answer, I have specified slf4j as "optional" in my pom.xml
and I have excluded it in the karaf-maven-plugin configuration as below. Is
it the best way to do it?
Now, Karaf tries to install it. But it is very very long... such long that
it has never been installed
Hi,
it's not possible to attach file on message for the mailing list.
Can you please send it to me via paste.bin or gist and eventually share your
project ?
Thanks,
Regards
JB
On 12/15/2017 10:21 AM, GFO wrote:
Hello jbonofre,
Thanks for your answer, I have specified slf4j as "optional" in
Hello,
Indeed, I didn't notice my examples are not in my messages... thanks for the
information!
exclusion of slf4j : https://pastebin.com/Wa36sas1
feature.xml : https://pastebin.com/wr9S2q2t
Thanks.
Regards,
GFO
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
Hi,
you should try to depend on already existing features.
For one, there are spring features available from Karaf itself, that'll
reduce already.
Same is for all the logging part.
Make sure to define your logging dependencies in your maven pom as
provided
CXF etc. are also features which already
I did one more test. I've created simple environment based on two karaf
instances with cellar and cellar-dosgi. I've take karaf 4.1.1 and cellar
4.1.1.
First I set up ports on karaf instances for allow to run both. Then I use
command:
install -s wrap:mvn:com.oracle/ojdbc6/11.2.0
Next I've instal
I will check, but it depends of the sync policy define on the node as you didn't
use cluster:feature-install.
Give me time to complete 4.1.4 release preparation and I will test.
Regards
JB
On 12/15/2017 12:47 PM, Dominik Marciniszyn wrote:
I did one more test. I've created simple environment
Hi there.
Following the description on http://cxf.apache.org/docs/jms-transactions.html,
I set up a JMS XA transaction together with pax-jdbc datasource in karaf 4.1.2.
The datasource looks like this:
osgi.jdbc.driver.name = mariadb
dataSourceName = jmsTest
databaseName = test
user = test
passw
Hi again Michael,
Just to be clear, you’re saying that something like the following will achieve
the desired affect:
@Reference
volatile ConfigurationAdmin ca;
Dictionary serviceProps =
toDictionary(previouslyInitializedServiceProperties);
serviceProps.put(ConfigurationAdmin.SERVICE_FACTORYPI
