Re: execute only at first startup?

[Christian Schneider]

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 new version.

Best
Christian

Am Fr., 8. Juni 2018 um 03:42 Uhr schrieb Max Spring :

> 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 tarball on a test VM
> together with the production data.
>
> After this deployment, the very first time the Karaf container starts up,
> I want to run some initialization logic.
> But only this very first time. Any subsequent Karaf container start up
> should not do this initialization any more.
>
> -Max
>
>
> On 06/07/2018 05:48 PM, Leschke, Scott wrote:
> > 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 at first startup?
> >
> > 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 like to automate this.
> >
> > I'm thinking of using a marker file somewhere to indicate "first
> startup".
> > I'd have a new bundle checking for this file when it starts up. When it
> detect the file, the bundle executes my business logic initialization and
> then deletes the marker file.
> >
> > Or, is there something better for this scenario?
> >
> > -Max
> >
>


-- 
-- 
Christian Schneider
http://www.liquid-reality.de

Computer Scientist
http://www.adobe.com

Re: Unresolved dependency using blueprint transaction

[ceugster]

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

Re: execute only at first startup?

[Max Spring]

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 tarball on a test VM together 
with the production data.

After this deployment, the very first time the Karaf container starts up, I 
want to run some initialization logic.
But only this very first time. Any subsequent Karaf container start up should 
not do this initialization any more.

-Max


On 06/07/2018 05:48 PM, Leschke, Scott wrote:

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 at first startup?

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 like to automate this.

I'm thinking of using a marker file somewhere to indicate "first startup".
I'd have a new bundle checking for this file when it starts up. When it detect 
the file, the bundle executes my business logic initialization and then deletes 
the marker file.

Or, is there something better for this scenario?

-Max

Re: execute only at first startup?

[David Jencks]

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 (initialized to 0).
Have a ds component requiring the configuration, and with a mandatory reference 
to config admin. In the activate method, where the configuration arrives as a 
parameter, compare the current and last updated versions and if they differ do 
your initialization, and then use ca to update the configuration so the 
versions match.

The current version could be hard coded in the class if that is easier than 
updating the json.

David Jencks 
Sent from my iPhone

> On Jun 7, 2018, at 5:48 PM, Leschke, Scott  wrote:
> 
> 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 at first startup?
> 
> 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 like to automate this.
> 
> I'm thinking of using a marker file somewhere to indicate "first startup".
> I'd have a new bundle checking for this file when it starts up. When it 
> detect the file, the bundle executes my business logic initialization and 
> then deletes the marker file.
> 
> Or, is there something better for this scenario?
> 
> -Max
> 

RE: execute only at first startup?

[Leschke, Scott]

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 at first startup?

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 like to automate this.

I'm thinking of using a marker file somewhere to indicate "first startup".
I'd have a new bundle checking for this file when it starts up. When it detect 
the file, the bundle executes my business logic initialization and then deletes 
the marker file.

Or, is there something better for this scenario?

-Max

execute only at first startup?

[Max Spring]

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 like to automate this.

I'm thinking of using a marker file somewhere to indicate "first startup".
I'd have a new bundle checking for this file when it starts up. When it detect 
the file, the bundle executes my business logic initialization and then deletes 
the marker file.

Or, is there something better for this scenario?

-Max

Re: Any plans for supporting JDK 11 ?

[Freeman Fang]

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
* java.corba — CORBA
 * java.transaction — The subset of the Java Transaction API defined by Java SE 
to support CORBA Object Transaction Services
 * java.activation — JavaBeans Activation Framework
 * java.xml.bind — Java Architecture for XML Binding (JAXB)
 * java.xml.ws — Java API for XML Web Services (JAX-WS), Web Services Metadata 
for the Java Platform, and SOAP with Attachments for Java (SAAJ)
 * java.xml.ws.annotation — The subset of the JSR-250 Common Annotations 
defined by Java SE to support web services

So I think we don't need to use --patch-module for those APIs which already get 
removed. What we do is just use normal bundle for those APIs, or if we really 
need those API in boot stage we can put those in $KARAF_HOME/lib/boot folder, 
so far we need jaxb and activation in lib/boot/folder as features.core need 
those.

