Hi,
I gonna check but it seems that a refresh has been triggered, upgrading
proxy which breaks Cellar itself, probably due to camel-scr feature.
By the way, you can use cluster:feature-install, cluster-sync is not
required, it's only used when you have a split brain.
Regards
JB
On 11/06/2018
Hi,
In Karaf, the HTTP service is provided by Pax Web, and it's the
recommended approach (feature:install http).
Any reason why to use Felix HTTP instead ?
Anyway, regarding your error, I have to check if the Felix HTTP bundle
has been compiled with Java 7/8.
Regards
JB
On 11/06/2018 22:11,
I am new to cellar and trying to do POC, I did following steps
- Install Karaf(4.1.5) on two instances.
- feature:repo-add
mvn:org.apache.karaf.cellar/apache-karaf-cellar/4.1.1/xml/features (On both
instances)
- feature:install cellar (On both instances)
- Edit hazelcast.xml on both instances
Did you able to fix cluster:synch issue, as i am still facing issue.
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
I'm trying to get org.apache.felix.http.bundle v3.0.0 to work under Karaf
v4.2.0 but am not having much success. We are using Karaf on an internal
network that does not have Internet access so I cannot use the http feature
that is already within Karaf.
We are upgrading Karaf from v3.0 and we were
(sorry for disturbing you yet)
Ok, I did
karaf@root()> service:list DataSource
karaf@root()> jdbc:ds-create -dn derby -url
"jdbc:derby:fancyfoods;create=true" fancyfoods
karaf@root()> service:list DataSource
[javax.sql.DataSource]
--
dataSourceName = fancyfoods
Thanks guys for this, I've been having hard time trying to solve this!
Il lun 11 giu 2018, 16:44 Ignasi Barrera ha scritto:
> Thanks for the quick reply! It's always a pleasure to ask for help in this
> list :)
>
> On 11 June 2018 at 16:35, Jean-Baptiste Onofré wrote:
>
> > Hi,
> >
> > I'm
Up to Karaf 3, the Karaf JDBC feature created a datasource service using
blueprint (as you do).
It means that:
1. The JDBC feature had a dependency to blueprint
2. Changing the datasource configuration itself triggered
unregister/register of the datasource service (as the blueprint
container is
What do you mean by
jbonofre wrote
> By the way, why don't you use pax-jdbc ? We removed the blueprint
> approach for pax-jdbc to avoid the blueprint dependency and provide a
> more dynamic approach.
? Are there bundles that I have to uninstall and install?
Regards
Christian
--
Sent from:
Thanks for the quick reply! It's always a pleasure to ask for help in this
list :)
On 11 June 2018 at 16:35, Jean-Baptiste Onofré wrote:
> Hi,
>
> I'm gonna help on this one, as I also need this in a personal project ;)
>
> I'm starting a "fixing" branch.
>
> Regards
> JB
>
> On 11/06/2018
Hi,
I'm gonna help on this one, as I also need this in a personal project ;)
I'm starting a "fixing" branch.
Regards
JB
On 11/06/2018 16:30, Ignasi Barrera wrote:
> This thread is cross-posted to the jclouds-dev list.
>
> We (jclouds) are trying to move our codebase to Java 8 and are stuck
>
This thread is cross-posted to the jclouds-dev list.
We (jclouds) are trying to move our codebase to Java 8 and are stuck with
an issue we've found in our Karaf integration that we are not able to
understand.
We have our codebase compiled with Java 8, and our Karaf integration (built
with Java 8
that was it! It seems that I have to learn more about this dynamic import, i
did not know about. Thanks
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
Can you try a bundle:refresh too ?
Regards
JB
On 11/06/2018 13:43, ceugster wrote:
> Yes bundle derby is installed as shown in my last message. Now I did a
>
> 245 │ Active │ 80 │ 1.0.1 │ Apache Aries Blueprint Web
> OSGI
> karaf@root()> bundle:dynamic-import 245
> Enabling
That's not the correct bundle for the import.
Your bundle blueprint is the one of the xml.
Check this bundle (241 according to your previous e-mail).
By the way, why don't you use pax-jdbc ? We removed the blueprint
approach for pax-jdbc to avoid the blueprint dependency and provide a
more
Hi,
if you use maven, test are not included. So your junit test cases and
deps should be in src/test/java.
For remote debug, it's really easy: just start karaf with debug option
(./karaf debug), then connect your IDE to the 5005 remote. You will have
your breakpoint handled.
Regards
JB
On
Hello,
I've taken over some application written OSGi using Felix and Karaf being
deployed as a docker container. I have basically two (beginner) questions
here:
* It seems that the JUnit test cases are deployed together with the bundle
and started when the bundle's start method is
Yes bundle derby is installed as shown in my last message. Now I did a
245 │ Active │ 80 │ 1.0.1 │ Apache Aries Blueprint Web
OSGI
karaf@root()> bundle:dynamic-import 245
Enabling dynamic imports on bundle org.apache.aries.blueprint.webosgi [245]
karaf@root()> bundle:info 245
HI
in the meantime I did a step back following the tutorial in enterprise osgi
in action by Holly Cummins and Timothy Ward. I stuck while creating a data
source in the old fashion blueprint way (using xml). I get a stack trace
(see below) when registering the data source:
karaf@root()> diag 241
Hi *,
we are using datasources for connections to an Oracale database.
Now we have to use failover, because the backend team switched from
loadbalancer to something else, I dont know.
Currently this is our configuration:
osgi.jdbc.driver.class = oracle.jdbc.OracleDriver
osgi.jdbc.driver.name
20 matches
Mail list logo
