How about storing the fact that the initialization is done in the data?
I have seen this with liquibase.
Liquibase is a tool that manages database updates. It stores the version of
the installed data in a table.
So when you install a new version it can do the necessary updates and then
stores the
Hi JB
I did Feature:install the Transaction Feature. Could it be, that I have a
Version Problem? How can I find out?
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
Not sure I understand your notion of "service changed" :-)
I use the term "service" in a colloquial sense. I don't mean "OSGi service".
Let me try it that way:
My release build produces a self-contained tarball of the entire code of my
service.
My "devops" automation (in Jenkins) deploys the
I don’t know if this is better...
I would use a configuration instead of a file. (Details assume karaf is using
r7 ca, I don’t know if this is true yet)
Install the configuration from json in the bundle (this is the r7 bit). It
needs 2 entries, current version and last updated version
You mean the logic should only execute if the service is "changed", but not in
the case where the service is stopped and restarted?
-Original Message-
From: Max Spring [mailto:m2spr...@springdot.org]
Sent: Thursday, June 07, 2018 7:40 PM
To: user@karaf.apache.org
Subject: execute only
I've got a Karaf-based service.
Whenever I deploy a new revision of my service, I need to execute some code
only at the very first startup.
I have this first-time functionality available as a Karaf command which I
currently run manually each time right after startup after a new deployment.
I'd
Please see the patch and my comment on KARAF-5764, I think we need more change
to support java11 in KARAF.
As XBean also embed asm source, so we need a new XBean release which build
against ASM6.2, as well as a new easymock release.
Besides, Since JDK11, those modules get removed from JDK
*
Hello,
Using Karaf 4.2.0, I want to update a property in my custom distribution. So I
add file src/main/karaf/assembly-property-edits.xml with:
org.ops4j.pax.web.cfg
put
org.osgi.service.http.port
8182
The result is:
#Modified by
I'm pretty sure you will love the new examples where the readme mentions all
the steps/features to install.
Regards
JB
Le 7 juin 2018 à 19:47, à 19:47, ceugster a écrit:
>Hi François
>this did not solve the problem. I think there are unresolved
>dependencies,
>but I don't see what bundles are
Did you install the transaction feature (not the bundle) ? It brings the
transaction.blueprint namespace.
Regards
JB
Le 7 juin 2018 à 19:47, à 19:47, ceugster a écrit:
>Hi François
>this did not solve the problem. I think there are unresolved
>dependencies,
>but I don't see what bundles are
You need to install the "transaction" feature:
> repo-add enterprise
> feature:install transaction
Cheers,
Guillaume
2018-06-06 20:05 GMT+02:00 ceugster :
> Hi
> I try to implement a jpa bundle into karaf 4.2.0. with tycho i build the
> bundles, that works fine. Then in karaf I do
Hi François
this did not solve the problem. I think there are unresolved dependencies,
but I don't see what bundles are missing.
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
Hi,
In your error trace, we can see :
Caused by: org.xml.sax.SAXParseException; cvc-complex-type.2.4.c:
xDCbereinstimmungsplatzhalter ist streng, aber es kann keine Deklaration
fxFCr Element 'jpa:context' gefunden werden.
In your bundle list you have the 2.2.0 version of the Java Persistance
Hi Serge,
I just submitted Aries Proxy Impl 1.1.2 with ASM 6.2 this morning,
bringing support of Java 9, 10, 11.
As soon as the vote passed, I will update in Karaf. The purpose is to
include this for Karaf 4.2.1 (planned next week), in order to give us
time to test.
Before 4.2.1, I have also to
Hello,
With the upcoming release of JDK 11 (planned for September), I was
wondering what the plans for supporting it looked like ? Are we expecting
any kind of blocking problems ? Should be simpler than JDK 9 I think.
I didn't follow the JDK 10 support, did that involve any problems ?
cheers,
... and the blueprint is:
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:jpa="http://aries.apache.org/xmlns/jpa/v2.0.0;
xmlns:tx="http://aries.apache.org/xmlns/transactions/v1.1.0;>
Erf, we don't see your change on the mailing list (I guess you used the
nabble forum).
Can you send a new message with the blueprint please ?
Thanks,
Regards
JB
On 07/06/2018 16:25, ceugster wrote:
> Hi
> sorry for that, i corrected the message and added the blueprint, hope it
> helps :)
>
>
Hi
sorry for that, i corrected the message and added the blueprint, hope it
helps :)
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
That's the persistence.xml, not the blueprint.
The problem seems in your blueprint where you use .
Regards
JB
On 07/06/2018 15:32, ceugster wrote:
> ... and the blueprint is:
>
>
> http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
>
... and the blueprint is:
http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd; version="2.0"
xmlns="http://java.sun.com/xml/ns/persistence;>
Hi
I changed the jdk to jdk-9. And indeed there is no more complaining about
dependencies. Thank you for your help!
Now I get the following message, when I invoke feature:install my bundles.
The jpa bundle failed to start and bundle:diag says:
Herakles Jpa Persistence Bundle (133)
Oh right, Java 10 is not fully supported yet.
I sent a new aries proxy release on vote this morning to have a better support
of java 10 and 11. It's planned for Karaf 4.2.1.
Regards
JB
Le 7 juin 2018 à 13:12, à 13:12, Francois Papon
a écrit:
>Hi,
>
>You should use Java <= 9 for Karaf 4.2.0.
Hi,
You should use Java <= 9 for Karaf 4.2.0.
Can you tried with Java 9 ?
François Papon
fpa...@apache.org
Open3m - https://www.open3m.io
Le 07/06/2018 à 16:06, ceugster a écrit :
> Hi
> I reinstalled apache-karaf-4.2.0 from scratch and did afterwards:
>
> feature:install pax-transx-tm
>
I don't see the Aries blueprint bundles. Did you have install the
aries-blueprint before any other features ?
Regards
JB
Le 7 juin 2018 à 12:31, à 12:31, ceugster a écrit:
>Hi
>
>I tried to restart the bundle in question, but nothing changed.
>
>This is the list of my bundle:list
>
Hi
I reinstalled apache-karaf-4.2.0 from scratch and did afterwards:
feature:install pax-transx-tm
feature:install aries-blueprint
feature:install eclipselink
on the last entry I got the following stack trace (see later on) saying,
invalid java version 54:
My system:property
os.arch=x86_64
Hi
I tried to restart the bundle in question, but nothing changed.
This is the list of my bundle:list
karaf@root()> feature:uninstall pax-cdi
karaf@root()> bundle:list
START LEVEL 100 , List Threshold: 50
ID │ State │ Lvl │ Version │ Name
Hi,
I have also run into this issue. I think there is a bug in Karaf 4.2.0 related
to blueprint namespace loading.
It does not happen all the time, but when it is the case, the solution is to
manually restart bundle org.apache.aries.transaction.blueprint-2.1.0.
Regards,
--
Nicolas Dutertry
27 matches
Mail list logo