[1]https://issues.apache.org/jira/browse/KARAF-5764 


Cheers
－
Freeman(Yue) Fang

Red Hat, Inc. 
FuseSource is now part of Red Hat



> On Jun 8, 2018, at 1:37 AM, Jean-Baptiste Onofré  wrote:
> 
> 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 work on Pax Web (7.1.1) supporting Jetty
> 9.4.10 supporting new Java version as well.
> 
> So, to summarize, 4.2.1 should support Java 10 & 11, thanks to the ASM
> 6.2 update + Aries Proxy + Pax Web/Jetty update (all Jira are created
> and in my bucket).
> 
> Regards
> JB
> 
> On 07/06/2018 17:35, Serge Huber wrote:
>> 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,
>>   Serge... 
> 
> -- 
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

Karaf assembly plugin property edits erasing properties

[Alex Soto]

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 org.apache.karaf.tools.utils.KarafPropertiesFile
#Thu Jun 07 15:39:28 EDT 2018
org.osgi.service.http.port=8182


The issue is that it erased all other properties.  Normally, this file has the 
following:

org.osgi.service.http.port=8181
javax.servlet.context.tempdir=${karaf.data}/pax-web-jsp
org.ops4j.pax.web.config.file=${karaf.etc}/jetty.xml


Is this the expected behavior?   How can I preserve the rest of the properties 
and modify just one?

Best regards,
Alex soto

Re: Unresolved dependency using blueprint transaction

[Jean-Baptiste Onofré]

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 missing.
>
>
>
>
>--
>Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html

Re: Unresolved dependency using blueprint transaction

[Jean-Baptiste Onofré]

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 missing.
>
>
>
>
>--
>Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html

Re: Unresolved dependency using blueprint transaction

[Guillaume Nodet]

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 feature:repo-add and
> feature:install works well too. But listing the bundles shows up status
> grace period for my jpa bundle. bundle:diag shows:
>
> Status: GracePeriod
> Blueprint
> 06.06.18, 19:59
> Missing dependencies:
> (&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.
> service.blueprint.namespace=http://aries.apache.org/xmlns/
> transactions/v2.0.0))
> Declarative Services
>
> I tried other versions of transactions too (e.g. v1.0.0, v1.1.0) How can I
> resolve this problem?
> Thank you for any hints!
> Christian
>
>
>
> --
> Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
>



-- 

Guillaume Nodet

Re: Unresolved dependency using blueprint transaction

[ceugster]

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

Re: Unresolved dependency using blueprint transaction

[Francois Papon]

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
API and the 2.6.1 version of the Apache Aries JPA  :

 67 │ Active  │  80 │ 2.2.0.v201708071007 │ Java Persistence API 2.2
 68 │ Active  │  80 │ 2.6.1   │ Apache Aries JPA

but in your blueprint.xml you define 2.0.0 xmlns version.

Maybe you should align the version in your blueprint.xml


François Papon
fpa...@apache.org
Open3m - https://www.open3m.io

Le 07/06/2018 à 18:41, ceugster a écrit :
> ... 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";>
>
>  class="ch.eugster.herakles.persistence.jpa.query.JpaQuery">
> 
> 
> 
> 
>
>  interface="ch.eugster.herakles.persistence.api.query.Query"
> />
>
>  class="ch.eugster.herakles.persistence.jpa.query.Populator" 
> init-method="populate" activation="eager">
> 
> 
> 
> 
>
>
>
> --
> Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html

Re: Any plans for supporting JDK 11 ?

[Jean-Baptiste Onofré]

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 work on Pax Web (7.1.1) supporting Jetty
9.4.10 supporting new Java version as well.

So, to summarize, 4.2.1 should support Java 10 & 11, thanks to the ASM
6.2 update + Aries Proxy + Pax Web/Jetty update (all Jira are created
and in my bucket).

Regards
JB

On 07/06/2018 17:35, Serge Huber wrote:
> 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,
>   Serge... 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Any plans for supporting JDK 11 ?

[Serge Huber]

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,
  Serge...

Re: Unresolved dependency using blueprint transaction

[ceugster]

... 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";>

















--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html

Re: Unresolved dependency using blueprint transaction

[Jean-Baptiste Onofré]

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 :)
> 
> 
> 
> --
> Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Unresolved dependency using blueprint transaction

[ceugster]

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

Re: Unresolved dependency using blueprint transaction

[Jean-Baptiste Onofré]

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
> http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd"; version="2.0"
> xmlns="http://java.sun.com/xml/ns/persistence";>
>   
>   
> osgi.service/jdbc/xaheraklesdb
>   
> osgi.service/jdbc/heraklesdb
>   
> ch.eugster.herakles.persistence.jpa.util.URIConverter
>   
> ch.eugster.herakles.persistence.jpa.util.UUIDConverter
> 
>   
> ch.eugster.herakles.persistence.jpa.model.JpaAbstractEntity
>   
> ch.eugster.herakles.persistence.jpa.model.JpaPermission
>   
> ch.eugster.herakles.persistence.jpa.model.JpaRolePermission
>   
> ch.eugster.herakles.persistence.jpa.model.JpaSystemRole
>   
> ch.eugster.herakles.persistence.jpa.model.JpaSystemUser
>   true
>   
> 
> 
> 
> 
> --
> Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Unresolved dependency using blueprint transaction

[ceugster]

... 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";>


osgi.service/jdbc/xaheraklesdb

osgi.service/jdbc/heraklesdb

ch.eugster.herakles.persistence.jpa.util.URIConverter

ch.eugster.herakles.persistence.jpa.util.UUIDConverter


ch.eugster.herakles.persistence.jpa.model.JpaAbstractEntity

ch.eugster.herakles.persistence.jpa.model.JpaPermission

ch.eugster.herakles.persistence.jpa.model.JpaRolePermission

ch.eugster.herakles.persistence.jpa.model.JpaSystemRole

ch.eugster.herakles.persistence.jpa.model.JpaSystemUser
true





--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html

Re: Unresolved dependency using blueprint transaction

[ceugster]

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)
-
Status: Failure
Blueprint
07.06.18, 15:27
Exception: 
Unable to validate xml
org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to
validate xml
at org.apache.aries.blueprint.parser.Parser.validate(Parser.java:349)
at org.apache.aries.blueprint.parser.Parser.validate(Parser.java:336)
at
org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:345)
at
org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:278)
at
org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:299)
at
org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:268)
at
org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:264)
at
org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:254)
at
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)
at
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)
at
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)
at
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)
at
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)
at
org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1179)
at
org.apache.felix.framework.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:730)
at
org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:485)
at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4579)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2174)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)
at
org.apache.karaf.features.internal.service.BundleInstallSupportImpl.startBundle(BundleInstallSupportImpl.java:161)
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1116)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:996)
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1025)
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:964)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.base/java.lang.Thread.run(Thread.java:844)
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.
at
java.xml/com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:204)
at
java.xml/com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:135)
at
java.xml/com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:395)
at
java.xml/com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:326)
at
java.xml/com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:283)
at
java.xml/com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:510)
at
java.xml/com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3587)
at
java.xml/com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:2142)
at
java.xml/com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:828)
at
java.xml/com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.beginNode(DOMValidatorHelper.java:277)
at
java.xml/com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.va

Re: Unresolved dependency using blueprint transaction

[Jean-Baptiste Onofré]

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.
>
>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
>> 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
>> os.name=Mac OS X
>> os.version=10.13.5
>> path.separator=:
>> socksNonProxyHosts=local|*.local|169.254/16|*.169.254/16
>> sun.arch.data.model=64
>>
>sun.boot.library.path=/Library/Java/JavaVirtualMachines/jdk-10.0.1.jdk/Contents/Home/lib
>> sun.cpu.endian=little
>> sun.cpu.isalist=
>> sun.io.unicode.encoding=UnicodeBig
>> sun.java.command=org.apache.karaf.main.Main
>> sun.java.launcher=SUN_STANDARD
>> sun.jnu.encoding=UTF-8
>> sun.management.compiler=HotSpot 64-Bit Tiered Compilers
>> sun.os.patch.level=unknown
>> user.country=CH
>>
>user.dir=/Users/christian/Projekte/ceugster/Frameworks/apache-karaf-4.2.0
>> user.home=/Users/christian
>> user.language=de
>> user.name=christian
>> user.timezone=Europe/Zurich
>> xml.catalog.files=
>> karaf@root()>  
>   
>>
>> and the stack trace:
>>
>> karaf@root()> feature:install eclipselink
>> 13:59:37.522 [features-3-thread-1] ERROR
>> org.apache.aries.blueprint.container.ServiceRecipe - Error retrieving
>> service from ServiceRecipe[name='.component-4']
>> org.osgi.service.blueprint.container.ComponentDefinitionException:
>Error
>> setting property: PropertyDescriptor getter:
>> null, setter: [class
>>
>org.apache.aries.transaction.parsing.TxNamespaceHandler.setBlueprintContainer(interface
>> org.osgi.service.blueprint.container.BlueprintContainer)]
>>  at
>>
>org.apache.aries.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:821)
>> ~[?:?]
>>  at
>>
>org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:784)
>> ~[?:?]
>>  at
>>
>org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:765)
>> ~[?:?]
>>  at
>>
>org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:699)
>> ~[?:?]
>>  at
>>
>org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:666)
>> ~[?:?]
>>  at
>>
>org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:81)
>> ~[?:?]
>>  at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
>>  at
>>
>org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:90)
>> ~[?:?]
>>  at
>>
>org.apache.aries.blueprint.di.RefRecipe.internalCreate(RefRecipe.java:62)
>> ~[?:?]
>>  at
>>
>org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:108)
>> ~[?:?]
>>  at
>>
>org.apache.aries.blueprint.container.BeanRecipe.getInstance(BeanRecipe.java:268)
>> ~[?:?]
>>  at
>>
>org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:685)
>> ~[?:?]
>>  at
>>
>org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:666)
>> ~[?:?]
>>  at
>>
>org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:108)
>> ~[?:?]
>>  at
>>
>org.apache.aries.blueprint.container.ServiceRecipe.createService(ServiceRecipe.java:285)
>> ~[?:?]
>>  at
>>
>org.apache.aries.blueprint.container.ServiceRecipe.internalGetService(ServiceRecipe.java:252)
>> ~[?:?]
>>  at
>>
>org.apache.aries.blueprint.container.ServiceRecipe.getService(ServiceRecipe.java:365)
>> ~[?:?]
>>  at
>>
>org.apache.aries.blueprint.container.ServiceRecipe$TriggerServiceFactory.getService(ServiceRecipe.java:540)
>> ~[?:?]
>>  at
>>
>org.apache.felix.framework.ServiceRegistrationImpl.getFactoryUnchecked(ServiceRegistrationImpl.java:347)
>> ~[?:?]
>>  at
>>
>org.apache.felix.framework.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:247)
>> ~[?:?]
>>  at
>>
>org.apache.felix.framework.ServiceRegistry.getService(ServiceRegistry.java:350)
>> ~[?:?]
>>  at org.apache.felix.framework.Felix.getService(Felix.java:3737)
>~[?:?]
>>  at
>>
>org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:470)
>> ~[?:?]
>>  at
>>
>org.apache.aries.blueprint.container.BlueprintEventDispatcher$2.addingService(BlueprintEventDispatcher.java:95)
>> ~[?:?]
>>  at
>>
>org.apache.aries.blueprint.container.BlueprintEventDispatcher$2.addingService(BlueprintEventDispatcher.java:93)
>> ~[?:?]
>>  at
>>
>org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941)
>> ~[?:?]
>

Re: Unresolved dependency using blueprint transaction

[Francois Papon]

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
> 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
> os.name=Mac OS X
> os.version=10.13.5
> path.separator=:
> socksNonProxyHosts=local|*.local|169.254/16|*.169.254/16
> sun.arch.data.model=64
> sun.boot.library.path=/Library/Java/JavaVirtualMachines/jdk-10.0.1.jdk/Contents/Home/lib
> sun.cpu.endian=little
> sun.cpu.isalist=
> sun.io.unicode.encoding=UnicodeBig
> sun.java.command=org.apache.karaf.main.Main
> sun.java.launcher=SUN_STANDARD
> sun.jnu.encoding=UTF-8
> sun.management.compiler=HotSpot 64-Bit Tiered Compilers
> sun.os.patch.level=unknown
> user.country=CH
> user.dir=/Users/christian/Projekte/ceugster/Frameworks/apache-karaf-4.2.0
> user.home=/Users/christian
> user.language=de
> user.name=christian
> user.timezone=Europe/Zurich
> xml.catalog.files=
> karaf@root()> 
>   
> 
>
> and the stack trace:
>
> karaf@root()> feature:install eclipselink
> 13:59:37.522 [features-3-thread-1] ERROR
> org.apache.aries.blueprint.container.ServiceRecipe - Error retrieving
> service from ServiceRecipe[name='.component-4']
> org.osgi.service.blueprint.container.ComponentDefinitionException: Error
> setting property: PropertyDescriptor  null, setter: [class
> org.apache.aries.transaction.parsing.TxNamespaceHandler.setBlueprintContainer(interface
> org.osgi.service.blueprint.container.BlueprintContainer)]
>   at
> org.apache.aries.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:821)
> ~[?:?]
>   at
> org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:784)
> ~[?:?]
>   at
> org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:765)
> ~[?:?]
>   at
> org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:699)
> ~[?:?]
>   at
> org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:666)
> ~[?:?]
>   at
> org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:81)
> ~[?:?]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
>   at
> org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:90)
> ~[?:?]
>   at
> org.apache.aries.blueprint.di.RefRecipe.internalCreate(RefRecipe.java:62)
> ~[?:?]
>   at
> org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:108)
> ~[?:?]
>   at
> org.apache.aries.blueprint.container.BeanRecipe.getInstance(BeanRecipe.java:268)
> ~[?:?]
>   at
> org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:685)
> ~[?:?]
>   at
> org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:666)
> ~[?:?]
>   at
> org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:108)
> ~[?:?]
>   at
> org.apache.aries.blueprint.container.ServiceRecipe.createService(ServiceRecipe.java:285)
> ~[?:?]
>   at
> org.apache.aries.blueprint.container.ServiceRecipe.internalGetService(ServiceRecipe.java:252)
> ~[?:?]
>   at
> org.apache.aries.blueprint.container.ServiceRecipe.getService(ServiceRecipe.java:365)
> ~[?:?]
>   at
> org.apache.aries.blueprint.container.ServiceRecipe$TriggerServiceFactory.getService(ServiceRecipe.java:540)
> ~[?:?]
>   at
> org.apache.felix.framework.ServiceRegistrationImpl.getFactoryUnchecked(ServiceRegistrationImpl.java:347)
> ~[?:?]
>   at
> org.apache.felix.framework.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:247)
> ~[?:?]
>   at
> org.apache.felix.framework.ServiceRegistry.getService(ServiceRegistry.java:350)
> ~[?:?]
>   at org.apache.felix.framework.Felix.getService(Felix.java:3737) ~[?:?]
>   at
> org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:470)
> ~[?:?]
>   at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher$2.addingService(BlueprintEventDispatcher.java:95)
> ~[?:?]
>   at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher$2.addingService(BlueprintEventDispatcher.java:93)
> ~[?:?]
>   at
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941)
> ~[?:?]
>   at
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:870)
> ~[?:?]
>   at
> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
> ~[?:?]
>   at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)

RE: Unresolved dependency using blueprint transaction

[Jean-Baptiste Onofré]

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
>
>karaf@root()> feature:uninstall pax-cdi
>karaf@root()> bundle:list
>START LEVEL 100 , List Threshold: 50
> ID │ State   │ Lvl │ Version │ Name
>┼─┼─┼─┼
>21 │ Active  │  80 │ 4.2.0   │ Apache Karaf :: OSGi
>Services :: Event
>57 │ Active  │  80 │ 3.0.0   │ Expression Language
>3.0
>API
> 58 │ Active  │  80 │ 1.2.0   │ CDI APIs
>59 │ Active  │  80 │ 1.2 │ javax.interceptor
>API
>60 │ Active  │  80 │ 1.2 │ javax.transaction
>API
>61 │ Active  │  80 │ 1.1.1   │ Apache Aries
>Transaction
>Blueprint
>62 │ Active  │  80 │ 2.1.0   │ Apache Aries
>Transaction
>Blueprint
>63 │ Active  │  80 │ 1.0.2   │ Apache Felix
>Coordinator
>Service
>64 │ Active  │  80 │ 1.0.0.2 │ Apache ServiceMix ::
>Bundles :: javax.inject
> 65 │ Active  │  80 │ 0.2.0   │ pax-transx-tm-api
>66 │ Active  │  80 │ 0.2.0   │
>pax-transx-tm-geronimo
>67 │ Active  │  80 │ 2.2.0.v201708071007 │ Java Persistence API
>2.2
> 68 │ Active  │  80 │ 2.6.1   │ Apache Aries JPA
>Container adapter for EclipseLink
> 69 │ Active  │  80 │ 3.5.2.v201605171345 │ EclipseLink ANTLR
> 70 │ Active  │  80 │ 6.0.0.v201710052159 │ EclipseLink ASM
> 71 │ Active  │  80 │ 2.7.1.v20171221-bd47e8f │ EclipseLink Core
> 72 │ Active  │  80 │ 2.7.1.v20171221-bd47e8f │ EclipseLink JPA
> 73 │ Active  │  80 │ 2.7.1.v20171221-bd47e8f │ EclipseLink Hermes
>Parser
>96 │ Active  │  80 │ 4.6.0   │ Apache XBean OSGI
>Bundle
>Utilities
> 97 │ Active  │  80 │ 4.6.0   │ Apache XBean ::
>Classpath Resource Finder
>135 │ Active  │  80 │ 1.9.2.1 │ Apache ServiceMix
>::
>Bundles :: jasypt
>136 │ Active  │  80 │ 1.2.0   │ OPS4J Pax JDBC
>Generic
>Driver Extender
>137 │ Active  │  80 │ 1.2.0   │ OPS4J Pax JDBC
>Config
>138 │ Active  │  80 │ 1.2.0   │ OPS4J Pax JDBC
>Pooling
>Support Base
>139 │ Active  │  80 │ 1.0.0.201505202023  │
>org.osgi:org.osgi.service.jdbc
>145 │ Active  │  80 │ 4.2.0   │ Apache Karaf ::
>JDBC ::
>Core
>149 │ Active  │  80 │ 1.2.0   │ OPS4J Pax JDBC
>Apache
>Derby Driver Adapter
>157 │ Active  │  80 │ 1.0.0.201806071126  │ Herakles
>Persistence API
>Bundle
>158 │ GracePeriod │  80 │ 1.0.0.201806071126  │ Herakles Jpa
>Persistence
>Bundle
>159 │ Active  │  80 │ 1.0.0.201806071126  │ Herakles Derby
>Datasource Bundle
>160 │ Active  │  80 │ 10.14.200.1828579   │ Apache Derby 10.14
>karaf@root()>
>
>and the bundle:diag result
>
>karaf@root()> bundle:diag 158
>Herakles Jpa Persistence Bundle (158)
>-
>Status: GracePeriod
>Blueprint
>07.06.18, 13:26
>Missing dependencies:
>(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://aries.apache.org/xmlns/transactions/v1.1.0))
>(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://aries.apache.org/xmlns/jpa/v2.0.0))
>
>Declarative Services
>
>  
>
>
>
>--
>Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html

RE: Unresolved dependency using blueprint transaction

[ceugster]

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
os.name=Mac OS X
os.version=10.13.5
path.separator=:
socksNonProxyHosts=local|*.local|169.254/16|*.169.254/16
sun.arch.data.model=64
sun.boot.library.path=/Library/Java/JavaVirtualMachines/jdk-10.0.1.jdk/Contents/Home/lib
sun.cpu.endian=little
sun.cpu.isalist=
sun.io.unicode.encoding=UnicodeBig
sun.java.command=org.apache.karaf.main.Main
sun.java.launcher=SUN_STANDARD
sun.jnu.encoding=UTF-8
sun.management.compiler=HotSpot 64-Bit Tiered Compilers
sun.os.patch.level=unknown
user.country=CH
user.dir=/Users/christian/Projekte/ceugster/Frameworks/apache-karaf-4.2.0
user.home=/Users/christian
user.language=de
user.name=christian
user.timezone=Europe/Zurich
xml.catalog.files=
karaf@root()>   



and the stack trace:

karaf@root()> feature:install eclipselink
13:59:37.522 [features-3-thread-1] ERROR
org.apache.aries.blueprint.container.ServiceRecipe - Error retrieving
service from ServiceRecipe[name='.component-4']
org.osgi.service.blueprint.container.ComponentDefinitionException: Error
setting property: PropertyDescriptor (InterfaceCombiningClassAdapter.java:79)
~[?:?]
at
org.apache.aries.proxy.impl.interfaces.ProxyClassLoader.createProxyClass(ProxyClassLoader.java:155)
~[?:?]
at
org.apache.aries.proxy.impl.interfaces.InterfaceProxyGenerator.getProxyInstance(InterfaceProxyGenerator.java:97)
~[?:?]
at
org.apache.aries.proxy.impl.AsmProxyManager.createNewProxy(AsmProxyManager.java:80)
~[?:?]
at
org.apache.aries.proxy.impl.AbstractProxyManager.createDelegatingInterceptingProxy(AbstractProxyManager.java:77)
~[?:?]
at
org.apache.aries.proxy.impl.AbstractProxyManager.createDelegatingProxy(AbstractProxyManager.java:42)
~[?:?]
at
org.apache.aries.blueprint.container.AbstractServiceReferenceRecipe.createProxy(AbstractServiceReferenceRecipe.java:332)
~[?:?]
at
org.apache.aries.blueprint.container.ReferenceRecipe.internalCreate(ReferenceRecipe.java:125)
~[?:?]
at
org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:81)
~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at
org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:90)
~[?:?]
at
org.apache.aries.blueprint.di.RefRecipe.internalCreate(RefRecipe.java:62)
~[?:?]
at
org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:108)
~[?:?]
at
org.apache.aries.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:810)
~[?:?]
at
org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:784)
~[?:?]
at
org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:765)
~[?:?]
at
org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:699)
~[?:?]
at
org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:666)
~[?:?]
at
org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:81)
~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at
org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:90)
~[?:?]
at
org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:360)
~[?:?]
at
org.apache.aries.blueprint.container.BlueprintRepository.createInstance(BlueprintRepository.java:338)
~[?:?]
at
org.apache.aries.blueprint.container.BlueprintRepository.create(BlueprintRepository.java:152)
~[?:?]
at
org.apache.aries.blueprint.container.BlueprintContainerImpl.getComponentInstance(BlueprintContainerImpl.java:788)
~[?:?]
at
org.apache.aries.transaction.parsing.TxNamespaceHandler.setBlueprintContainer(TxNamespaceHandler.java:177)
~[?:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
~[?:?]
at
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
~[?:?]
at
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[?:?]
at java.lang.reflect.Method.invoke(Method.java:564) ~[?:?]
at
org.apache.aries.blueprint.utils.ReflectionUtils$MethodPropertyDescriptor.internalSet(ReflectionUtils.java:662)
~[?:?]
at
org.apache.aries.blueprint.utils.ReflectionUtils$PropertyDescriptor.set(ReflectionUtils.java:412)
~[?:?]
at
org.apache.aries.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:819)
~[?:?]
... 65 more
karaf@root()>  

java



--
Sent from: htt

RE: Unresolved dependency using blueprint transaction

[ceugster]

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
┼─┼─┼─┼
 21 │ Active  │  80 │ 4.2.0   │ Apache Karaf :: OSGi
Services :: Event
 57 │ Active  │  80 │ 3.0.0   │ Expression Language 3.0
API
 58 │ Active  │  80 │ 1.2.0   │ CDI APIs
 59 │ Active  │  80 │ 1.2 │ javax.interceptor API
 60 │ Active  │  80 │ 1.2 │ javax.transaction API
 61 │ Active  │  80 │ 1.1.1   │ Apache Aries Transaction
Blueprint
 62 │ Active  │  80 │ 2.1.0   │ Apache Aries Transaction
Blueprint
 63 │ Active  │  80 │ 1.0.2   │ Apache Felix Coordinator
Service
 64 │ Active  │  80 │ 1.0.0.2 │ Apache ServiceMix ::
Bundles :: javax.inject
 65 │ Active  │  80 │ 0.2.0   │ pax-transx-tm-api
 66 │ Active  │  80 │ 0.2.0   │ pax-transx-tm-geronimo
 67 │ Active  │  80 │ 2.2.0.v201708071007 │ Java Persistence API 2.2
 68 │ Active  │  80 │ 2.6.1   │ Apache Aries JPA
Container adapter for EclipseLink
 69 │ Active  │  80 │ 3.5.2.v201605171345 │ EclipseLink ANTLR
 70 │ Active  │  80 │ 6.0.0.v201710052159 │ EclipseLink ASM
 71 │ Active  │  80 │ 2.7.1.v20171221-bd47e8f │ EclipseLink Core
 72 │ Active  │  80 │ 2.7.1.v20171221-bd47e8f │ EclipseLink JPA
 73 │ Active  │  80 │ 2.7.1.v20171221-bd47e8f │ EclipseLink Hermes
Parser
 96 │ Active  │  80 │ 4.6.0   │ Apache XBean OSGI Bundle
Utilities
 97 │ Active  │  80 │ 4.6.0   │ Apache XBean ::
Classpath Resource Finder
135 │ Active  │  80 │ 1.9.2.1 │ Apache ServiceMix ::
Bundles :: jasypt
136 │ Active  │  80 │ 1.2.0   │ OPS4J Pax JDBC Generic
Driver Extender
137 │ Active  │  80 │ 1.2.0   │ OPS4J Pax JDBC Config
138 │ Active  │  80 │ 1.2.0   │ OPS4J Pax JDBC Pooling
Support Base
139 │ Active  │  80 │ 1.0.0.201505202023  │
org.osgi:org.osgi.service.jdbc
145 │ Active  │  80 │ 4.2.0   │ Apache Karaf :: JDBC ::
Core
149 │ Active  │  80 │ 1.2.0   │ OPS4J Pax JDBC Apache
Derby Driver Adapter
157 │ Active  │  80 │ 1.0.0.201806071126  │ Herakles Persistence API
Bundle
158 │ GracePeriod │  80 │ 1.0.0.201806071126  │ Herakles Jpa Persistence
Bundle
159 │ Active  │  80 │ 1.0.0.201806071126  │ Herakles Derby
Datasource Bundle
160 │ Active  │  80 │ 10.14.200.1828579   │ Apache Derby 10.14
karaf@root()>

and the bundle:diag result

karaf@root()> bundle:diag 158
Herakles Jpa Persistence Bundle (158)
-
Status: GracePeriod
Blueprint
07.06.18, 13:26
Missing dependencies: 
(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://aries.apache.org/xmlns/transactions/v1.1.0))
(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://aries.apache.org/xmlns/jpa/v2.0.0))
 
Declarative Services


   



--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html

RE: Unresolved dependency using blueprint transaction

[DUTERTRY Nicolas]

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

-Message d'origine-
De : ceugster [mailto:christian.eugs...@gmx.net] 
Envoyé : mercredi 6 juin 2018 21:32
À : user@karaf.apache.org
Objet : Re: Unresolved dependency using blueprint transaction

Hi JB
because I was not sure if I did feature:install of aries-blueprint and
transaction in the right order, I installed a clean version of karaf-4.2 and
then

feature:install aries-blueprint
feature:install transactions
feature:install eclipselink
feature:install my bundles

then a bundle:diag showed following:

karaf@root()> bundle:diag 75
Herakles Jpa Persistence Bundle (75)

Status: GracePeriod
Blueprint
06.06.18, 21:26
Missing dependencies: 
(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://aries.apache.org/xmlns/transactions/v2.0.0))
(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://aries.apache.org/xmlns/jpa/v2.0.0))
 

it seems even worse than before!? Do you have an idea, what could be the
solution to this?

Thank you!
Christian



--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html