unsubscribe

[Jason Pratt]

unsubscribe

unsubscribe

[Jason Pratt]

unsubscribe

unsubscribe

[Jason Pratt]

unsubscribe

karaf + java 10

[Jason Reilly]

Hi all,

What's the current state of Karaf with jdk 10?  I only ask as I tried to 
upgrade from Karaf 4.1.4/jdk8 to Karaf 4.2.0/jdk10I got the 
following error while trying to install one of my bundles that uses 
aries-blueprint:


12:25:47.326 WARN [pipe-bundle:install -s 
mvn:org.renci.canvas.canvas-dao/canvas-datasource/0.1.21-SNAPSHOT] Object to be 
destroyed is not an instance of UnwrapperedBeanHolder, type: null

12:25:47.327 ERROR [pipe-bundle:install -s 
mvn:org.renci.canvas.canvas-dao/canvas-datasource/0.1.21-SNAPSHOT] Unable to 
start blueprint container for bundle canvas-datasource/0.1.21.SNAPSHOT

org.osgi.service.blueprint.container.ComponentDefinitionException: 
java.lang.IllegalArgumentException: Invalid Java version 54

    at 
org.apache.aries.blueprint.container.ReferenceRecipe.internalCreate(ReferenceRecipe.java:141)
 ~[165:org.apache.aries.blueprint.core:1.9.0]

    at 
org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:81) 
~[165:org.apache.aries.blueprint.core:1.9.0]

    at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]

    at 
org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:90) 
~[165:org.apache.aries.blueprint.core:1.9.0]

    at 
org.apache.aries.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:810)
 ~[165:org.apache.aries.blueprint.core:1.9.0]


It's not a problem to do Karaf 4.2.0/jdk8 instead, but I thought I would 
inquire if this is expected to work.



Thanks in advance,
Jason

unsubscribe

[Jason Pratt]

unsubscribe

Re: hibernate caching

[Jason Reilly]

Another quick update...

I removed the jsr107 ehcache option & tried out the hibernate ehcache 
factory.  So, the persistence.xml file has the following:






And the dao-api/pom.xml had the following Import-Package:

org.hibernate.proxy,org.hibernate.cache.ehcache,javassist.util.proxy,*


This works, but the log has a bunch of warnings, "Could not find a 
specific ehcache configuration for cache named".  I can live with the 
warnings for now.



On 05/03/2017 03:32 PM, Jason Reilly wrote:

Quick update

Adding the following to my dao-api/pom.xml file:

org.hibernate.proxy,org.ehcache.jsr107,org.hibernate.cache.jcache,javassist.util.proxy,* 




I get the following at startup:


2017-05-03 15:21:08,067 | ERROR | pache.cxf.osgi]) | 
configadmin  | 5 - org.apache.felix.configadmin - 
1.8.14 | [org.osgi.service.cm.ManagedService, id=236, 
bundle=73/mvn:org.apache.aries.jpa/org.apache.aries.jpa.container/2.6.1]: 
Unexpected problem updating configuration org.apache.aries.jpa.canvas


javax.persistence.PersistenceException: [PersistenceUnit: canvas] 
Unable to build Hibernate SessionFactory


at 
org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.persistenceException(EntityManagerFactoryBuilderImpl.java:967) 
[246:org.hibernate.core:5.2.10.Final]


at 
org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:892) 
[246:org.hibernate.core:5.2.10.Final]


at 
org.hibernate.osgi.OsgiPersistenceProvider.createContainerEntityManagerFactory(OsgiPersistenceProvider.java:96) 
[251:org.hibernate.osgi:5.2.10.Final]


at 
org.apache.aries.jpa.container.impl.ManagedEMF.createAndPublishEMF(ManagedEMF.java:129) 
[73:org.apache.aries.jpa.container:2.6.1]


at 
org.apache.aries.jpa.container.impl.ManagedEMF.updated(ManagedEMF.java:125) 
[73:org.apache.aries.jpa.container:2.6.1]


at 
org.apache.felix.cm.impl.helper.ManagedServiceTracker.updated(ManagedServiceTracker.java:189) 
[5:org.apache.felix.configadmin:1.8.14]


at 
org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:152) 
[5:org.apache.felix.configadmin:1.8.14]


at 
org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:85) 
[5:org.apache.felix.configadmin:1.8.14]


at 
org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.provide(ConfigurationManager.java:1463) 
[5:org.apache.felix.configadmin:1.8.14]


at 
org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:1419) 
[5:org.apache.felix.configadmin:1.8.14]


at 
org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:141) 
[5:org.apache.felix.configadmin:1.8.14]


at 
org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:109) 
[5:org.apache.felix.configadmin:1.8.14]


at java.lang.Thread.run(Thread.java:745) [?:?]

Caused by: org.hibernate.service.spi.ServiceException: Unable to 
create requested service [org.hibernate.engine.spi.CacheImplementor]


at 
org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:271) 
~[?:?]


at 
org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:233) 
~[?:?]


at 
org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:210) 
~[?:?]


at 
org.hibernate.service.internal.SessionFactoryServiceRegistryImpl.getService(SessionFactoryServiceRegistryImpl.java:77) 
~[?:?]


at 
org.hibernate.internal.SessionFactoryImpl.(SessionFactoryImpl.java:240) 
~[?:?]


at 
org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:452) 
~[?:?]


at 
org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:889) 
~[?:?]


... 11 more

Caused by: javax.cache.CacheException: Failed to load the 
CachingProvider [org.ehcache.jsr107.EhcacheCachingProvider]


at 
javax.cache.Caching$CachingProviderRegistry.loadCachingProvider(Caching.java:169) 
~[?:?]


at 
javax.cache.Caching$CachingProviderRegistry.getCachingProvider(Caching.java:184) 
~[?:?]


at 
javax.cache.Caching$CachingProviderRegistry.getCachingProvider(Caching.java:156) 
~[?:?]


at javax.cache.Caching.getCachingProvider(Caching.java:66) ~[?:?]

at 
org.hibernate.cache.jcache.JCacheRegionFactory.getCachingProvider(JCacheRegionFactory.java:157) 
~[?:?]


at 
org.hibernate.cache.jcache.JCacheRegionFactory.getCacheManager(JCacheRegionFactory.java:166) 
~[?:?]


at 
org.hibernate.cache.jcache.JCacheRegionFactory.start(JCacheRegionFactory.java:68) 
~[?:?]


at 
org.hibernate.cache.spi.RegionFactory.start(RegionFactory.java:63) ~[?:?]


at org.hibernate.internal.CacheImpl.(CacheImpl.java:71) ~[?:?]

at 
org.hibernate.engine.spi.CacheInitiator.i

Re: hibernate caching

[Jason Reilly]

 
org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:210)
 ~[?:?]

at 
org.hibernate.service.internal.SessionFactoryServiceRegistryImpl.getService(SessionFactoryServiceRegistryImpl.java:77)
 ~[?:?]

at 
org.hibernate.internal.SessionFactoryImpl.(SessionFactoryImpl.java:240) 
~[?:?]

at 
org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:452)
 ~[?:?]

at 
org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:889)
 ~[?:?]

... 11 more

Caused by: java.lang.ClassNotFoundException: 
org.ehcache.jsr107.EhcacheCachingProvider

at java.net.URLClassLoader.findClass(URLClassLoader.java:381) ~[?:?]

at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[?:?]

at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) ~[?:?]

at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:?]

at 
javax.cache.Caching$CachingProviderRegistry.loadCachingProvider(Caching.java:162)
 ~[?:?]

at 
javax.cache.Caching$CachingProviderRegistry.getCachingProvider(Caching.java:184)
 ~[?:?]

at 
javax.cache.Caching$CachingProviderRegistry.getCachingProvider(Caching.java:156)
 ~[?:?]

at javax.cache.Caching.getCachingProvider(Caching.java:66) ~[?:?]



On 05/03/2017 02:01 PM, Jason Reilly wrote:

Hi all,

I tried to add caching to my persistence layer.  I added the following 
to my persistence.xml:



  value="org.hibernate.cache.jcache.JCacheRegionFactory" />


  value="org.ehcache.jsr107.EhcacheCachingProvider" />


  value="true" />


  


I added the necessary dependencies (test cases all run great), but 
this configuration doesn't seem to deploy nicely to Karaf (4.1.1).  
The exception thrown is the following:



2017-05-03 13:03:30,645 | ERROR | atures.logging]) | 
configadmin  | 5 - org.apache.felix.configadmin - 
1.8.14 | [org.osgi.service.cm.ManagedService, id=242, 
bundle=75/mvn:org.apache.aries.jpa/org.apache.aries.jpa.container/2.6.0]: 
Unexpected problem updating configuration org.apache.aries.jpa.canvas


org.hibernate.service.spi.ServiceException: Unable to create requested 
service [org.hibernate.cache.spi.RegionFactory]


at 
org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:271) 
[249:org.hibernate.core:5.2.8.Final]


at 
org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:233) 
[249:org.hibernate.core:5.2.8.Final]


at 
org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:210) 
[249:org.hibernate.core:5.2.8.Final]


at 
org.hibernate.boot.internal.MetadataBuilderImpl$MetadataBuildingOptionsImpl.(MetadataBuilderImpl.java:663) 
[249:org.hibernate.core:5.2.8.Final]


at 
org.hibernate.boot.internal.MetadataBuilderImpl.(MetadataBuilderImpl.java:127) 
[249:org.hibernate.core:5.2.8.Final]


at 
org.hibernate.boot.MetadataSources.getMetadataBuilder(MetadataSources.java:135) 
[249:org.hibernate.core:5.2.8.Final]


at 
org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.(EntityManagerFactoryBuilderImpl.java:214) 
[249:org.hibernate.core:5.2.8.Final]


at 
org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.(EntityManagerFactoryBuilderImpl.java:177) 
[249:org.hibernate.core:5.2.8.Final]


at 
org.hibernate.jpa.boot.spi.Bootstrap.getEntityManagerFactoryBuilder(Bootstrap.java:83) 
[249:org.hibernate.core:5.2.8.Final]


at 
org.hibernate.jpa.boot.spi.Bootstrap.getEntityManagerFactoryBuilder(Bootstrap.java:103) 
[249:org.hibernate.core:5.2.8.Final]


at 
org.hibernate.osgi.OsgiPersistenceProvider.createContainerEntityManagerFactory(OsgiPersistenceProvider.java:95) 
[253:org.hibernate.osgi:5.2.8.Final]


at 
org.apache.aries.jpa.container.impl.ManagedEMF.createAndPublishEMF(ManagedEMF.java:129) 
[75:org.apache.aries.jpa.container:2.6.0]


at 
org.apache.aries.jpa.container.impl.ManagedEMF.updated(ManagedEMF.java:125) 
[75:org.apache.aries.jpa.container:2.6.0]


at 
org.apache.felix.cm.impl.helper.ManagedServiceTracker.updated(ManagedServiceTracker.java:189) 
[5:org.apache.felix.configadmin:1.8.14]


at 
org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:152) 
[5:org.apache.felix.configadmin:1.8.14]


at 
org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:85) 
[5:org.apache.felix.configadmin:1.8.14]


at 
org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.provide(ConfigurationManager.java:1463) 
[5:org.apache.felix.configadmin:1.8.14]


at 
org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:1419) 
[5:o

hibernate caching

[Jason Reilly]

.8.Final   │ 249 │ org.hibernate.core

org.hibernate.cache.spi.entry   
   │ 5.2.8.Final   │ 249 │ org.hibernate.core

org.hibernate.cache.spi 
   │ 5.2.8.Final   │ 249 │ org.hibernate.core

karaf@root()> exports | grep org.hibernate.cache.jcache

org.hibernate.cache.jcache.access   
   │ 5.2.8.Final   │ 252 │ org.hibernate.jcache

org.hibernate.cache.jcache.time 
   │ 5.2.8.Final   │ 252 │ org.hibernate.jcache

org.hibernate.cache.jcache  
   │ 5.2.8.Final   │ 252 │ org.hibernate.jcache

karaf@root()> exports | grep org.ehcache.jsr107

org.ehcache.jsr107.config   
   │ 0.0.0 │ 246 │ org.ehcache.ehcache

org.ehcache.jsr107  
   │ 0.0.0 │ 246 │ org.ehcache.ehcache


Anyone get Hibernate (5.2.8.Final) working in Karaf with caching?  
Suggestions?



Thanks,

Jason

RE: Why is karaf so much easier to get working than older OSGi containers?

[Pratt, Jason]

Count me in on this

-Original Message-
From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] 
Sent: Wednesday, April 12, 2017 12:40 PM
To: user@karaf.apache.org
Subject: Re: Why is karaf so much easier to get working than older OSGi 
containers?

Hi Brad,

I would be more than happy to restart the Karaf Boot PoC. But I was feeling a 
bit alone on this ;) I started several threads on the mailing list.

I fully agree with what you said and also Serge's comments.

I will restart/update Karaf Boot during the week. If you have any idea or want 
to contribute, please let me know, I will give you access to my repo !

Thanks
Regards
JB

On 04/12/2017 08:33 PM, Ranx wrote:
> I don’t think there’s been much work on Karaf Boot lately. I hope they 
> decide to pick that up again and just go with an opinionated way of 
> doing Karaf Boot development as Spring Boot does. For example, use the 
> PAX and Camel CDI as the mechanism of bootstrap and wire up and simply 
> leave other mechanisms alone. If one wants to use blueprint or DS then 
> go for it but Karaf Boot could just ignore it. That doesn’t deprecate 
> those other technologies as far as Karaf is concerned, it just means 
> that the subset or mindset of Karaf Boot would be CDI-centric.
>
>
>
> Brad
>
>
>
> *From:*Serge Huber [mailto:shu...@jahia.com]
> *Sent:* Monday, April 10, 2017 4:13 AM
> *To:* user@karaf.apache.org
> *Subject:* Re: Why is karaf so much easier to get working than older 
> OSGi containers?
>
>
>
> I think that Karaf Boot is also important to get people started 
> quickly. Or maybe even some kind of CLI interface and container integrations.
>
>
>
> I still find that building a new project with my own custom 
> distribution is a big more work than I would like.
>
>
>
> Not to say that I don't love Karaf, I'm using it in more and more 
> projects (4 professional and 2 personal !)
>
>
>
> cheers,
>
>   Serge...
>
>
>   Serge Huber
>   CTO & Co-Founder
>
>
>   T +41 22 361 3424
>
>
>   9 route des Jeunes | 1227 Acacias | Switzerland
>
>
>   jahia.com 
>
>
>   SKYPE | LINKEDIN  | TWITTER
>    | VCARD
>   
>
>
>
>
>
>   > JOIN OUR COMMUNITY  to evaluate, get trained and 
> to discover why Jahia is
>   a leading User Experience Platform (UXP) for Digital Transformation.
>
>
>
> On Sun, Apr 9, 2017 at 8:50 AM, Jean-Baptiste Onofré  > wrote:
>
> Hi Steinar,
>
> Great e-mail !
>
> I think Karaf just works thanks to combination of what you said: features
> and resolver, prepackage features, convenient functionalities (shell, 
> ACL, etc).
>
> I still think we should improve the dev experience providing samples in 
> the
> distribution (as started).
>
> Regards
> JB
>
>
>
> On 04/09/2017 08:37 AM, Steinar Bang wrote:
>
> I first encountered OSGi in 2006.  The place I worked at that time had
> (prior to my hiring) selected OSGi as the platform for server side
> components.
>
> The team I worked on extended this into the GUI space by creating an
> eclipse GEF-based IDE for data flows in the server system, where we
> integrated the server components into the eclipse instance for
> debugging.
>
> At that time it was a very promising technology, it was defined in a
> standard document that was actually readable, and it had (at that 
> time,
> if memory serves me right) one complete free software implementation
> (eclipse equinox), two commercial implementations, and one free
> implementation (apache felix) just getting started.
>
> For my own part I was attracted to the lego building block 
> possibilities
> of OSGi, and the fact that we were able to get the server components
> running inside eclipse and talking to eclipse GUI components by
> using OSGi services (even though what the server side components and
> eclipse used on top of OSGi services was very different).
>
> But... the problem with OSGi both then, and when I started looking at 
> it
> back in 2013, was the practicalities in getting all bundle 
> dependencies
> satisfied, and finding, and working around bundle version issues.
>
> In contrast to this, karaf has just worked for me (I took the plunge
> into learning karaf in the autumn of 2016).
>
> Or let me qualify that a little: since I started creating features for
> my own bundles, as a part of the maven build, karaf has just worked 
> for
> me.
>
> So what I'm wondering, is: why is karaf so easy when everything before
> has been so hard?
>
> Is it because there is something magical in the feature resolution,
> compared to other way of starting OSGi runtimes?
>
> Or is it just that

Re: hibernate 5.2.6 & karaf 4.1.0

[Jason Reilly]

I saw the following and installed it in place of the default 'jpa' feature.

http://repo1.maven.org/maven2/org/apache/aries/jpa/jpa-features/2.6.0/jpa-features-2.6.0-features.xml


I don't know if they work yet, but, at least my persistence bundles are 
now started.



Thanks & keep up the great work.

Regards,
Jason





On 02/28/2017 09:07 AM, Jean-Baptiste Onofré wrote:

Ok,

we have multiple JPA API installed (Geronimo and Hibernate API). Once 
in 2.0, the other in 2.1.


It's what we fixed with Christian. I think your issue could be related 
as it might not cast on the right persistence API version.


Regards
JB

On 02/28/2017 03:04 PM, Jason Reilly wrote:

137 │ Active   │  80 │ 1.1   │ Apache Geronimo JSR-317
JPA 2.0 Spec API

238 │ Active   │  80 │ 1.0.0.Final   │ hibernate-jpa-2.1-api

261 │ Active   │  80 │ 1.0.0.201505202024│
org.osgi:org.osgi.service.jpa

Re: hibernate 5.2.6 & karaf 4.1.0

[Jason Reilly]

karaf@root()> la|grep -i jpa

 63 │ Active   │  80 │ 2.5.0 │ Apache Aries JPA Container API

 64 │ Active   │  80 │ 2.5.0 │ Apache Aries JPA blueprint

 65 │ Active   │  80 │ 2.5.0 │ Apache Aries JPA container

 66 │ Active   │  80 │ 2.5.0 │ Apache Aries JPA support

137 │ Active   │  80 │ 1.1   │ Apache Geronimo JSR-317 JPA 2.0 
Spec API

238 │ Active   │  80 │ 1.0.0.Final   │ hibernate-jpa-2.1-api

261 │ Active   │  80 │ 1.0.0.201505202024│ org.osgi:org.osgi.service.jpa



On 02/28/2017 09:03 AM, Jean-Baptiste Onofré wrote:

Hi,

can you do:

la|grep -i jpa

Thanks !
Regards
JB

On 02/28/2017 03:01 PM, Jason Reilly wrote:

karaf@root()> feature:list | grep jpa
deltaspike-jpa  │ 1.2.1│  │
Uninstalled │ org.ops4j.pax.cdi-0.12.0  │ Apache Deltaspike jpa
support
deltaspike-jpa  │ 1.4.2│  │
Uninstalled │ org.ops4j.pax.cdi-1.0.0.RC2   │ Apache Deltaspike jpa
support
jpa │ 2.5.0│ x│
Started │ enterprise-4.1.0  │ OSGi Persistence
Container
openjpa │ 2.4.1│  │
Uninstalled │ enterprise-4.1.0  │ Apache OpenJPA 2.4.x
persistence engine support
karaf@root()> feature:list | grep transaction
transaction-api │ 1.2.0│ x│
Started │ enterprise-4.1.0  │
transaction-manager-geronimo│ 1.3.2│  │
Started │ enterprise-4.1.0  │ Geronimo Transaction
Manager
transaction-manager-narayana│ 5.5.0.Final  │  │
Uninstalled │ enterprise-4.1.0  │ Narayana Transaction
Manager
transaction │ 2.0.0│ x│
Started │ enterprise-4.1.0  │ OSGi Transaction 
Manager



On 02/28/2017 08:59 AM, Jean-Baptiste Onofré wrote:

Hi Jason,

Can you check the jpa API bundle installed ?

Christian and I investigated an issue about JPA API installed last
week, it could be related.

Regards
JB

On 02/28/2017 02:58 PM, Jason Reilly wrote:

Hi all,

Has anyone tried this combination yet?  I am giving it a whirl & am
getting the following exception when I add my persistence bundle:


Bundle org.apache.aries.jpa.container [65] EventDispatcher: Error 
during

dispatch. (java.lang.ClassCastException:
org.hibernate.osgi.OsgiPersistenceProvider cannot be cast to
javax.persistence.spi.PersistenceProvider)
java.lang.ClassCastException: 
org.hibernate.osgi.OsgiPersistenceProvider

cannot be cast to javax.persistence.spi.PersistenceProvider
at
org.apache.aries.jpa.container.impl.PersistenceProviderTracker.addingService(PersistenceProviderTracker.java:84) 



[65:org.apache.aries.jpa.container:2.5.0]
at
org.apache.aries.jpa.container.impl.PersistenceProviderTracker.addingService(PersistenceProviderTracker.java:44) 



[65:org.apache.aries.jpa.container:2.5.0]
at
org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941) 



[?:?]
.

08:46:48.925 [FelixDispatchQueue] ERROR 
org.apache.aries.jpa.container -

FrameworkEvent ERROR - org.apache.aries.jpa.container

java.lang.ClassCastException: 
org.hibernate.osgi.OsgiPersistenceProvider

cannot be cast to javax.persistence.spi.PersistenceProvider

at
org.apache.aries.jpa.container.impl.PersistenceProviderTracker.addingService(PersistenceProviderTracker.java:84) 



[65:org.apache.aries.jpa.container:2.5.0]

at
org.apache.aries.jpa.container.impl.PersistenceProviderTracker.addingService(PersistenceProviderTracker.java:44) 



[65:org.apache.aries.jpa.container:2.5.0]


I have tried using Hibernate 5.2.8.Final which issues the same
exception.


Regards,

Jason

Re: hibernate 5.2.6 & karaf 4.1.0

[Jason Reilly]

karaf@root()> feature:list | grep jpa
deltaspike-jpa  │ 1.2.1│  │ Uninstalled │ 
org.ops4j.pax.cdi-0.12.0  │ Apache Deltaspike jpa support
deltaspike-jpa  │ 1.4.2│  │ Uninstalled │ 
org.ops4j.pax.cdi-1.0.0.RC2   │ Apache Deltaspike jpa support
jpa │ 2.5.0│ x│ Started │ 
enterprise-4.1.0  │ OSGi Persistence Container
openjpa │ 2.4.1│  │ Uninstalled │ 
enterprise-4.1.0  │ Apache OpenJPA 2.4.x persistence engine 
support
karaf@root()> feature:list | grep transaction
transaction-api │ 1.2.0│ x│ Started │ 
enterprise-4.1.0  │
transaction-manager-geronimo│ 1.3.2│  │ Started │ 
enterprise-4.1.0  │ Geronimo Transaction Manager
transaction-manager-narayana│ 5.5.0.Final  │  │ Uninstalled │ 
enterprise-4.1.0  │ Narayana Transaction Manager
transaction │ 2.0.0│ x│ Started │ 
enterprise-4.1.0  │ OSGi Transaction Manager


On 02/28/2017 08:59 AM, Jean-Baptiste Onofré wrote:

Hi Jason,

Can you check the jpa API bundle installed ?

Christian and I investigated an issue about JPA API installed last 
week, it could be related.


Regards
JB

On 02/28/2017 02:58 PM, Jason Reilly wrote:

Hi all,

Has anyone tried this combination yet?  I am giving it a whirl & am
getting the following exception when I add my persistence bundle:


Bundle org.apache.aries.jpa.container [65] EventDispatcher: Error during
dispatch. (java.lang.ClassCastException:
org.hibernate.osgi.OsgiPersistenceProvider cannot be cast to
javax.persistence.spi.PersistenceProvider)
java.lang.ClassCastException: org.hibernate.osgi.OsgiPersistenceProvider
cannot be cast to javax.persistence.spi.PersistenceProvider
at
org.apache.aries.jpa.container.impl.PersistenceProviderTracker.addingService(PersistenceProviderTracker.java:84) 


[65:org.apache.aries.jpa.container:2.5.0]
at
org.apache.aries.jpa.container.impl.PersistenceProviderTracker.addingService(PersistenceProviderTracker.java:44) 


[65:org.apache.aries.jpa.container:2.5.0]
at
org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941) 


[?:?]
.

08:46:48.925 [FelixDispatchQueue] ERROR org.apache.aries.jpa.container -
FrameworkEvent ERROR - org.apache.aries.jpa.container

java.lang.ClassCastException: org.hibernate.osgi.OsgiPersistenceProvider
cannot be cast to javax.persistence.spi.PersistenceProvider

at
org.apache.aries.jpa.container.impl.PersistenceProviderTracker.addingService(PersistenceProviderTracker.java:84) 


[65:org.apache.aries.jpa.container:2.5.0]

at
org.apache.aries.jpa.container.impl.PersistenceProviderTracker.addingService(PersistenceProviderTracker.java:44) 


[65:org.apache.aries.jpa.container:2.5.0]


I have tried using Hibernate 5.2.8.Final which issues the same 
exception.



Regards,

Jason

hibernate 5.2.6 & karaf 4.1.0

[Jason Reilly]

Hi all,

Has anyone tried this combination yet?  I am giving it a whirl & am 
getting the following exception when I add my persistence bundle:



Bundle org.apache.aries.jpa.container [65] EventDispatcher: Error during 
dispatch. (java.lang.ClassCastException: 
org.hibernate.osgi.OsgiPersistenceProvider cannot be cast to 
javax.persistence.spi.PersistenceProvider)
java.lang.ClassCastException: org.hibernate.osgi.OsgiPersistenceProvider cannot 
be cast to javax.persistence.spi.PersistenceProvider
at 
org.apache.aries.jpa.container.impl.PersistenceProviderTracker.addingService(PersistenceProviderTracker.java:84)
 [65:org.apache.aries.jpa.container:2.5.0]
at 
org.apache.aries.jpa.container.impl.PersistenceProviderTracker.addingService(PersistenceProviderTracker.java:44)
 [65:org.apache.aries.jpa.container:2.5.0]
at 
org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941)
 [?:?]
.

08:46:48.925 [FelixDispatchQueue] ERROR org.apache.aries.jpa.container - 
FrameworkEvent ERROR - org.apache.aries.jpa.container

java.lang.ClassCastException: org.hibernate.osgi.OsgiPersistenceProvider cannot 
be cast to javax.persistence.spi.PersistenceProvider

at 
org.apache.aries.jpa.container.impl.PersistenceProviderTracker.addingService(PersistenceProviderTracker.java:84)
 [65:org.apache.aries.jpa.container:2.5.0]

at 
org.apache.aries.jpa.container.impl.PersistenceProviderTracker.addingService(PersistenceProviderTracker.java:44)
 [65:org.apache.aries.jpa.container:2.5.0]


I have tried using Hibernate 5.2.8.Final which issues the same exception.


Regards,

Jason

RE: Opinionated...

[Pratt, Jason]

Brad are you looking at doing some sort of RxJava here?

From: Brad Johnson [mailto:bradj...@redhat.com]
Sent: Saturday, January 14, 2017 5:20 AM
To: user@karaf.apache.org
Subject: RE: Opinionated...

Scott,

It’s funny that you mention OSGi Remote Services as that was sort of in the 
back of my mind.   I think I recall Christian said he was working on a Remote 
Services implementation as well. But I don’t know enough about it yet to 
include it in the discussion.  I suspect what I’m going to do is set up a 
GitHub project with a basic project and then a set of appliances for a variety 
of enterprise integration purposes.  That baseline has to be in place before 
lower levels can be addressed

But I do think that a communications abstraction is going to be necessary.  A 
next generation of communications pipes should abstract protocols away from the 
OSGi programmer. Or as the great and powerful Oz put it “never mind the little 
man behind the curtain”.

When writing code in a Camel route in an OSGi bundle the programmer should 
either be thinking about using a named request/response pipe or an event pipe – 
IPs, ports, transports, and so on should happen via straight configuration 
files, parsed, configured and then registered as services to be picked up in 
bundles.  There isn’t anything that stands in the way of doing that now other 
than a little elbow grease.

So I’ll definitely give the Remote Services a deeper look.


From: Scott Lewis [mailto:sle...@composent.com]
Sent: Friday, January 13, 2017 7:16 PM
To: user@karaf.apache.org
Subject: Re: Opinionated...

Hi Brad,

You might be interested in the OSGi Remote Services specification...which 
mentions the distributed computing fallacies in the introduction.   It's 
chapter 100 in the enterprise spec [1].

A big part of Remote Services is the ability to use OSGi service dynamics to 
'deal-with' distributed systems issues like partial failure (i.e. network is 
reliable).   For example, one way to represent the failure of a remote service 
would be to make the local service proxy go away.  Note that with OSGi service 
dynamics and (e.g.) DS, the consequences of such a thing on dependent services 
can be easily handled without introducing special mechanism.

IMO another advantage of Remote Services is that the OSGi service contract/impl 
separation also decouples the service from the distribution system.   This 
allows the service designer to create remote services (API and impl) that are 
independent of the distribution system's serialization format (e.g json, xml, 
obj serialization, etc) and comm approach/protocol (e.g. http/rest, pub/sub 
messaging, mqtt, tcp, etc).   As an example of this, I've created three 
Karaf-hosted remote services that allow remote monitoring and management of 
Karaf bundles, services, and install/uninstall of Karaf features...and these 
services can be accessed from remote Eclipse via an mqtt broker, or via 
server-based tcp, or via other distribution systems without changing the 
service APIs or implementation.

Scott

[1] https://www.osgi.org/developer/specifications/
[2] https://wiki.eclipse.org/Karaf_Remote_Management_with_Eclipse

On 1/13/2017 11:19 AM, Brad Johnson wrote:
That is certainly the sort of library that could be used as a standard. Get an 
agreement on the standard OSGi service interface and then use it and others for 
that implementation.  Which brings up a good question and issue.  There would 
have to be some set of standardized messages and exception types.  The 
CiruitBreaker example throws a CircuitBreakingException (naturally enough).  If 
there’s an ErrorHandlerService it would have to know the standard set of 
exceptions that could be expected or, at least, a set of parent classes.  Since 
CircuitBreakingException is a relatively simple class it would be perfect for a 
default ErrorHandlerService to catch for that class of exceptions.

Obviously there will have to be some head scratching and chin rubbing about how 
the pieces fit together exactly.  The CircuitBreakerService (and the others 
too) could also be more like container classes that listen and pick up 
CircuitBreakerListenerService instances.  So one listener might just log the 
circuit breaker exception.  But you might instantiate an 
SMTPCircuitBreakerNotifcationService that implements the 
CircuitBreakerListenerService and fires off an email to an admin email address 
if the breaker is tripped.

That CircuitBreakerService might also be picked by the Kontainer instance which 
listens for on/off control events from the outside world.  Some thinking to do 
there but they are tractable problems with services and events.

The main services like CircuitBreakerService and ThrottlerService might 
register themselves as providers with the ErrorHandlerService which would catch 
the types of exceptions they throw.  It in turn could listen for custom 
ExceptionHandlerListener that listen for and handle specific exception

Re: Levels of Containerization - focus on Docker and Karaf

[Jason Pratt]

i'd like to see it please

jason

On Tue, Jan 17, 2017 at 5:26 AM, Jean-Baptiste Onofré 
wrote:

> It makes sense.
>
> The only "lacking" part is about global service registry, API gateway and
> governance.
>
> I talked a bit with Guillaume some month ago and with Krystof during last
> ApacheCon in Sevilla: I think it would be great to have something around
> that as part of ServiceMix.
>
> I prepared a document describing this that I can share with people
> interested.
>
> Regards
> JB
>
> On 01/17/2017 12:19 AM, souciance wrote:
>
>> Someone may have mentioned this before but they way we do build our
>> services
>> is building karaf inside a docker container.
>>
>> We also deploy each Karaf instance which contains multiple Camel projects
>> inside separate containers. So we have a one to one mapping between karaf
>> instance and container. This is mainly because we don't want a container
>> going down affecting more than one instance.
>>
>> Off course if our instances increase we may later have to consolidate but
>> so
>> far it was has worked. We also create our Karaf instances using custom
>> distributions and then add them using dockerfiles. The main problem has
>> been
>> to get the distribution working correctly.
>>
>>
>>
>> --
>> View this message in context: http://karaf.922171.n3.nabble.
>> com/Levels-of-Containerization-focus-on-Docker-and-Karaf-tp4
>> 049162p4049260.html
>> Sent from the Karaf - User mailing list archive at Nabble.com.
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: karaf boot

[Jason Pratt]

Do you have any examples on github for this?

Sent from my iPad

> On Jan 11, 2017, at 4:38 PM, Nick Baker  wrote:
> 
> We're deploying into Kubernetes (OpenShift), but it could be Mesos/Marathon, 
> Docker Swarm, etc. the only important thing is for each pod to know where to 
> find zookeeper.
> 
> -Nick
> From: jason.pr...@windriver.com
> Sent: January 11, 2017 7:19 PM
> To: user@karaf.apache.org
> Reply-to: user@karaf.apache.org
> Subject: RE: karaf boot
> 
> This sounds very interesting. Would the Dockers then be deployed similar to 
> VertX?
>  
> From: Nick Baker [mailto:nba...@pentaho.com] 
> Sent: Wednesday, January 11, 2017 11:31 AM
> To: user@karaf.apache.org
> Subject: Re: karaf boot
>  
> Some background on what we've been playing with may be of use.
>  
> We've worked on a Kubenetes/OpenShift deployment of micro-service Karaf 
> instances (pods). Each pod simply runs a plain Karaf preconfigured with 
> Remote Service support (ECF) and select features of our own design.
>  
> This implementation leverages the OpenShift Source-to-image feature which 
> transforms a simple Karaf assembly template checked into a Git Repository 
> into a Maven Karaf assembly, which is then run to produce a Docker Image 
> containing the Karaf assembly. The Fabric8 team has done great work here and 
> we used their S2I image as inspiration for our own.
>  
>  
> Templated Assembly
> I really like this templated assembly approach. We have a single 
> configuration file specifying which features are to be installed, optionally 
> supplying new Feature repository URLs, and environment variables. You can 
> also supply extra CFG files and even artifacts to be placed in the /deploy 
> directory.
>  
> One aspect about containerized deployments and microservice practices to 
> consider is how they treat applications as static immutable images. You don't 
> modify the capabilities or even configuration of running instances. Indeed 
> instances themselves are not to be manipulated directly as the container 
> environment will start/stop and scale out the base image as needed. Rather if 
> you want to extend the capabilities or change configuration, you would create 
> a new image or new version of an existing one and propagate that out to the 
> cluster. 
>  
> That said one of the goals for our application is the ability to deploy a 
> small footprint instance and have it dynamically provision capabilities 
> (features) as needed by the incoming workload. These would seem to run 
> counter to the trend of static instances, but I disagree as the scope of what 
> can be dynamically provisioned is controlled. Each of these runtime features 
> contributes to an existing one -plugins to an existing capability.
>  
> TLDR: Support easy assemblies from a very simplified configuration. I'd 
> probably introduce a command-line program to invoke the build and a maven 
> plugin.
>  
>  
> Run my template
> Building off templated assemblies would be simple "run" support from the same 
> configuration. Another command for the command-line program, maven plugin. 
> Put everything in java.io.tmpdir, who cares.
>  
>  
> Run Programatically
> Another item I've wanted is a better Karaf Main class. Really, I would just 
> like to use PAX-Exam as a Runner. I know... it originated from pax-runner. 
> Something simple. Specify Karaf version, features, config, setup System 
> Bundle packages, run. I guess if this was done it could be used in concert 
> with the build template to support the run-from-template above. 
>  
>  
> Health Checks
> We had to develop some custom health check code to ensure that all features 
> and blueprint containers successfully start. Legacy portions of our 
> application need to wait for Karaf to be fully realized before continuing 
> execution. This was pretty important to our embedded Karaf usage, but that's 
> certainly rare. Regardless, Health Checks are vital to microservice / cloud 
> deployments. I recently found that the Fabric8 team pretty much already has 
> this, and it's just about exactly what we developed  This needs to be 
> documented for others to find. 
>  
>  
> Boot Features 
> Boot Feature support in the assembly plugin is a Huge benefit for fast 
> lightweight Karaf instances. This would clearly be the preferred 
> configuration for a Nano-like distribution (shout-out to our Virgo brothers). 
> Unfortunately, I've had varying success moving our assemblies from 
> startupFeatures to bootFeatures. It may have to do with our custom deployers. 
> Honestly I haven't looked into it too deeply.
>  
>  
> Easy Web Interface
> Hawtio is nice, but can be a bit overwhelming. An easy interface, especially 
> for those new to OSGI/Karaf would go a long way. 
>  
>  
> I've reached-out to our OSGI guys here for their thoughts and will post them 
> here as they come in.
>  
> -Nick Baker
> From: Christian Schneider  on behalf of Christian 
> Schneider 
> Sent: Wednesday, January 11, 2017 9:51:56 AM
> To: use

RE: karaf boot

[Pratt, Jason]

This sounds very interesting. Would the Dockers then be deployed similar to 
VertX?

From: Nick Baker [mailto:nba...@pentaho.com]
Sent: Wednesday, January 11, 2017 11:31 AM
To: user@karaf.apache.org
Subject: Re: karaf boot

Some background on what we've been playing with may be of use.

We've worked on a Kubenetes/OpenShift deployment of micro-service Karaf 
instances (pods). Each pod simply runs a plain Karaf preconfigured with Remote 
Service support (ECF) and select features of our own design.

This implementation leverages the OpenShift Source-to-image feature which 
transforms a simple Karaf assembly template checked into a Git Repository into 
a Maven Karaf assembly, which is then run to produce a Docker Image containing 
the Karaf assembly. The Fabric8 team has done great work here and we used their 
S2I image as inspiration for our own.


Templated Assembly
I really like this templated assembly approach. We have a single configuration 
file specifying which features are to be installed, optionally supplying new 
Feature repository URLs, and environment variables. You can also supply extra 
CFG files and even artifacts to be placed in the /deploy directory.

One aspect about containerized deployments and microservice practices to 
consider is how they treat applications as static immutable images. You don't 
modify the capabilities or even configuration of running instances. Indeed 
instances themselves are not to be manipulated directly as the container 
environment will start/stop and scale out the base image as needed. Rather if 
you want to extend the capabilities or change configuration, you would create a 
new image or new version of an existing one and propagate that out to the 
cluster.

That said one of the goals for our application is the ability to deploy a small 
footprint instance and have it dynamically provision capabilities (features) as 
needed by the incoming workload. These would seem to run counter to the trend 
of static instances, but I disagree as the scope of what can be dynamically 
provisioned is controlled. Each of these runtime features contributes to an 
existing one -plugins to an existing capability.

TLDR: Support easy assemblies from a very simplified configuration. I'd 
probably introduce a command-line program to invoke the build and a maven 
plugin.


Run my template
Building off templated assemblies would be simple "run" support from the same 
configuration. Another command for the command-line program, maven plugin. Put 
everything in java.io.tmpdir, who cares.


Run Programatically
Another item I've wanted is a better Karaf Main class. Really, I would just 
like to use PAX-Exam as a Runner. I know... it originated from pax-runner. 
Something simple. Specify Karaf version, features, config, setup System Bundle 
packages, run. I guess if this was done it could be used in concert with the 
build template to support the run-from-template above.


Health Checks
We had to develop some custom health check code to ensure that all features and 
blueprint containers successfully start. Legacy portions of our application 
need to wait for Karaf to be fully realized before continuing execution. This 
was pretty important to our embedded Karaf usage, but that's certainly rare. 
Regardless, Health Checks are vital to microservice / cloud deployments. I 
recently found that the Fabric8 team pretty much already has this, and it's 
just about exactly what we developed [☹]  This needs to be documented for 
others to find.


Boot Features
Boot Feature support in the assembly plugin is a Huge benefit for fast 
lightweight Karaf instances. This would clearly be the preferred configuration 
for a Nano-like distribution (shout-out to our Virgo brothers). Unfortunately, 
I've had varying success moving our assemblies from startupFeatures to 
bootFeatures. It may have to do with our custom deployers. Honestly I haven't 
looked into it too deeply.


Easy Web Interface
Hawtio is nice, but can be a bit overwhelming. An easy interface, especially 
for those new to OSGI/Karaf would go a long way.


I've reached-out to our OSGI guys here for their thoughts and will post them 
here as they come in.

-Nick Baker

From: Christian Schneider 
mailto:cschneider...@gmail.com>> on behalf of 
Christian Schneider mailto:ch...@die-schneider.net>>
Sent: Wednesday, January 11, 2017 9:51:56 AM
To: user@karaf.apache.org
Subject: Re: karaf boot

Sounds like you have a good case to validate karaf boot on.

Can you explain how you create your deployments now and what you are missing in 
current karaf? Until now we only discussed internally about the scope and 
requirements of karaf boot. It would be very valuable to get some input from a 
real world case.

Christian

On 11.01.2017 13:41, Nick Baker wrote:
We'd be interested in this as well. Beginning to move toward Microservices 
deployments + Remote Services for interop. I'll have a look at your b

Re: Karaf IoT

[Jason Pratt]

well please keep me in mind when you do sort something out. i am designing
a project now and was looking at both kura and openhab for it

On Wed, Jan 4, 2017 at 12:53 PM, Łukasz Dywicki  wrote:

> I am OpenHab (OH) 2 user and I I must say that whole PDE thing is
> redundant from my Karaf (as a platform) point of view. But this all comes
> from past of project which was launched with Tycho and PDE since early
> days. There are multiple entities involved in project and it is not an easy
> task to redefine how things should be built.
>
> Initial apis of OH were quite simple and didn’t require anything strictly
> related to physical thing. Starting form OH2 and extraction of Eclipse
> SmartHome there is a seperation of concerns. OH2 bindings define Bridge and
> Things connected over it and may have Channels associated with every of
> these. At this stage it is lowest common denominator. There is no higher
> level APIs for representing pumps, boilers or sensors or alarms but from
> other hand OH is not a SCADA platform. Maybe at some point there will be
> further generalization of code which will allow bindings to gain some
> benefits? Many of bindings is pure software integration with vendor bridges
> having very little or no hardware involved at all which makes it easier to
> develop.
>
> I haven’t played with Kura so far because I didn’t need such low level
> library, but even if I would need something such that I would rather go for
> dedicated library handling specific use case instead of Kura which brings
> too much.
>
> Kind regards,
> Lukasz
> --
> Apache Karaf Committer & PMC
> Twitter: @ldywicki
> Blog: http://dywicki.pl
> Code-House - http://code-house.org
>
>
> > Wiadomość napisana przez chris.g...@kiffer.ltd.uk w dniu 2 sty 2017, o
> godz. 19:56:
> >
> > I share most of Brad's concerns; at first I was very interested in
> OpenHAB
> > but after playing with it for a bit I began to think about designing a
> new
> > service layer and then seeing if I could fit the OpenHAB native libraries
> > to it.
> >
> > OpenHAB corroborates my "PDE considered harmful" theory; it must be
> > possible to use OSGi idioms effectively while developing in Eclipse PDE,
> > but it doesn't seem to happen in practice.
> >
> > So Brad, I am right with you and I would like to help - but I am
> seriously
> > short of time at the moment :-(
> >
> >
> >
> >
>
>

Re: Karaf IoT

[Jason Pratt]

scott/brad do you guys have a repo setup for this project?

On Wed, Jan 4, 2017 at 9:39 AM, Brad Red Hat  wrote:

> I'll certainly look at that a bit more. My concerns about Kura project have
> as much to do with the project's level of abstraction and I can bring it up
> there.   I did ask about their intentions with service interfaces.  As I've
> dug into it deeper and thought about "the vision thing", to quote a US
> president, I laid out some of those thoughts.
>
> https://enjekt.org/2017/01/04/iot-and-the-abstraction-of-things/
>
> Because it is an Eclipse project I wasn't sure that they'd be interested in
> Karaf/Felix but can check. I've heard that they have, in fact, opened a
> Jira
> ticket about it. So they may be interested.
>
> It isn't just about a Karaf implementation although it is certainly about
> that as well. I'm also concerned about the intermediary libraries/services
> that abstract developers away from low level details of pin outs in order
> to
> make application code portable.
>
> Obviously the intermediate level concerns really don't belong with Kura or
> Karaf so I won't discuss those here.  Suffice it to say I'd like to see
> that
> intermediate set of libraries become a "sticky" place where developers and
> sensor/actuator manufacturers go to add new high level device specific
> bundles for use in applications.
>
> Brad
>
>
> -Original Message-
> From: Scott Lewis [mailto:sle...@composent.com]
> Sent: Tuesday, January 3, 2017 9:33 PM
> To: user@karaf.apache.org
> Subject: Re: Karaf IoT
>
> On 1/2/2017 11:35 AM, Brad Red Hat wrote:
> > I certainly understand the "short of time" problem. It just happens
> > that I have a bit of a window right now and would like to get into it a
> bit deeper.
> >
> >
> > Whether a Karaf/PAX/Felix implementation is more appropriate under the
> > aegis of Kura or as a separate project that leverages the Kura driver
> > bundles is hard to say.  I guess that would depend on a couple of things.
> >
> > 1. How amenable they are to a more top down approach that starts with
> > OSGi service mechanics and drives down to meet the driver bundles?
> > 2. Does an Eclipse foundation project have any interest in an Karaf
> > branch project?
>
> The ECF project would be interested in such an effort [1].  We have
> been/are
> distributing our impl of the OSGi Remote Services/RSA specs [2] as Karaf
> features [3] and have recently been exploring using remote services for
> Karaf management [4].
>
> Also, in my interaction with some of the Kura committers it's become clear
> that they are doing some prototyping of running Kura services on
> Karaf [5].   I don't know whether they have release plans around that
> work, but I know that it has been going on.   It might be useful to
> convey to them directly what your desires/criticisms are, and perhaps
> contribute to that work.
>
> Scott
>
> [1] http://www.eclipse.org/ecf
> [2]
> https://wiki.eclipse.org/Eclipse_Communication_
> Framework_Project#OSGi_Remote
> _Services
> [3] https://wiki.eclipse.org/EIG:Install_into_Apache_Karaf
> [4] https://wiki.eclipse.org/Karaf_Remote_Management_with_Eclipse
> [5] https://dev.eclipse.org/mhonarc/lists/kura-dev/
>
>
>

Re: complete documentation for features.xml

[Jason Pratt]

is the "new" dev guide online now?

On Wed, Dec 7, 2016 at 7:19 AM, Jean-Baptiste Onofré 
wrote:

> Hi Milen,
>
> I have something like this in the "new" dev guide.
>
> Regards
> JB
>
> On 12/06/2016 07:14 PM, Milen Dyankov wrote:
>
>> Hi,
>>
>> is there any documentation that explains features.xml in details?
>> Particularly things like
>>
>>  - conditional features
>>  - prerequisite and dependency bundles
>>  - requirements and capabilities of features
>>  - libraries
>>  - repository and resource-repository
>>
>> I can find bits and pieces here and there (documentation, mailing lists,
>> JIRA) but it seams there is no one place to explain it all. Some of them
>> are completely mysterious unless one is willing to spend hours studying
>> the source code.
>>
>> Best,
>> Milen
>>
>>
>> --
>> http://about.me/milen
>>
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

RE: Apache Shiro in Karaf

[Pratt, Jason]

I ran into the same issue and eventually gave up using Shiro

From: bengt.rode...@gmail.com [mailto:bengt.rode...@gmail.com] On Behalf Of 
Bengt Rodehav
Sent: Sunday, November 06, 2016 11:57 PM
To: user@karaf.apache.org
Subject: Re: Apache Shiro in Karaf

It seems like the webconsole is what causes me problems. If I install the 
"webconsole" feature, then I'm prompted for basic authentiction when I use the 
anonymous filter in Shiro. If I do not install the "webconsole" feature, then 
this doesn't happen. It seems like the webconsole installs some filter that 
will kick in when I use anonymous filter.

Anyone has an idea about this?

I guess as a workaround I'll have to skip the webconsole. Normally I would like 
it installed though since it is very useful.

/Bengt

2016-11-07 8:40 GMT+01:00 Bengt Rodehav 
mailto:be...@rodehav.com>>:
Thanks for your reply Steinar,

I think the difference is that you don't use the anonymous filter (keyword 
"anon" in shiro.ini). I need to use that on a couple of pages that need to be 
accessible by anyone without having to login.

What happens if you try using "anon"? Will Karaf require basic authentication?

Note also that I have the Karaf web console installed. I think it might 
interfere with this.

/Bengt

2016-11-04 17:27 GMT+01:00 Steinar Bang mailto:s...@dod.no>>:
> Bengt Rodehav mailto:be...@rodehav.com>>:

> It seems that if I comment away the following line in etc/system.properties
> then the basic authentication goes away:

> *karaf.local.roles = admin,manager,viewer,systembundles*

> Not sure how this works. Would appreciate if someone could explain.

Except for the fact that one of my karaf installations is failing
mysteriously I have successfully used shiro basic authentication in
karaf.

The changes were:
 1. Added the ShiroFilter to the web.xml of my webapp
 
https://github.com/steinarb/ukelonn/blob/using-primefaces/ukelonn.bundle/src/main/webapp/WEB-INF/web.xml
 2. Added a shiro.ini file to the webapp
 
https://github.com/steinarb/ukelonn/blob/using-primefaces/ukelonn.bundle/src/main/webapp/WEB-INF/shiro.ini
 3. Added a custom realm (maybe I can replace this by the JDBC realm...?
But I was trying out stuff and learning as I created it)
  
https://github.com/steinarb/ukelonn/blob/using-primefaces/ukelonn.bundle/src/main/java/no/priv/bang/ukelonn/impl/UkelonnRealm.java
 4. Added a redirection in the main JSF page redirecting the admins to a
different page (that's the preRenderView  tag)
  
https://github.com/steinarb/ukelonn/blob/using-primefaces/ukelonn.bundle/src/main/webapp/ukelonn.xhtml
 5. Added a redirect method to the bean serving the main JSF page
 
https://github.com/steinarb/ukelonn/blob/using-primefaces/ukelonn.bundle/src/main/java/no/priv/bang/ukelonn/impl/UkelonnController.java
 6. Pulled in shiro-core and shiro-web as runtime dependencies
 
https://github.com/steinarb/ukelonn/blob/using-primefaces/ukelonn.karaf/ukelonn/pom.xml

And that was it, basically.

I basically just followed the directions I found here, and adapted them
to a pax-web setting:
 http://balusc.omnifaces.org/2013/01/apache-shiro-is-it-ready-for-java-ee-6.html

HELP - Jetty CORS error

[Pratt, Jason]

Hi Everyone - I really need some help here with a CORS error. I've followed 
http://www.eclipse.org/jetty/documentation/current/cross-origin-filter.html and 
http://chstrongjavablog.blogspot.com/2013/04/enabling-cors-for-jetty.html for 
reference.

I have in my POM:

org.eclipse.jetty
 jetty-servlets
 9.2.10.v20150310


Which is pulling the jar into the war files /lib directory. However, when the 
WAR file is loaded karaf says it cannot find the CORS filter class. I am at a 
real loss here and cannot explain why this is happening. Any recommendations 
would be great! Here are some additional details

Karaf: 4.0.4
Jetty:
Version

9.2.14.v20151106

Bundle Location

mvn:org.eclipse.jetty/jetty-servlet/9.2.14.v20151106

Pax-web: 4.2.4

Error:
2016-10-25 21:02:25,819 | ERROR | ool-117-thread-2 | RegisterWebAppVisitorWC
  | 132 - org.ops4j.pax.web.pax-web-extender-war - 4.2.4 | Registration 
exception. Skipping.
java.lang.ClassNotFoundException: org.eclipse.jetty.servlets.CrossOriginFilter 
not found by com.wrs.panorama [376]
at 
org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1574)[org.apache.felix.framework-5.4.0.jar:]
at 
org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:79)[org.apache.felix.framework-5.4.0.jar:]
at 
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2018)[org.apache.felix.framework-5.4.0.jar:]
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)[:1.8.0_45]
at 
org.apache.felix.framework.Felix.loadBundleClass(Felix.java:1925)[org.apache.felix.framework-5.4.0.jar:]
at 
org.apache.felix.framework.BundleImpl.loadClass(BundleImpl.java:978)[org.apache.felix.framework-5.4.0.jar:]
at 
org.ops4j.pax.swissbox.core.BundleClassLoader.findClass(BundleClassLoader.java:176)[137:org.ops4j.pax.web.pax-web-spi:4.2.4]
at 
org.ops4j.pax.swissbox.core.BundleClassLoader.loadClass(BundleClassLoader.java:194)[137:org.ops4j.pax.web.pax-web-spi:4.2.4]
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)[:1.8.0_45]
at 
org.ops4j.pax.web.extender.war.internal.RegisterWebAppVisitorHS.loadClass(RegisterWebAppVisitorHS.java:248)[132:org.ops4j.pax.web.pax-web-extender-war:4.2.4]
at 
org.ops4j.pax.web.extender.war.internal.RegisterWebAppVisitorWC.visit(RegisterWebAppVisitorWC.java:277)[132:org.ops4j.pax.web.pax-web-extender-war:4.2.4]
at 
org.ops4j.pax.web.extender.war.internal.model.WebApp.accept(WebApp.java:666)[132:org.ops4j.pax.web.pax-web-extender-war:4.2.4]
at 
org.ops4j.pax.web.extender.war.internal.WebAppPublisher$WebAppDependencyListener.register(WebAppPublisher.java:237)[132:org.ops4j.pax.web.pax-web-extender-war:4.2.4]
at 
org.ops4j.pax.web.extender.war.internal.WebAppPublisher$WebAppDependencyListener.addingService(WebAppPublisher.java:182)[132:org.ops4j.pax.web.pax-web-extender-war:4.2.4]
at 
org.ops4j.pax.web.extender.war.internal.WebAppPublisher$WebAppDependencyListener.addingService(WebAppPublisher.java:135)[132:org.ops4j.pax.web.pax-web-extender-war:4.2.4]
at 
org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941)[org.osgi.core-6.0.0.jar:]
at 
org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:870)[org.osgi.core-6.0.0.jar:]
at 
org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)[org.osgi.core-6.0.0.jar:]
at 
org.osgi.util.tracker.AbstractTracked.trackInitial(AbstractTracked.java:183)[org.osgi.core-6.0.0.jar:]
at 
org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:318)[org.osgi.core-6.0.0.jar:]
at 
org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:261)[org.osgi.core-6.0.0.jar:]
at 
org.ops4j.pax.web.extender.war.internal.WebAppPublisher.publish(WebAppPublisher.java:101)[132:org.ops4j.pax.web.pax-web-extender-war:4.2.4]
at 
org.ops4j.pax.web.extender.war.internal.WebObserver.deploy(WebObserver.java:219)[132:org.ops4j.pax.web.pax-web-extender-war:4.2.4]
at 
org.ops4j.pax.web.extender.war.internal.WebObserver$1.doStart(WebObserver.java:179)[132:org.ops4j.pax.web.pax-web-extender-war:4.2.4]
at 
org.ops4j.pax.web.extender.war.internal.extender.SimpleExtension.start(SimpleExtension.java:59)[132:org.ops4j.pax.web.pax-web-extender-war:4.2.4]
at 
org.ops4j.pax.web.extender.war.internal.extender.AbstractExtender$1.run(AbstractExtender.java:280)[132:org.ops4j.pax.web.pax-web-extender-war:4.2.4]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_45]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_45]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_45]
at 
java.util.concurrent.ScheduledThreadPoolExe

Re: 4.0.6 release

[Jason Smith]

Thanks JB – the blueprint 1.6.2 update coming in 4.0.6 is what I am 
specifically interested in.  Glad to hear it is coming soon.

- Jason

-Original Message-
From: Jean-Baptiste Onofré 
Reply-To: "user@karaf.apache.org" 
Date: Thursday, August 4, 2016 at 7:17 AM
To: "user@karaf.apache.org" 
Subject: Re: 4.0.6 release

Hi Jason,

The plan is 3.0.8 end of this week and 4.0.6 end of next week (or 
beginning of the following one).

Regards
JB

On 08/04/2016 03:00 PM, Jason Smith wrote:
> Hello! Are there any updates on when 4.0.6 will be released?  Thanks
>
    >
>
> -  Jason
>

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

4.0.6 release

[Jason Smith]

Hello! Are there any updates on when 4.0.6 will be released?  Thanks


-  Jason

Re: Access control of OSGi Web app?

[Jason Pratt]

Take a look at Shiro and JWT. You should be able to string something
together from that.

On Sun, Jul 31, 2016 at 11:08 PM, Sigmund Lee  wrote:

> Hi all,
>
> Thanks for advice and solutions you guys provided.
>
> Seems like they are all proper ways to protect server-side services. But
> as I said we are a website, what I need is a solution can integrate
> frontend & backend together, provide page-level access control. basically
> two steps involved:
>
> 1. A externalized access control system to protect access to exposed
> services(for example, restful service, web url, etc).
> 2. After access is permitted, return corresponding respond page to
> client(aka, browser), and every button or link on this responded page can
> be display or hidden based on permissions of current user.
>
> Basically, what I need is a solution not only free backend engineers from
> hard-coded authz code, but also free frontend engineers from hard-coding.
>
> Thanks again!
>
> Bests.
> --
> Sig
>
>
>
> On Fri, Jul 29, 2016 at 10:02 PM, Achim Nierbeck 
> wrote:
>
>> yes, as filters without servlets can't be served. They don't have a URI
>> binding.
>>
>> regards, Achim
>>
>> 2016-07-29 15:33 GMT+02:00 Nick Baker :
>>
>>> Hey Achim,
>>>
>>>
>>>
>>> Thanks for this example. We’re looking part of our ongoing OSGi
>>> migration will be URL security as well. We’re using Spring Security in the
>>> legacy non-OSGI space. So this is a timely conversation for us J
>>>
>>>
>>>
>>> Quick question: are we still working with the limitation that Filters
>>> are only invoked if a Servlet or Resource would already serve the URL?
>>>
>>>
>>>
>>> -Nick
>>>
>>>
>>>
>>> *From: *Achim Nierbeck 
>>> *Reply-To: *"user@karaf.apache.org" 
>>> *Date: *Friday, July 29, 2016 at 8:54 AM
>>> *To: *"user@karaf.apache.org" 
>>> *Subject: *Re: Access control of OSGi Web app?
>>>
>>>
>>>
>>> Hi Sigmund,
>>>
>>>
>>>
>>> sorry for being late to the party ... if those solutions above don't
>>> work for you you still have the possibility to create a customized filter
>>> which you can re-use with your own applications.
>>>
>>> For this you can either go the "classical" way of using web-fragments,
>>> or you can share the httpContext between your osgi bundles. For this you
>>> need to declare your httpContext to be sharable and after that you just
>>> need to attach your filter bundle to that sharable httpContext.
>>>
>>>
>>>
>>> Take a look at the following Sample, or better integration test of Pax
>>> Web [1].
>>>
>>>
>>>
>>> regards, Achim
>>>
>>>
>>>
>>> [1] -
>>> https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-itest/pax-web-itest-container/pax-web-itest-container-jetty/src/test/java/org/ops4j/pax/web/itest/jetty/CrossServiceIntegrationTest.java#L59-L95
>>>
>>>
>>>
>>> 2016-07-26 16:05 GMT+02:00 Christian Schneider >> >:
>>>
>>> In karaf authentication is based on JAAS. Using login modules you can
>>> define what source to authenticate against.
>>> The karaf web console is protected by this by default. It is also
>>> possible to enable JAAS based authentication for CXF e.g. for your REST
>>> services.
>>> There is also role based  and group based authentication out of the box.
>>>
>>> There is no attribute based access control available but you can create
>>> this based on the JAAS authentication.
>>>
>>> This code can give you an idea of how to get the subject and the
>>> principals from JAAS in karaf:
>>> https://github.com/apache/aries/blob/trunk/blueprint/blueprint-authz/src/main/java/org/apache/aries/blueprint/authorization/impl/AuthorizationInterceptor.java#L69-L81
>>>
>>> You could create your own annotations or OSGi service to handle the
>>> attribute based authorization based on the authentication information.
>>>
>>> Christian
>>>
>>>
>>>
>>> On 26.07.2016 08:29, Sigmund Lee wrote:
>>>
>>> We are a website, using OSGi as microservices implementation. every
>>> feature of our site is a standalone osgi-based webapp, and splited into
>>> several OSGi bundles(api, impl, webapp, rest, etc).
>>>
>>>
>>>
>>> But there are functions that coupled with more that one bundle, for
>>> example Access Control & Authorization. Currently our authorization code is
>>> hard-coded everywhere and was so hard to maintain.
>>>
>>>
>>>
>>> My question is, what's the proper way to handle with access control when
>>> using OSGi? Is there any osgi-compatible ABAC(Attribute-based access
>>> control, because our authorization model need calculated based on attribute
>>> of resource and context/environment) framework?
>>>
>>>
>>> Thanks.
>>>
>>>
>>>
>>> --
>>>
>>> Sig
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Christian Schneider
>>>
>>> http://www.liquid-reality.de
>>>
>>>
>>>
>>> Open Source Architect
>>>
>>> http://www.talend.com
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>>
>>> Apache Member
>>>
>>> Apache Karaf  Committer & PMC
>>> OPS4J Pax Web  Committer
>>> & Project Lead
>>> blog 

Re: JMX annotations

[Jason Pratt]

thanks JB

On Sun, Jul 17, 2016 at 10:31 PM, Jean-Baptiste Onofré 
wrote:

> Basically:
>
> 1. you define an interface to describe your MBean (like this:
> https://github.com/apache/karaf/blob/master/http/src/main/java/org/apache/karaf/http/core/HttpMBean.java
> )
>
> 2. you implement your MBean. This class extends StandardMBean and
> implements your interface (like this:
> https://github.com/apache/karaf/blob/master/http/src/main/java/org/apache/karaf/http/core/internal/HttpMBeanImpl.java
> )
>
> 3. Then, you register this MBean as a service using service properties for
> ObjectName (in the activator, or DS, or whatever).
>
> Regards
> JB
>
>
> On 07/18/2016 07:20 AM, Pratt, Jason wrote:
>
>> Hi JB,
>> Thanks for the response, does that mean extending the standardmbean class
>> and calling the super in the constructor? Or is there a simpler way to do
>> it?
>>
>> Kind regards,
>> Jason
>>
>> -Original Message-
>> From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net]
>> Sent: Sunday, July 17, 2016 9:48 PM
>> To: user@karaf.apache.org
>> Subject: Re: JMX annotations
>>
>> Hi Jason,
>>
>> In karaf 4, you just directly register a StandardMBean service with
>> property containing the ObjectName.
>>
>> Aries JMX uses a whiteboard partner to automatically register MBean in
>> the MBeanServer.
>>
>> Regards
>> JB
>>
>> On 07/18/2016 05:54 AM, Pratt, Jason wrote:
>>
>>> Hello - I am looking at wiring up a few bundles for JMX, but I can't
>>> seem to find any good examples for it. Can the standard JMX @MBean not
>>> be used? I did find the Aries JMX page, but that didn't really provide
>>> any useful information. Can anyone point me at a good example to use?
>>>
>>> Kind regards,
>>>
>>> Jason
>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

RE: JMX annotations

[Pratt, Jason]

Hi JB,
Thanks for the response, does that mean extending the standardmbean class and 
calling the super in the constructor? Or is there a simpler way to do it?

Kind regards,
Jason

-Original Message-
From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] 
Sent: Sunday, July 17, 2016 9:48 PM
To: user@karaf.apache.org
Subject: Re: JMX annotations

Hi Jason,

In karaf 4, you just directly register a StandardMBean service with property 
containing the ObjectName.

Aries JMX uses a whiteboard partner to automatically register MBean in the 
MBeanServer.

Regards
JB

On 07/18/2016 05:54 AM, Pratt, Jason wrote:
> Hello - I am looking at wiring up a few bundles for JMX, but I can't 
> seem to find any good examples for it. Can the standard JMX @MBean not 
> be used? I did find the Aries JMX page, but that didn't really provide 
> any useful information. Can anyone point me at a good example to use?
>
> Kind regards,
>
> Jason
>

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

RE: WeavingHook using Felix

[Pratt, Jason]

I was hoping that it would be a fairly easy task to bring some aspects into our 
project, but it seems to be path not easily traveled.

Thanks for the comments

From: Tim Ward [mailto:tim.w...@paremus.com]
Sent: Saturday, July 16, 2016 2:39 AM
To: user@karaf.apache.org
Subject: Re: WeavingHook using Felix

I would like to add that you need to be *very* careful with weaving hooks. If 
you have to add dynamic imports then you should make sure to add all the 
necessary version/target information

It is also difficult to add a weaving hook using DS or blueprint. Lazy 
behaviours cause the Weaving hook to try to weave itself.

Weaving hooks are also one of the few times that start up ordering really is 
important in OSGi. Ideally your hook will have no service dependencies, no 
configuration dependencies, be registered eagerly very early in the framework 
start process, and be very selective about what it tries to weave.

I also have one question for you. What are you trying to achieve and do you 
*really* need a weaving hook to do it? In most cases there are other, safer 
ways to achieve the same thing.

Tim Ward

OSGi IoT EG chair

Sent from my iPhone

On 16 Jul 2016, at 03:15, David Jencks 
mailto:david.a.jen...@gmail.com>> wrote:
I hope there aren’t any uses that don’t work with any R5 framework.   I believe 
Apache Aries proxy and (IIRC) spi-fly use weaving hooks.

hope this helps
david jencks

On Jul 15, 2016, at 4:51 PM, Pratt, Jason 
mailto:jason.pr...@windriver.com>> wrote:

Hello - Can anyone recommend a good example for WeavingHook that uses the Felix 
framework?

Regards,
Jason

JMX annotations

[Pratt, Jason]

Hello - I am looking at wiring up a few bundles for JMX, but I can't seem to 
find any good examples for it. Can the standard JMX @MBean not be used? I did 
find the Aries JMX page, but that didn't really provide any useful information. 
Can anyone point me at a good example to use?

Kind regards,
Jason

WeavingHook using Felix

[Pratt, Jason]

Hello - Can anyone recommend a good example for WeavingHook that uses the Felix 
framework?

Regards,
Jason

Apollo feature for Karaf

[Pratt, Jason]

Hello - Has anyone done any work on integrating Apollo into Karaf? I see 
https://issues.apache.org/jira/browse/APLO-299 is still open.

Regards,
Jason

RE: Blueprint class missing error

[Pratt, Jason]

Sorry, we're using


org.apache.aries.blueprint
org.apache.aries.blueprint.api
1.0.1



org.apache.aries.blueprint
org.apache.aries.blueprint.core
1.4.3



org.apache.aries.blueprint
org.apache.aries.blueprint.annotation.api
1.0.1


-Original Message-
From: Pratt, Jason [mailto:jason.pr...@windriver.com] 
Sent: Wednesday, June 08, 2016 1:43 PM
To: user@karaf.apache.org
Subject: RE: Blueprint class missing error

I believe that it is 1.0.0

-Original Message-
From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net]
Sent: Wednesday, June 08, 2016 1:09 PM
To: user@karaf.apache.org
Subject: Re: Blueprint class missing error

Hi Jason,

ok, it's what I thought: the service is not there, that's why the blueprint 
container is in GracePeriod.

I think the annotations don't behave as expected: in the generated 
blueprint.xml, we can see:



...

...


So, basically, the blueprint defines a  that it doesn't use
(userService-) in any other bean, whereas it does a  directly.
It doesn't make sense to me ;)

Let me check in the annotations. What version of Aries Blueprint annotations 
are you using ?

Regards
JB

On 06/08/2016 10:01 PM, Pratt, Jason wrote:
> Interestingly, it is not coming up under "ls". Any recommendations?
> I was thinking of hand turning an XML file instead of annotations 
> based
>
> -Original Message-
> From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net]
> Sent: Wednesday, June 08, 2016 11:59 AM
> To: user@karaf.apache.org
> Subject: Re: Blueprint class missing error
>
> Hi Jason,
>
> can you check if the UserService is actually available (using ls or
> bundle:service) ?
>
> GracePeriod means that you have a  (not optional) not satisfied 
> as blueprint container startup: it's not a package import/export issue 
> (module layer) but a service issue.
> So, basically, I don't think the problem is on blueprint side, but more on 
> the service provider bundle side.
>
> Regards
> JB
>
> On 06/08/2016 08:34 PM, Pratt, Jason wrote:
>> Hello - I am having an issue pop up that I haven't seen before. I 
>> have a service that is hanging in a Grace state and I am not sure 
>> why. We have many services declared just like this and running in 
>> other bundles. What am I missing? The details are:
>>
>> /422 | GracePeriod |  80 | 1.0.8  | WRS ::
>> RNT :: Server :: Core :: User/
>>
>> The log file shows its waiting for a dependency that is in the same bundle:
>>
>> /13 - org.apache.aries.blueprint.core - 1.5.0 | Bundle
>> rnt-core-user/1.0.8 is waiting for dependencies 
>> [(objectClass=com.wrs.rnt.core.user.service.api.UserService)]/
>>
>> Looking further in the console:
>>
>> /rnt-user@root>bundle:diag 422/
>>
>> /WRS :: RNT :: Server :: Core :: User (422)/
>>
>> /--/
>>
>> /Status: GracePeriod/
>>
>> /Blueprint/
>>
>> /6/8/16 11:10 AM/
>>
>> /Missing dependencies:/
>>
>> /(objectClass=com.wrs.rnt.core.user.service.api.UserService)/
>>
>> The class in question is declared:
>>
>> *import*com.wrs.rnt.core.user.service.api.UserService;
>>
>> /@CrossOriginResourceSharing//(///
>>
>> /allowAllOrigins = /*/true/*/, allowCredentials = /*/true/*/,
>> maxAge = 1, ///
>>
>> /allowHeaders = { //"X-custom-1"//, //"X-custom-2"//},
>> exposeHeaders = { //"X-custom-3"//, //"X-custom-4"//})///
>>
>> /@Named//(//"userService"//)///
>>
>> /@OsgiServiceProvider//(classes = { UserService./*/class/*/})///
>>
>> /@Singleton///
>>
>> /@Transactional///
>>
>> */public/*//*/class/*/UserServiceImpl /*/implements/*/UserService {/
>>
>> //
>>
>> With the autowire.xml showing:
>>
>> //
>>
>> /http://www.osgi.org/xmlns/blueprint/v1.0.0";
>> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0";
>> xmlns:tx="http://aries.apache.org/xmlns/transactions/v2.0.0";
>> xmlns:jpa="http://aries.apache.org/xmlns/jpa/v2.0.0";>/
>>
>> //
>>
>> //
>>
>> /> class="com.wrs.rnt.core.user.service.FilterServiceImpl"
>> ext:field-injection="true">/
>>
>> //
>>
>> /> class="com.wrs.rnt.core.user.service.UserServiceImpl"
>> ext:field-injection="true">/
>>
>> //
>>
>> /> interface="com.wrs.rnt.core.product.service.api.ProductLineService"/>
>> /
>&g

RE: Blueprint class missing error

[Pratt, Jason]

I believe that it is 1.0.0

-Original Message-
From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] 
Sent: Wednesday, June 08, 2016 1:09 PM
To: user@karaf.apache.org
Subject: Re: Blueprint class missing error

Hi Jason,

ok, it's what I thought: the service is not there, that's why the blueprint 
container is in GracePeriod.

I think the annotations don't behave as expected: in the generated 
blueprint.xml, we can see:



...

...


So, basically, the blueprint defines a  that it doesn't use
(userService-) in any other bean, whereas it does a  directly.
It doesn't make sense to me ;)

Let me check in the annotations. What version of Aries Blueprint annotations 
are you using ?

Regards
JB

On 06/08/2016 10:01 PM, Pratt, Jason wrote:
> Interestingly, it is not coming up under "ls". Any recommendations?
> I was thinking of hand turning an XML file instead of annotations 
> based
>
> -Original Message-
> From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net]
> Sent: Wednesday, June 08, 2016 11:59 AM
> To: user@karaf.apache.org
> Subject: Re: Blueprint class missing error
>
> Hi Jason,
>
> can you check if the UserService is actually available (using ls or
> bundle:service) ?
>
> GracePeriod means that you have a  (not optional) not satisfied 
> as blueprint container startup: it's not a package import/export issue 
> (module layer) but a service issue.
> So, basically, I don't think the problem is on blueprint side, but more on 
> the service provider bundle side.
>
> Regards
> JB
>
> On 06/08/2016 08:34 PM, Pratt, Jason wrote:
>> Hello - I am having an issue pop up that I haven't seen before. I 
>> have a service that is hanging in a Grace state and I am not sure 
>> why. We have many services declared just like this and running in 
>> other bundles. What am I missing? The details are:
>>
>> /422 | GracePeriod |  80 | 1.0.8  | WRS ::
>> RNT :: Server :: Core :: User/
>>
>> The log file shows its waiting for a dependency that is in the same bundle:
>>
>> /13 - org.apache.aries.blueprint.core - 1.5.0 | Bundle
>> rnt-core-user/1.0.8 is waiting for dependencies 
>> [(objectClass=com.wrs.rnt.core.user.service.api.UserService)]/
>>
>> Looking further in the console:
>>
>> /rnt-user@root>bundle:diag 422/
>>
>> /WRS :: RNT :: Server :: Core :: User (422)/
>>
>> /--/
>>
>> /Status: GracePeriod/
>>
>> /Blueprint/
>>
>> /6/8/16 11:10 AM/
>>
>> /Missing dependencies:/
>>
>> /(objectClass=com.wrs.rnt.core.user.service.api.UserService)/
>>
>> The class in question is declared:
>>
>> *import*com.wrs.rnt.core.user.service.api.UserService;
>>
>> /@CrossOriginResourceSharing//(///
>>
>> /allowAllOrigins = /*/true/*/, allowCredentials = /*/true/*/,
>> maxAge = 1, ///
>>
>> /allowHeaders = { //"X-custom-1"//, //"X-custom-2"//},
>> exposeHeaders = { //"X-custom-3"//, //"X-custom-4"//})///
>>
>> /@Named//(//"userService"//)///
>>
>> /@OsgiServiceProvider//(classes = { UserService./*/class/*/})///
>>
>> /@Singleton///
>>
>> /@Transactional///
>>
>> */public/*//*/class/*/UserServiceImpl /*/implements/*/UserService {/
>>
>> //
>>
>> With the autowire.xml showing:
>>
>> //
>>
>> /http://www.osgi.org/xmlns/blueprint/v1.0.0";
>> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0";
>> xmlns:tx="http://aries.apache.org/xmlns/transactions/v2.0.0";
>> xmlns:jpa="http://aries.apache.org/xmlns/jpa/v2.0.0";>/
>>
>> //
>>
>> //
>>
>> /> class="com.wrs.rnt.core.user.service.FilterServiceImpl"
>> ext:field-injection="true">/
>>
>> //
>>
>> /> class="com.wrs.rnt.core.user.service.UserServiceImpl"
>> ext:field-injection="true">/
>>
>> //
>>
>> /> interface="com.wrs.rnt.core.product.service.api.ProductLineService"/>
>> /
>>
>> /> interface="com.wrs.rnt.core.user.service.api.UserService"/>/
>>
>> /> interface="com.wrs.rnt.core.user.service.api.FilterService"/>/
>>
>> /> interface="com.wrs.rnt.core.user.service.api.UserService"/>/
>>
>> //
>>
>> //
>>
>> The calling class which is in the same bundle is declared:
>>
>> /@Named//(//"fi

RE: Blueprint class missing error

[Pratt, Jason]

Interestingly, it is not coming up under "ls". Any recommendations?
I was thinking of hand turning an XML file instead of annotations based

-Original Message-
From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] 
Sent: Wednesday, June 08, 2016 11:59 AM
To: user@karaf.apache.org
Subject: Re: Blueprint class missing error

Hi Jason,

can you check if the UserService is actually available (using ls or
bundle:service) ?

GracePeriod means that you have a  (not optional) not satisfied as 
blueprint container startup: it's not a package import/export issue (module 
layer) but a service issue.
So, basically, I don't think the problem is on blueprint side, but more on the 
service provider bundle side.

Regards
JB

On 06/08/2016 08:34 PM, Pratt, Jason wrote:
> Hello - I am having an issue pop up that I haven't seen before. I have 
> a service that is hanging in a Grace state and I am not sure why. We 
> have many services declared just like this and running in other 
> bundles. What am I missing? The details are:
>
> /422 | GracePeriod |  80 | 1.0.8  | WRS ::
> RNT :: Server :: Core :: User/
>
> The log file shows its waiting for a dependency that is in the same bundle:
>
> /13 - org.apache.aries.blueprint.core - 1.5.0 | Bundle
> rnt-core-user/1.0.8 is waiting for dependencies 
> [(objectClass=com.wrs.rnt.core.user.service.api.UserService)]/
>
> Looking further in the console:
>
> /rnt-user@root>bundle:diag 422/
>
> /WRS :: RNT :: Server :: Core :: User (422)/
>
> /--/
>
> /Status: GracePeriod/
>
> /Blueprint/
>
> /6/8/16 11:10 AM/
>
> /Missing dependencies:/
>
> /(objectClass=com.wrs.rnt.core.user.service.api.UserService)/
>
> The class in question is declared:
>
> *import*com.wrs.rnt.core.user.service.api.UserService;
>
> /@CrossOriginResourceSharing//(///
>
> /allowAllOrigins = /*/true/*/, allowCredentials = /*/true/*/,
> maxAge = 1, ///
>
> /allowHeaders = { //"X-custom-1"//, //"X-custom-2"//},
> exposeHeaders = { //"X-custom-3"//, //"X-custom-4"//})///
>
> /@Named//(//"userService"//)///
>
> /@OsgiServiceProvider//(classes = { UserService./*/class/*/})///
>
> /@Singleton///
>
> /@Transactional///
>
> */public/*//*/class/*/UserServiceImpl /*/implements/*/UserService {/
>
> //
>
> With the autowire.xml showing:
>
> //
>
> /http://www.osgi.org/xmlns/blueprint/v1.0.0";
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0";
> xmlns:tx="http://aries.apache.org/xmlns/transactions/v2.0.0";
> xmlns:jpa="http://aries.apache.org/xmlns/jpa/v2.0.0";>/
>
> //
>
> //
>
> / class="com.wrs.rnt.core.user.service.FilterServiceImpl"
> ext:field-injection="true">/
>
> //
>
> / class="com.wrs.rnt.core.user.service.UserServiceImpl"
> ext:field-injection="true">/
>
> //
>
> / interface="com.wrs.rnt.core.product.service.api.ProductLineService"/>/
>
> / interface="com.wrs.rnt.core.user.service.api.UserService"/>/
>
> / interface="com.wrs.rnt.core.user.service.api.FilterService"/>/
>
> / interface="com.wrs.rnt.core.user.service.api.UserService"/>/
>
> //
>
> //
>
> The calling class which is in the same bundle is declared:
>
> /@Named//(//"filterService"//)///
>
> /@OsgiServiceProvider//(classes = { FilterService./*/class/*/})///
>
> /@Singleton///
>
> /@Transactional///
>
> */public/*//*/class/*/FilterServiceImpl /*/implements/*/FilterService 
> {///
>
> //*/private/*//*/final/*//*/static/*/Logger /*/log/*/ =
> LoggerFactory.getLogger(FilterServiceImpl./*/class/*/);///
>
> //
>
> ///@PersistenceContext//(unitName = //"rnt-core"//)///
>
> /   EntityManager //em//;///
>
> //
>
> ///@Inject//(ref = //"userService"//)///
>
> ///@OsgiService///
>
> //*/private/*/UserService //userService//;///
>
> //
>
> ///@Inject//(ref = //"productLineService"//)///
>
> ///@OsgiService///
>
> //*/private/*/ProductLineService //productLineService//;/
>
> //
>
> With the maven-bundle-plugin exporting the following:
>
> 
>
> /
> !com.wrs.rnt.core.user.**.api,com.wrs.rnt.core.user.service.*;version=
> ${project.version}///
>
> //
>

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

Blueprint class missing error

[Pratt, Jason]

Hello - I am having an issue pop up that I haven't seen before. I have a 
service that is hanging in a Grace state and I am not sure why. We have many 
services declared just like this and running in other bundles. What am I 
missing? The details are:

422 | GracePeriod |  80 | 1.0.8  | WRS :: RNT :: 
Server :: Core :: User

The log file shows its waiting for a dependency that is in the same bundle:

13 - org.apache.aries.blueprint.core - 1.5.0 | Bundle rnt-core-user/1.0.8 is 
waiting for dependencies 
[(objectClass=com.wrs.rnt.core.user.service.api.UserService)]

Looking further in the console:

rnt-user@root>bundle:diag 422
WRS :: RNT :: Server :: Core :: User (422)
--
Status: GracePeriod
Blueprint
6/8/16 11:10 AM
Missing dependencies:
(objectClass=com.wrs.rnt.core.user.service.api.UserService)

The class in question is declared:

import com.wrs.rnt.core.user.service.api.UserService;


@CrossOriginResourceSharing(
allowAllOrigins = true, allowCredentials = true, maxAge = 1,
allowHeaders = { "X-custom-1", "X-custom-2" }, exposeHeaders = { 
"X-custom-3", "X-custom-4" })
@Named("userService")
@OsgiServiceProvider(classes = { UserService.class })
@Singleton
@Transactional
public class UserServiceImpl implements UserService {

With the autowire.xml showing:


http://www.osgi.org/xmlns/blueprint/v1.0.0"; 
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0"; 
xmlns:tx="http://aries.apache.org/xmlns/transactions/v2.0.0"; 
xmlns:jpa="http://aries.apache.org/xmlns/jpa/v2.0.0";>












The calling class which is in the same bundle is declared:

@Named("filterService")
@OsgiServiceProvider(classes = { FilterService.class })
@Singleton
@Transactional
public class FilterServiceImpl implements FilterService {
   private final static Logger  log = 
LoggerFactory.getLogger(FilterServiceImpl.class);

   @PersistenceContext(unitName = "rnt-core")
   EntityManagerem;

   @Inject(ref = "userService")
   @OsgiService
   private UserService  userService;

   @Inject(ref = "productLineService")
   @OsgiService
   private ProductLineService productLineService;

With the maven-bundle-plugin exporting the following:


   
!com.wrs.rnt.core.user.**.api,com.wrs.rnt.core.user.service.*;version=${project.version}

Camel-Redis without spring

[Pratt, Jason]

Hello - I am looking at using Camel to connect to our Redis backend, but I see 
that the feature has spring listed in the name "camel-spring-redis". How well 
will this play with Blueprint in the Karaf sandbox?

I thought I had read somewhere that Spring had stopped supporting OSGi.

Kind regards,
Jason

Shiro 1.2.4 issues

[Pratt, Jason]

Hello - I am having an issue popping up with Shiro to provide authentication to 
our front end. The log says it's a beanutils issue, but I have a servicemix 
bundle that provides the class in question so I am a bit confused. I've 
installed Shiro via its karaf feature.

Has anyone encountered this or have a recommendation to correct it?


 org.apache.servicemix.bundles
 
org.apache.servicemix.bundles.commons-beanutils
 1.8.3_2



2016-04-27 11:43:22,573 | WARN  | tp1987743246-555 | PhaseInterceptorChain  
  | 174 - org.apache.cxf.cxf-core - 3.1.4 | Application ShiroServiceImpl 
has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: org/apache/commons/beanutils/PropertyUtils
at 
org.apache.cxf.service.invoker.AbstractInvoker.createFault(AbstractInvoker.java:162)[174:org.apache.cxf.cxf-core:3.1.4]
at 
org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:128)[174:org.apache.cxf.cxf-core:3.1.4]
at 
org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:200)[187:org.apache.cxf.cxf-rt-frontend-jaxrs:3.1.4]
at 
org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:99)[187:org.apache.cxf.cxf-rt-frontend-jaxrs:3.1.4]
at 
org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59)[174:org.apache.cxf.cxf-core:3.1.4]
at 
org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:96)[174:org.apache.cxf.cxf-core:3.1.4]
at 
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)[174:org.apache.cxf.cxf-core:3.1.4]
at 
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)[174:org.apache.cxf.cxf-core:3.1.4]
at 
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:251)[200:org.apache.cxf.cxf-rt-transports-http:3.1.4]
at 
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234)[200:org.apache.cxf.cxf-rt-transports-http:3.1.4]
at 
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208)[200:org.apache.cxf.cxf-rt-transports-http:3.1.4]
at 
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160)[200:org.apache.cxf.cxf-rt-transports-http:3.1.4]
at 
org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:180)[200:org.apache.cxf.cxf-rt-transports-http:3.1.4]
at 
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:293)[200:org.apache.cxf.cxf-rt-transports-http:3.1.4]
at 
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:212)[200:org.apache.cxf.cxf-rt-transports-http:3.1.4]
at 
javax.servlet.http.HttpServlet.service(HttpServlet.java:707)[82:javax.servlet-api:3.1.0]
at 
org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:268)[200:org.apache.cxf.cxf-rt-transports-http:3.1.4]
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)[133:org.eclipse.jetty.servlet:9.2.14.v20151106]
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)[133:org.eclipse.jetty.servlet:9.2.14.v20151106]
at 
org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:70)[151:org.ops4j.pax.web.pax-web-jetty:4.2.4]
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)[132:org.eclipse.jetty.server:9.2.14.v20151106]
at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)[131:org.eclipse.jetty.security:9.2.14.v20151106]
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)[132:org.eclipse.jetty.server:9.2.14.v20151106]
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)[132:org.eclipse.jetty.server:9.2.14.v20151106]
at 
org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:271)[151:org.ops4j.pax.web.pax-web-jetty:4.2.4]
at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)[133:org.eclipse.jetty.servlet:9.2.14.v20151106]
at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)[132:org.eclipse.jetty.server:9.2.14.v20151106]
at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)[132:org.eclipse.jetty.server:9.2.14.v20151106]
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)[132:org.eclipse.jetty.server:9.2.14.v20151106]
at 
org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80)[151:org.ops4j.pax.web.pax-web-jetty:4.2.4]
at 
or

RE: Need Help in getting started with EIK 0.9.0

[Pratt, Jason]

Is there a roadmap for Karaf on what is being planned and why that we can see?

-Original Message-
From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] 
Sent: Monday, April 18, 2016 10:22 PM
To: user@karaf.apache.org
Subject: Re: Need Help in getting started with EIK 0.9.0

Hi Vishal,

I'm not sure that using EIK is a good idea at this point.

I'm not Eclipse user (I prefer IntelliJ) and I'm not a big bndtools fan. 
Karaf doesn't really need any IDE.

You can develop OSGi bundles (and associated features) in any IDE, leveraging 
Maven.

The coming karaf-boot will also simplify a lot the way to create bundles and 
applications, providing annotations and maven plugin.

Regards
JB

On 04/18/2016 10:42 PM, Balana, Vishal wrote:
> Ok, Thanks for your reply Jean!
>
> So is it good idea to rely upon EIK for development at this point in time?
>
> Is anyone here been able to create Apache Karaf Installation and do the 
> development in eclipse with it?
>
> I would like to know how others are developing OSGI bundles with eclipse?
>
>
> Regards,
> Vishal
>
> -Original Message-
> From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net]
> Sent: Monday, April 18, 2016 10:45 AM
> To: user@karaf.apache.org
> Subject: Re: Need Help in getting started with EIK 0.9.0
>
> Hi Vishal,
>
> unfortunately, EIK is not really active and maintained.
>
> Anyway the EIK plugins are there:
>
> http://repo.maven.apache.org/maven2/org/apache/karaf/eik/plugins/
>
> Regards
> JB
>
> On 04/18/2016 04:42 PM, Balana, Vishal wrote:
>> Can somebody please suggest about How could I get the EIK plugins 
>> source from GIT for version 0.9.0?
>>
>> Thanks,
>>
>> Vishal
>>
>> *From:*Balana, Vishal
>> *Sent:* Thursday, April 14, 2016 11:46 PM
>> *To:* 'user@karaf.apache.org'
>> *Subject:* Need Help in getting started with EIK
>>
>> Hello,
>>
>> I am trying to use EIK plugin to create first Apache Karaf 
>> Installation using Apache Karaf Perspective.
>>
>> After the Project is created, I am getting following error:
>>
>> java.lang.RuntimeException: URL
>> [mvn:org.apache.karaf.features/standard/3.0.5/xml/features] could not 
>> be resolved.
>>
>>   at
>> org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.j
>> ava:195)
>>
>>   at
>> org.apache.karaf.eik.ui.features.FeaturesResolverJob.resolveFeatures(
>> FeaturesResolverJob.java:129)
>>
>>   at
>> org.apache.karaf.eik.ui.features.FeaturesResolverJob.run(FeaturesReso
>> lverJob.java:87)
>>
>>   at
>> org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
>>
>> Could somebody help?  I am using Karaf 3.0.5.
>>
>> Thanks,
>>
>> Vishal
>>
>

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

Re: ssh access to Karaf 4.0.4

[Jason Reilly]

I figured this out.  I left off from the bottom of my bootFeatures a 
couple of features for some projects that I *thought* worked...meaning I 
didn't think they would not break anything.  One of them included the 
following:


mvn:org.bouncycastle/com.springsource.org.bouncycastle.jce/1.39.0

When I commented this out, I was able to log in successfully via the ssh 
command.


Thanks for the help,
Jason

On 03/04/2016 01:31 PM, Jason Reilly wrote:
I did a diff of the fresh Karaf ('feature:list | grep -v Uninstalled | 
sort') against my custom distribution & noticed I was not including 
'shell-compat'.  After adding that, I tried again to get the same error.


Here is what my bootFeatures looks like from the pom.xml:

standard

feature

shell

shell-compat

bundle

config

diagnostic

instance

kar

jaas

log

package

service

system

ssh

management

deployer

obr

http

war

jetty

scr

jndi

pax-cdi

aries-blueprint

cxf

jdbc

transaction-api/1.2.0

transaction

jpa

jms

activemq


Suggestions?




On 03/04/2016 12:03 PM, Jean-Baptiste Onofré wrote:
Do you define the same default features set as in Karaf standard 
distro ? or did you remove some features/libs ?


Regards
JB

On 03/04/2016 05:57 PM, Jason Reilly wrote:

Yes, I started with bin/karaf.  I was able to do as you didjust not
with my custom distribution.  Something must be different, but I don't
know what.

On 03/04/2016 11:56 AM, Jean-Baptiste Onofré wrote:

Do you start Karaf with bin/karaf ?

I just tried with a fresh Karaf 4.0.4:

bin/karaf

and on another terminal:

jbonofre@latitude:~$ ssh -p 8101 karaf@localhost
Password authentication
Password:
__ __  
   / //_/ __ _/ __/
  / ,<  / __ `/ ___/ __ `/ /_
 / /| |/ /_/ / /  / /_/ / __/
/_/ |_|\__,_/_/   \__,_/_/

  Apache Karaf (4.0.4)

Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit 'system:shutdown' to shutdown Karaf.
Hit '' or type 'logout' to disconnect shell from current 
session.


karaf@root()>


Regards
JB

On 03/04/2016 05:54 PM, Jason Reilly wrote:

$ java -version
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)


How do I check which JCE I am using?


On 03/04/2016 11:52 AM, Jean-Baptiste Onofré wrote:

Hi Jason,

which JCE/JDK are you using (provider and version) ?

Thanks,
Regards
JB

On 03/04/2016 05:48 PM, Jason Reilly wrote:

Hi all,

I am seeing an exception in the log when I try the following:

$ ssh -p 8101 -l karaf localhost

Connection reset by 127.0.0.1


 From the karaf.log file:

2016-03-04 11:12:27,501 | WARN  | f]-nio2-thread-1 |
ServerSession| 5 - org.apache.sshd.core - 
0.14.0 |

Exception caught

java.security.InvalidAlgorithmParameterException: parameter object
not a
ECParameterSpec

 at
org.bouncycastle.jce.provider.JDKKeyPairGenerator$EC.initialize(Unknown 



Source)

 at
java.security.KeyPairGenerator.initialize(KeyPairGenerator.java:411)[:1.8.0_45] 






 at
org.apache.sshd.common.kex.ECDH.getE(ECDH.java:58)[5:org.apache.sshd.core:0.14.0] 






 at
org.apache.sshd.server.kex.AbstractDHGServer.init(AbstractDHGServer.java:71)[5:org.apache.sshd.core:0.14.0] 






 at
org.apache.sshd.common.session.AbstractSession.doHandleMessage(AbstractSession.java:390)[5:org.apache.sshd.core:0.14.0] 






 at
org.apache.sshd.common.session.AbstractSession.handleMessage(AbstractSession.java:326)[5:org.apache.sshd.core:0.14.0] 






 at
org.apache.sshd.common.session.AbstractSession.decode(AbstractSession.java:780)[5:org.apache.sshd.core:0.14.0] 






 at
org.apache.sshd.common.session.AbstractSession.messageReceived(AbstractSession.java:308)[5:org.apache.sshd.core:0.14.0] 








This is from a custom distribution of Karafwhen I try the same
with
a clean Karaf4 instance, I do not encounter this issue & am able to
login successfully.  I figured it must be one of the etc/*.cfg 
files I
messed up that's included in the custom distribution. However, 
when I
remove all the custom distribution's etc files, I still 
encounter the

login problem.  Is there something else I can try?

Thanks
Jason

Re: ssh access to Karaf 4.0.4

[Jason Reilly]

I did a diff of the fresh Karaf ('feature:list | grep -v Uninstalled | 
sort') against my custom distribution & noticed I was not including 
'shell-compat'.  After adding that, I tried again to get the same error.


Here is what my bootFeatures looks like from the pom.xml:

standard

feature

shell

shell-compat

bundle

config

diagnostic

instance

kar

jaas

log

package

service

system

ssh

management

deployer

obr

http

war

jetty

scr

jndi

pax-cdi

aries-blueprint

cxf

jdbc

transaction-api/1.2.0

transaction

jpa

jms

activemq


Suggestions?




On 03/04/2016 12:03 PM, Jean-Baptiste Onofré wrote:
Do you define the same default features set as in Karaf standard 
distro ? or did you remove some features/libs ?


Regards
JB

On 03/04/2016 05:57 PM, Jason Reilly wrote:

Yes, I started with bin/karaf.  I was able to do as you didjust not
with my custom distribution.  Something must be different, but I don't
know what.

On 03/04/2016 11:56 AM, Jean-Baptiste Onofré wrote:

Do you start Karaf with bin/karaf ?

I just tried with a fresh Karaf 4.0.4:

bin/karaf

and on another terminal:

jbonofre@latitude:~$ ssh -p 8101 karaf@localhost
Password authentication
Password:
__ __  
   / //_/ __ _/ __/
  / ,<  / __ `/ ___/ __ `/ /_
 / /| |/ /_/ / /  / /_/ / __/
/_/ |_|\__,_/_/   \__,_/_/

  Apache Karaf (4.0.4)

Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit 'system:shutdown' to shutdown Karaf.
Hit '' or type 'logout' to disconnect shell from current 
session.


karaf@root()>


Regards
JB

On 03/04/2016 05:54 PM, Jason Reilly wrote:

$ java -version
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)


How do I check which JCE I am using?


On 03/04/2016 11:52 AM, Jean-Baptiste Onofré wrote:

Hi Jason,

which JCE/JDK are you using (provider and version) ?

Thanks,
Regards
JB

On 03/04/2016 05:48 PM, Jason Reilly wrote:

Hi all,

I am seeing an exception in the log when I try the following:

$ ssh -p 8101 -l karaf localhost

Connection reset by 127.0.0.1


 From the karaf.log file:

2016-03-04 11:12:27,501 | WARN  | f]-nio2-thread-1 |
ServerSession| 5 - org.apache.sshd.core - 
0.14.0 |

Exception caught

java.security.InvalidAlgorithmParameterException: parameter object
not a
ECParameterSpec

 at
org.bouncycastle.jce.provider.JDKKeyPairGenerator$EC.initialize(Unknown 



Source)

 at
java.security.KeyPairGenerator.initialize(KeyPairGenerator.java:411)[:1.8.0_45] 






 at
org.apache.sshd.common.kex.ECDH.getE(ECDH.java:58)[5:org.apache.sshd.core:0.14.0] 






 at
org.apache.sshd.server.kex.AbstractDHGServer.init(AbstractDHGServer.java:71)[5:org.apache.sshd.core:0.14.0] 






 at
org.apache.sshd.common.session.AbstractSession.doHandleMessage(AbstractSession.java:390)[5:org.apache.sshd.core:0.14.0] 






 at
org.apache.sshd.common.session.AbstractSession.handleMessage(AbstractSession.java:326)[5:org.apache.sshd.core:0.14.0] 






 at
org.apache.sshd.common.session.AbstractSession.decode(AbstractSession.java:780)[5:org.apache.sshd.core:0.14.0] 






 at
org.apache.sshd.common.session.AbstractSession.messageReceived(AbstractSession.java:308)[5:org.apache.sshd.core:0.14.0] 








This is from a custom distribution of Karafwhen I try the same
with
a clean Karaf4 instance, I do not encounter this issue & am able to
login successfully.  I figured it must be one of the etc/*.cfg 
files I
messed up that's included in the custom distribution. However, 
when I
remove all the custom distribution's etc files, I still encounter 
the

login problem.  Is there something else I can try?

Thanks
Jason

Re: ssh access to Karaf 4.0.4

[Jason Reilly]

Yes, I started with bin/karaf.  I was able to do as you didjust not 
with my custom distribution.  Something must be different, but I don't 
know what.


On 03/04/2016 11:56 AM, Jean-Baptiste Onofré wrote:

Do you start Karaf with bin/karaf ?

I just tried with a fresh Karaf 4.0.4:

bin/karaf

and on another terminal:

jbonofre@latitude:~$ ssh -p 8101 karaf@localhost
Password authentication
Password:
__ __  
   / //_/ __ _/ __/
  / ,<  / __ `/ ___/ __ `/ /_
 / /| |/ /_/ / /  / /_/ / __/
/_/ |_|\__,_/_/   \__,_/_/

  Apache Karaf (4.0.4)

Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit 'system:shutdown' to shutdown Karaf.
Hit '' or type 'logout' to disconnect shell from current session.

karaf@root()>


Regards
JB

On 03/04/2016 05:54 PM, Jason Reilly wrote:

$ java -version
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)


How do I check which JCE I am using?


On 03/04/2016 11:52 AM, Jean-Baptiste Onofré wrote:

Hi Jason,

which JCE/JDK are you using (provider and version) ?

Thanks,
Regards
JB

On 03/04/2016 05:48 PM, Jason Reilly wrote:

Hi all,

I am seeing an exception in the log when I try the following:

$ ssh -p 8101 -l karaf localhost

Connection reset by 127.0.0.1


 From the karaf.log file:

2016-03-04 11:12:27,501 | WARN  | f]-nio2-thread-1 |
ServerSession| 5 - org.apache.sshd.core - 0.14.0 |
Exception caught

java.security.InvalidAlgorithmParameterException: parameter object 
not a

ECParameterSpec

 at
org.bouncycastle.jce.provider.JDKKeyPairGenerator$EC.initialize(Unknown 


Source)

 at
java.security.KeyPairGenerator.initialize(KeyPairGenerator.java:411)[:1.8.0_45] 





 at
org.apache.sshd.common.kex.ECDH.getE(ECDH.java:58)[5:org.apache.sshd.core:0.14.0] 





 at
org.apache.sshd.server.kex.AbstractDHGServer.init(AbstractDHGServer.java:71)[5:org.apache.sshd.core:0.14.0] 





 at
org.apache.sshd.common.session.AbstractSession.doHandleMessage(AbstractSession.java:390)[5:org.apache.sshd.core:0.14.0] 





 at
org.apache.sshd.common.session.AbstractSession.handleMessage(AbstractSession.java:326)[5:org.apache.sshd.core:0.14.0] 





 at
org.apache.sshd.common.session.AbstractSession.decode(AbstractSession.java:780)[5:org.apache.sshd.core:0.14.0] 





 at
org.apache.sshd.common.session.AbstractSession.messageReceived(AbstractSession.java:308)[5:org.apache.sshd.core:0.14.0] 







This is from a custom distribution of Karafwhen I try the same 
with

a clean Karaf4 instance, I do not encounter this issue & am able to
login successfully.  I figured it must be one of the etc/*.cfg files I
messed up that's included in the custom distribution. However, when I
remove all the custom distribution's etc files, I still encounter the
login problem.  Is there something else I can try?

Thanks
Jason

Re: ssh access to Karaf 4.0.4

[Jason Reilly]

$ java -version
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)


How do I check which JCE I am using?


On 03/04/2016 11:52 AM, Jean-Baptiste Onofré wrote:

Hi Jason,

which JCE/JDK are you using (provider and version) ?

Thanks,
Regards
JB

On 03/04/2016 05:48 PM, Jason Reilly wrote:

Hi all,

I am seeing an exception in the log when I try the following:

$ ssh -p 8101 -l karaf localhost

Connection reset by 127.0.0.1


 From the karaf.log file:

2016-03-04 11:12:27,501 | WARN  | f]-nio2-thread-1 |
ServerSession| 5 - org.apache.sshd.core - 0.14.0 |
Exception caught

java.security.InvalidAlgorithmParameterException: parameter object not a
ECParameterSpec

 at
org.bouncycastle.jce.provider.JDKKeyPairGenerator$EC.initialize(Unknown
Source)

 at
java.security.KeyPairGenerator.initialize(KeyPairGenerator.java:411)[:1.8.0_45] 




 at
org.apache.sshd.common.kex.ECDH.getE(ECDH.java:58)[5:org.apache.sshd.core:0.14.0] 




 at
org.apache.sshd.server.kex.AbstractDHGServer.init(AbstractDHGServer.java:71)[5:org.apache.sshd.core:0.14.0] 




 at
org.apache.sshd.common.session.AbstractSession.doHandleMessage(AbstractSession.java:390)[5:org.apache.sshd.core:0.14.0] 




 at
org.apache.sshd.common.session.AbstractSession.handleMessage(AbstractSession.java:326)[5:org.apache.sshd.core:0.14.0] 




 at
org.apache.sshd.common.session.AbstractSession.decode(AbstractSession.java:780)[5:org.apache.sshd.core:0.14.0] 




 at
org.apache.sshd.common.session.AbstractSession.messageReceived(AbstractSession.java:308)[5:org.apache.sshd.core:0.14.0] 






This is from a custom distribution of Karafwhen I try the same with
a clean Karaf4 instance, I do not encounter this issue & am able to
login successfully.  I figured it must be one of the etc/*.cfg files I
messed up that's included in the custom distribution.  However, when I
remove all the custom distribution's etc files, I still encounter the
login problem.  Is there something else I can try?

Thanks
Jason

ssh access to Karaf 4.0.4

[Jason Reilly]

Hi all,

I am seeing an exception in the log when I try the following:

$ ssh -p 8101 -l karaf localhost

Connection reset by 127.0.0.1


From the karaf.log file:

2016-03-04 11:12:27,501 | WARN  | f]-nio2-thread-1 | ServerSession  
  | 5 - org.apache.sshd.core - 0.14.0 | Exception caught

java.security.InvalidAlgorithmParameterException: parameter object not a 
ECParameterSpec

at org.bouncycastle.jce.provider.JDKKeyPairGenerator$EC.initialize(Unknown 
Source)

at 
java.security.KeyPairGenerator.initialize(KeyPairGenerator.java:411)[:1.8.0_45]

at 
org.apache.sshd.common.kex.ECDH.getE(ECDH.java:58)[5:org.apache.sshd.core:0.14.0]

at 
org.apache.sshd.server.kex.AbstractDHGServer.init(AbstractDHGServer.java:71)[5:org.apache.sshd.core:0.14.0]

at 
org.apache.sshd.common.session.AbstractSession.doHandleMessage(AbstractSession.java:390)[5:org.apache.sshd.core:0.14.0]

at 
org.apache.sshd.common.session.AbstractSession.handleMessage(AbstractSession.java:326)[5:org.apache.sshd.core:0.14.0]

at 
org.apache.sshd.common.session.AbstractSession.decode(AbstractSession.java:780)[5:org.apache.sshd.core:0.14.0]

at 
org.apache.sshd.common.session.AbstractSession.messageReceived(AbstractSession.java:308)[5:org.apache.sshd.core:0.14.0]



This is from a custom distribution of Karafwhen I try the same with 
a clean Karaf4 instance, I do not encounter this issue & am able to 
login successfully.  I figured it must be one of the etc/*.cfg files I 
messed up that's included in the custom distribution.  However, when I 
remove all the custom distribution's etc files, I still encounter the 
login problem.  Is there something else I can try?


Thanks
Jason

RE: kar repo question

[Pratt, Jason]

Thank you very much, I thought this would be the case but wanted to hear back 
on it.
I’ll give this a go!

Have a good weekend

From: Achim Nierbeck [mailto:bcanh...@googlemail.com]
Sent: Friday, February 26, 2016 10:18 AM
To: user@karaf.apache.org
Subject: Re: kar repo question

Hi Jason,

make sure you have your nexus configured in the
org.ops4j.pax.url.mvn.cfg file.
You'll need to add your own repo in that file.

regards, Achim


2016-02-26 0:05 GMT+01:00 Pratt, Jason 
mailto:jason.pr...@windriver.com>>:
Thank Achim.
Let me try a different approach.
If my bundles are not in the central repo, how can I reference them for a 
bundle:install mvn:my.group using my local Nexus url?

Jason

From: Achim Nierbeck 
[mailto:bcanh...@googlemail.com<mailto:bcanh...@googlemail.com>]
Sent: Thursday, February 25, 2016 1:22 PM
To: user@karaf.apache.org<mailto:user@karaf.apache.org>
Subject: Re: kar repo question

Hi,

you have to differentiate a bit here.
The maven repository is configured in the
etc/org.ops4j.pax.url.mvn.cfg

This is needed if you install bundles with maven coordinates.

To install a set of bundles you have feature definitions (feature.xml) which 
group a bunch
of bundles to be installed in one go, this can also be used to declare 
dependencies between such sets of bundles.
Most of the time bundles in those feature.xmls are referenced via maven 
coordinates.

A Kar file builds on both, it contains feature files and the corresponding 
bundles, so this archive already contains
the bundles referenced in the feature definition. It actually acts more like a 
specialized local maven repository.

regards, Achim


2016-02-25 21:05 GMT+01:00 Pratt, Jason 
mailto:jason.pr...@windriver.com>>:
Hello – I am a bit confused on the setting the repository to pull from. We have 
an internal Nexus that I’d like to use to deploy our bundles from via a KAR 
file.
However, the two htmls
https://karaf.apache.org/manual/latest/users-guide/urls.html
https://karaf.apache.org/manual/latest/users-guide/provisioning.html
do not describe where I would list the URL to our Nexus.

My question is where would I put this URL for the Nexus so that the KAR file 
would pick it up?

Regards,
Jason






--

Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & 
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>

Software Architect / Project Manager / Scrum Master




--

Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & 
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>

Software Architect / Project Manager / Scrum Master

autowire.xml not in manifest.mf

[Pratt, Jason]

Hello - We've switched back to using jar as our packaging type as Jenkins 
wasn't recognizing bundle.  My question/problem is, when we generate the 
manifest the autowire.xml is never included.

We're using these plugins:


 org.apache.aries.blueprint
 blueprint-maven-plugin
 
  
  
  
 
 

 
 org.apache.maven.plugins
 maven-jar-plugin
 2.6
 
  
  
${project.build.outputDirectory}/META-INF/MANIFEST.MF
  
 
 

 
 maven-resources-plugin
 2.7
 
  
  copy-resources
  prepare-package
  
   copy-resources
  
  
   
${project.build.outputDirectory}/OSGI-INF/blueprint
   
   

${basedir}/target/generated-resources/OSGI-INF/blueprint


autowire.xml

   
   
  
  
 
 

  
  org.apache.felix
  maven-bundle-plugin
  
${maven-bundle-plugin.version}
  
   
   bundle-manifest
   
process-classes
   

manifest
   
   
  
  
   
   
jar
   
bundle
   
war
   
   
   
${project.artifactId}
   
${project.version}
   
true
   
!.*.api, 
*;version=${project.version}
   

org.apache.felix.service.command,

org.apache.felix.gogo.commands,

org.apache.karaf.shell.console,

org.apache.karaf.shell.commands,

javax.persistence;version="[1.0.0,2.1.0]",

!javax.transaction,

javax.transaction;version="[1.1,2)",


javax.ws.rs.*;version="[1.1,4)",

org.apache.cxf.*;version="[2,4)",

org.apache.cxf.jaxrs.client,
*
   
   
  
  

What is generated by plugin:

Manifest-Version: 1.0
Bundle-Description: Report OSGi bundle project.
Bundle-SymbolicName: report
Archiver-Version: Plexus Archiver
Built-By: jpratt
Bnd-LastModified: 1456427904864
Bundle-ManifestVersion: 2
Import-Package: 
Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.8))"
Tool: Bnd-3.0.0.201509101326
Export-Package: 
Bundle-Name: WRS Report
Bundle-Version: 1.0.7
Bundle-Blueprint: OSGI-INF/blueprint/cxfReport.xml
Created-By: Apache Maven Bundle Plugin
Build-Jdk: 1.8.0_66

The autowire.xml is not added to the bundle-blueprint section, why? What am I 
doing wrong?

Kind regards,
Jason

RE: kar repo question

[Pratt, Jason]

Thank Achim.
Let me try a different approach.
If my bundles are not in the central repo, how can I reference them for a 
bundle:install mvn:my.group using my local Nexus url?

Jason

From: Achim Nierbeck [mailto:bcanh...@googlemail.com]
Sent: Thursday, February 25, 2016 1:22 PM
To: user@karaf.apache.org
Subject: Re: kar repo question

Hi,

you have to differentiate a bit here.
The maven repository is configured in the
etc/org.ops4j.pax.url.mvn.cfg

This is needed if you install bundles with maven coordinates.

To install a set of bundles you have feature definitions (feature.xml) which 
group a bunch
of bundles to be installed in one go, this can also be used to declare 
dependencies between such sets of bundles.
Most of the time bundles in those feature.xmls are referenced via maven 
coordinates.

A Kar file builds on both, it contains feature files and the corresponding 
bundles, so this archive already contains
the bundles referenced in the feature definition. It actually acts more like a 
specialized local maven repository.

regards, Achim


2016-02-25 21:05 GMT+01:00 Pratt, Jason 
mailto:jason.pr...@windriver.com>>:
Hello – I am a bit confused on the setting the repository to pull from. We have 
an internal Nexus that I’d like to use to deploy our bundles from via a KAR 
file.
However, the two htmls
https://karaf.apache.org/manual/latest/users-guide/urls.html
https://karaf.apache.org/manual/latest/users-guide/provisioning.html
do not describe where I would list the URL to our Nexus.

My question is where would I put this URL for the Nexus so that the KAR file 
would pick it up?

Regards,
Jason






--

Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & 
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>

Software Architect / Project Manager / Scrum Master

kar repo question

[Pratt, Jason]

Hello - I am a bit confused on the setting the repository to pull from. We have 
an internal Nexus that I'd like to use to deploy our bundles from via a KAR 
file.
However, the two htmls
https://karaf.apache.org/manual/latest/users-guide/urls.html
https://karaf.apache.org/manual/latest/users-guide/provisioning.html
do not describe where I would list the URL to our Nexus.

My question is where would I put this URL for the Nexus so that the KAR file 
would pick it up?

Regards,
Jason

RE: does EIK work with 4.0.4?

[Pratt, Jason]

Sure I can take a look and see what I can do to help out.

-Original Message-
From: Jamie G. [mailto:jamie.goody...@gmail.com] 
Sent: Tuesday, February 23, 2016 2:26 PM
To: user@karaf.apache.org
Subject: Re: does EIK work with 4.0.4?

I do not believe its being actively supported at this moment for K4 line.

Any help/support in helping to get EIK functioning for K4 would be appreciated 
:)

On Tue, Feb 23, 2016 at 6:46 PM, Markus Rathgeb  wrote:
> Hello,
> I asked a similar question August 2015:
> https://www.mail-archive.com/user@karaf.apache.org/msg11439.html
>
> The last commit has been done on Aug 13, 2014 
> (https://github.com/apache/karaf-eik/commits/master).
>
> So I don't think there has anything been changed and it is still not 
> working using Karaf 4.x

RE: openjpa 2.4.1

[Pratt, Jason]

Thanks!

From: Christian Schneider [mailto:cschneider...@gmail.com] On Behalf Of 
Christian Schneider
Sent: Wednesday, February 24, 2016 10:12 AM
To: user@karaf.apache.org
Subject: Re: openjpa 2.4.1

He means maven central.
http://search.maven.org/#artifactdetails|org.apache.openjpa|openjpa|2.4.1|bundle

Christian

On 24.02.2016 19:05, Jason Pratt wrote:
central what (repo/website/magic ether)?




[http://ws-promos.appspot.com/ga/pixel.png?yes__count=1&e=5732568548769792]
Get a signature like this: Click 
here!<http://ws-promos.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS9lbWFpbC1pbnN0YWxsP3dzX25jaWQ9NjcyMjk0MDA4JnV0bV9zb3VyY2U9ZXh0ZW5zaW9uJnV0bV9tZWRpdW09ZW1haWwmdXRtX2NhbXBhaWduPXByb21vXzU3MzI1Njg1NDg3Njk3OTIiLCAiZSI6ICI1NzMyNTY4NTQ4NzY5NzkyIn0=&u=340371543099172>

On Wed, Feb 24, 2016 at 12:14 AM, Charlie Mordant 
mailto:cmorda...@gmail.com>> wrote:
Hi,
OpenJPA 2.4.1 is available on central at least until 3 days (I'm using it, and 
I love it ;) ).
Regards,

2016-02-23 21:30 GMT+01:00 Pratt, Jason 
mailto:jason.pr...@windriver.com>>:
Thanks JB for the info!
I guess their moving on a different calendar

-Original Message-
From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net<mailto:j...@nanthrax.net>]
Sent: Monday, February 01, 2016 10:50 AM
To: user@karaf.apache.org<mailto:user@karaf.apache.org>
Subject: Re: openjpa 2.4.1

Yes, Mark (Struberg) and Romain said they gonna release it very soon (this 
week).

Regards
JB

On 02/01/2016 07:42 PM, Pratt, Jason wrote:
> Jb - any response back yet?
>
> jason
>
> *From:*Pratt, Jason
> *Sent:* Tuesday, January 26, 2016 1:46 PM
> *To:* 'user@karaf.apache.org<mailto:user@karaf.apache.org>'
> *Subject:* openjpa 2.4.1
>
> Any idea when this will be released with the version fix so we can use
> it in karaf?
>

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



--
Charlie Mordant

Full OSGI/EE stack made with Karaf: 
https://github.com/OsgiliathEnterprise/net.osgiliath.parent





--

Christian Schneider

http://www.liquid-reality.de



Open Source Architect

http://www.talend.com

Re: openjpa 2.4.1

[Jason Pratt]

central what (repo/website/magic ether)?




Get a signature like this: Click here!
<http://ws-promos.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS9lbWFpbC1pbnN0YWxsP3dzX25jaWQ9NjcyMjk0MDA4JnV0bV9zb3VyY2U9ZXh0ZW5zaW9uJnV0bV9tZWRpdW09ZW1haWwmdXRtX2NhbXBhaWduPXByb21vXzU3MzI1Njg1NDg3Njk3OTIiLCAiZSI6ICI1NzMyNTY4NTQ4NzY5NzkyIn0=&u=340371543099172>

On Wed, Feb 24, 2016 at 12:14 AM, Charlie Mordant 
wrote:

> Hi,
>
> OpenJPA 2.4.1 is available on central at least until 3 days (I'm using it,
> and I love it ;) ).
>
> Regards,
>
> 2016-02-23 21:30 GMT+01:00 Pratt, Jason :
>
>> Thanks JB for the info!
>> I guess their moving on a different calendar
>>
>> -Original Message-
>> From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net]
>> Sent: Monday, February 01, 2016 10:50 AM
>> To: user@karaf.apache.org
>> Subject: Re: openjpa 2.4.1
>>
>> Yes, Mark (Struberg) and Romain said they gonna release it very soon
>> (this week).
>>
>> Regards
>> JB
>>
>> On 02/01/2016 07:42 PM, Pratt, Jason wrote:
>> > Jb - any response back yet?
>> >
>> > jason
>> >
>> > *From:*Pratt, Jason
>> > *Sent:* Tuesday, January 26, 2016 1:46 PM
>> > *To:* 'user@karaf.apache.org'
>> > *Subject:* openjpa 2.4.1
>> >
>> > Any idea when this will be released with the version fix so we can use
>> > it in karaf?
>> >
>>
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
>
>
> --
> Charlie Mordant
>
> Full OSGI/EE stack made with Karaf:
> https://github.com/OsgiliathEnterprise/net.osgiliath.parent
>

does EIK work with 4.0.4?

[Pratt, Jason]

Hello everyone,
I installed the EIK 0.9.0 version in eclipse (Mars1) and it doesn't recognize 
the directory I have karaf-4.0.4 installed in.
Is there something I am missing in the lengthy documentation for this plugin?

Regards,
Jason

RE: openjpa 2.4.1

[Pratt, Jason]

Thanks JB for the info!
I guess their moving on a different calendar

-Original Message-
From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] 
Sent: Monday, February 01, 2016 10:50 AM
To: user@karaf.apache.org
Subject: Re: openjpa 2.4.1

Yes, Mark (Struberg) and Romain said they gonna release it very soon (this 
week).

Regards
JB

On 02/01/2016 07:42 PM, Pratt, Jason wrote:
> Jb - any response back yet?
>
> jason
>
> *From:*Pratt, Jason
> *Sent:* Tuesday, January 26, 2016 1:46 PM
> *To:* 'user@karaf.apache.org'
> *Subject:* openjpa 2.4.1
>
> Any idea when this will be released with the version fix so we can use 
> it in karaf?
>

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

RE: [fixed] Jenkins not recognizing "bundle" packaging

[Pratt, Jason]

I just used the maven resource plugin to move the files I needed.

-Original Message-
From: Pratt, Jason [mailto:jason.pr...@windriver.com] 
Sent: Wednesday, February 03, 2016 11:13 AM
To: user@karaf.apache.org
Subject: RE: Jenkins not recognizing "bundle" packaging

Hi JB - I've tried setting package to "jar" with 


jar
bundle
war


Added to the maven-bundle-plugin, it still is not picking up the autowire.xml 
file from generated-resources\OSGI-INF\blueprint directory generated by the 
blueprint annotations and adding it to the final jar.

Jason

-Original Message-
From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net]
Sent: Tuesday, February 02, 2016 9:21 PM
To: user@karaf.apache.org
Subject: Re: Jenkins not recognizing "bundle" packaging

Hi Jason,

the "bundle" packaging is valid only if you use maven-bundle-plugin extension 
(true).

You can use "jar" package, and define the maven-bundle-plugin with 
supportedType configuration.

Regards
JB

On 02/03/2016 02:48 AM, Pratt, Jason wrote:
> Hello - We're getting a CI system setup to build our bundles for us, 
> the first issue we've encountered is that Jenkins is not recognizing 
> anything with a "bundle".
>
> When we change the packaging to "jar" and use the maven-jar-plugin to 
> copy the manifest over everything appeared to be working correctly. As 
> per the end of 
> http://felix.apache.org/documentation/subprojects/apache-felix-maven-b
> undle-plugin-bnd.html
>
> However, we discovered that the blueprint autowire.xml is never being 
> moved. Has anyone run into this issue before, how did you solve it?
>
> Regards,
>
> Jason
>

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

RE: Jenkins not recognizing "bundle" packaging

[Pratt, Jason]

Hi JB - I've tried setting package to "jar" with 


jar
bundle
war


Added to the maven-bundle-plugin, it still is not picking up the autowire.xml 
file from generated-resources\OSGI-INF\blueprint directory generated by the 
blueprint annotations and adding it to the final jar.

Jason

-Original Message-
From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] 
Sent: Tuesday, February 02, 2016 9:21 PM
To: user@karaf.apache.org
Subject: Re: Jenkins not recognizing "bundle" packaging

Hi Jason,

the "bundle" packaging is valid only if you use maven-bundle-plugin extension 
(true).

You can use "jar" package, and define the maven-bundle-plugin with 
supportedType configuration.

Regards
JB

On 02/03/2016 02:48 AM, Pratt, Jason wrote:
> Hello - We're getting a CI system setup to build our bundles for us, 
> the first issue we've encountered is that Jenkins is not recognizing 
> anything with a "bundle".
>
> When we change the packaging to "jar" and use the maven-jar-plugin to 
> copy the manifest over everything appeared to be working correctly. As 
> per the end of 
> http://felix.apache.org/documentation/subprojects/apache-felix-maven-b
> undle-plugin-bnd.html
>
> However, we discovered that the blueprint autowire.xml is never being 
> moved. Has anyone run into this issue before, how did you solve it?
>
> Regards,
>
> Jason
>

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

Jenkins not recognizing "bundle" packaging

[Pratt, Jason]

Hello - We're getting a CI system setup to build our bundles for us, the first 
issue we've encountered is that Jenkins is not recognizing anything with a 
"bundle".

When we change the packaging to "jar" and use the maven-jar-plugin to copy the 
manifest over everything appeared to be working correctly. As per the end of 
http://felix.apache.org/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html

However, we discovered that the blueprint autowire.xml is never being moved. 
Has anyone run into this issue before, how did you solve it?

Regards,
Jason

RE: openjpa 2.4.1

[Pratt, Jason]

Jb - any response back yet?

jason

From: Pratt, Jason
Sent: Tuesday, January 26, 2016 1:46 PM
To: 'user@karaf.apache.org'
Subject: openjpa 2.4.1

Any idea when this will be released with the version fix so we can use it in 
karaf?

openjpa 2.4.1

[Pratt, Jason]

Any idea when this will be released with the version fix so we can use it in 
karaf?

karaf 4.0.4 clean not working

[Pratt, Jason]

The clean flag is not working for bin/karaf or bin/start on linux and win7
When used all files/directories still remain in the data directory

Re: Karaf 4.0.3 & JPA

[Jason Reilly]

FWIW, I rebundled OpenJPA with the 
javax.transaction/javax.transaction-api/1.2 dependency & I am now able 
to successfully connect to the database.


Thanks again,
Jason


On 11/30/2015 10:56 AM, Christian Schneider wrote:
Ah .. sorry forgot that you use openjpa. This might be difficult as 
openjpa is incompatible to jta 1.2 which the transaction.blueprint 
2.0.0 requires.
In this case you will probably need to create your own transaction 
feature that skips the 2.0.0 version and only relies on jta 1.1.


I guess because of openjpa karaf installed jta 1.1 and 1.2. 
Unfortunately it does not work to install both.


Another option would be to rebundle openjpa as in fact it is 
compatible to jta 1.2 and only the import package version range is too 
small. As the openjpa guys have still not fixed this
I wonder if we should even do the rebundling at karaf or servicemix. 
On the other hand I still hope that they fix this.


Christian

On 30.11.2015 16:47, Jason Reilly wrote:
I gave that a whirl...specifically, I changed the bootFeatures to the 
following:


jdbc

transaction

jpa

openjpa/${openjpa.version}

hearsay-commons




Upon startup of the custom distro, I see the following from a list 
command:


151 | Resolved |  80 | 2.4.0  | OpenJPA Aggregate Jar


There is an exception in the karaf.log:

org.apache.karaf.features.internal.util.MultiException: Error 
restarting bundles


at 
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:844)[7:org.apache.karaf.features.core:4.0.3]


at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1079)[7:org.apache.karaf.features.core:4.0.3]


at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:975)[7:org.apache.karaf.features.core:4.0.3]


at 
java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_45]


at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_45]


at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_45]


at java.lang.Thread.run(Thread.java:745)[:1.8.0_45]

Caused by: org.osgi.framework.BundleException: Activator start error 
in bundle org.apache.openjpa [151].


at 
org.apache.felix.framework.Felix.activateBundle(Felix.java:2276)[org.apache.felix.framework-5.4.0.jar:]


at 
org.apache.felix.framework.Felix.startBundle(Felix.java:2144)[org.apache.felix.framework-5.4.0.jar:]


at 
org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)[org.apache.felix.framework-5.4.0.jar:]


at 
org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)[org.apache.felix.framework-5.4.0.jar:]


at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1189)[7:org.apache.karaf.features.core:4.0.3]


at 
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:836)[7:org.apache.karaf.features.core:4.0.3]


... 6 more

Caused by: java.lang.NoClassDefFoundError: 
javax/transaction/SystemException


at 
org.apache.openjpa.persistence.osgi.PersistenceActivator.start(PersistenceActivator.java:61)


at 
org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)


at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226)

... 11 more

Caused by: java.lang.ClassNotFoundException: 
javax.transaction.SystemException not found by org.apache.openjpa [151]


at 
org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1574)[org.apache.felix.framework-5.4.0.jar:]


at 
org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:79)[org.apache.felix.framework-5.4.0.jar:]


at 
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2018)[org.apache.felix.framework-5.4.0.jar:]


at java.lang.ClassLoader.loadClass(ClassLoader.java:357)[:1.8.0_45]


However, the transaction packages are visible:

karaf@root()> exports | grep javax.transaction

javax.transaction.xa | 0.0.0| 0   | 
org.apache.felix.framework


javax.transaction.xa | 1.1.0| 119 | 
org.apache.geronimo.specs.geronimo-jta_1.1_spec


javax.transaction.xa | 1.2.0| 30  | javax.transaction-api

javax.transaction | 0.0.0| 0   | org.apache.felix.framework

javax.transaction | 1.1.0| 119 | 
org.apache.geronimo.specs.geronimo-jta_1.1_spec


javax.transaction | 1.2.0| 30  | javax.transaction-api


Regards,
Jason

On 11/30/2015 10:31 AM, Christian Schneider wrote:

On 30.11.2015 16:13, Jason Reilly wrote:

Thanks Christian,



Then in the pom.xml for building the custom distribution, I have 
the following relevant bootFeatures:


aries-blueprint

cxf

jdbc

transaction-api/1.1.0
This is wro

Re: Karaf 4.0.3 & JPA

[Jason Reilly]

On 11/30/2015 12:33 PM, Christian Schneider wrote:

No idea why the namespace handler does not seem to be present.

You can look through the bundles with la -s and check if the 
transaction blueprint 2.0.0 bundle is present.


karaf@root()> la -s | grep transaction

 31 | Active   |  80 | 1.2 | javax.transaction-api

 59 | Active   |  80 | 1.1.1   | 
org.apache.aries.transaction.blueprint

 60 | Active   |  80 | 2.0.0   | 
org.apache.aries.transaction.blueprint

 61 | Active   |  80 | 1.3.0   | 
org.apache.aries.transaction.manager


You can then do bundle:service -p  to see which services it 
offers. It should offer the correct blueprint namespace handler.


karaf@root()> bundle:services -p 60

Apache Aries Transaction Blueprint (60) provides:

-

objectClass = [org.osgi.service.blueprint.container.BlueprintContainer]

osgi.blueprint.container.symbolicname = org.apache.aries.transaction.blueprint

osgi.blueprint.container.version = 2.0.0

service.bundleid = 60

service.id = 201

service.scope = singleton



objectClass = [org.apache.aries.blueprint.NamespaceHandler]

osgi.service.blueprint.compname = nsHandler

osgi.service.blueprint.namespace = 
http://aries.apache.org/xmlns/transactions/v2.0.0

service.bundleid = 60

service.id = 273

service.scope = bundle


That all looks good.

If just the EntityManager is missing then maybe the DataSource is not 
present or the persistence unit bundle is not correctly identified.
You should see in the log if a persistence unit is found in a bundle 
and what it is waiting for.


I am deploying the datasource as a bundle & seems to be registered fine:

karaf@root()> service:list javax.sql.DataSource

[javax.sql.DataSource]

--

 osgi.jndi.service.name = hearsayNoJTA

 osgi.service.blueprint.compname = hearsay-ds-no-jta

 service.bundleid = 268

 service.id = 269

 service.scope = bundle

Provided by :

 Hearsay :: Datasource (268)

[javax.sql.DataSource]

--

 osgi.jndi.service.name = hearsayJTA

 osgi.service.blueprint.compname = hearsay-ds-jta

 service.bundleid = 268

 service.id = 270

 service.scope = bundle

Provided by :

 Hearsay :: Datasource (268)


The persistence.xml file has the following:

  
org.eclipse.persistence.jpa.PersistenceProvider

osgi:service/javax.sql.DataSource/(osgi.jndi.service.name=hearsayJTA)
osgi:service/javax.sql.DataSource/(osgi.jndi.service.name=hearsayNoJTA)


I think this configuration all lines up, so I am leaning towards the 
"persistence unit bundle is not correctly identified" idea.  The dao 
impl bundle finally fails with the following exception:


2015-11-30 12:25:48,287 | ERROR | rint Extender: 2 | BlueprintContainerImpl 
  | 39 - org.apache.aries.blueprint.core - 1.4.5 | Unable to start blueprint 
container for bundle hearsay-dao-jpa/0.0.46.SNAPSHOT due to unresolved dependencies 
[(&(osgi.unit.name=hearsay)(objectClass=javax.persistence.EntityManager))]

java.util.concurrent.TimeoutException

at 
org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:343)[39:org.apache.aries.blueprint.core:1.4.5]

at 
org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)[39:org.apache.aries.blueprint.core:1.4.5]


Is there something else I should be looking for?

Thanks,
Jason

Re: Karaf 4.0.3 & JPA

[Jason Reilly]

Thanks Christian,

I will try repackaging openjpa.

Switching gears a little, I have a couple of branches where I am 
flushing out these Karaf4/JPA woes.  One branch uses openjpa & another 
uses eclipselink.  Switching over to the eclipselink branch, I have the 
following configuration message in the karaf.log:


2015-11-30 11:54:56,746 | INFO  | rint Extender: 3 | BlueprintContainerImpl 
  | 39 - org.apache.aries.blueprint.core - 1.4.5 | Bundle 
hearsay-dao-jpa/0.0.46.SNAPSHOT is waiting for namespace handlers 
[http://aries.apache.org/xmlns/transactions/v2.0.0]

2015-11-30 11:54:56,779 | INFO  | rint Extender: 1 | BlueprintContainerImpl 
  | 39 - org.apache.aries.blueprint.core - 1.4.5 | Bundle 
hearsay-dao-jpa/0.0.46.SNAPSHOT is waiting for dependencies 
[(&(osgi.unit.name=hearsay)(objectClass=javax.persistence.EntityManager))]


This branch more closely resembles the 
KarafTutorial/tasklist-blueprint-cdi project.  Here are the details...


From the custom distro pom.xml file's bootFeatures:

pax-cdi

jdbc

transaction

jpa

eclipselink

hearsay-commons




From the BaseDAO class:

@PersistenceContext(unitName = "hearsay")

private EntityManager em;


From the blueprint.xml file:

http://www.osgi.org/xmlns/blueprint/v1.0.0"; 
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0";

  xmlns:tx="http://aries.apache.org/xmlns/transactions/v2.0.0"; 
xmlns:jpa="http://aries.apache.org/xmlns/jpa/v2.0.0";>

  

  

  

  




As with the openjpa branch, all the bundles are active upon bootup, but 
when I install the "hearsay-dao" feature, the dao impl bundle is in a 
graceperiod state.  When I rollback the transaction namespace in the 
blueprint.xml file to 1.2.0 & use 'enable-annotations' instead of 
'enable', I get only the following message in the karaf.log:


2015-11-30 12:20:48,312 | INFO  | pool-64-thread-1 | BlueprintContainerImpl 
  | 39 - org.apache.aries.blueprint.core - 1.4.5 | Bundle 
hearsay-dao-jpa/0.0.46.SNAPSHOT is waiting for dependencies 
[(&(osgi.unit.name=hearsay)(objectClass=javax.persistence.EntityManager))]


Do you have suggestions for this scenario?

Thanks,
Jason

Re: Karaf 4.0.3 & JPA

[Jason Reilly]

I gave that a whirl...specifically, I changed the bootFeatures to the 
following:


jdbc

transaction

jpa

openjpa/${openjpa.version}

hearsay-commons




Upon startup of the custom distro, I see the following from a list command:

151 | Resolved |  80 | 2.4.0  | OpenJPA Aggregate Jar


There is an exception in the karaf.log:

org.apache.karaf.features.internal.util.MultiException: Error restarting bundles

at 
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:844)[7:org.apache.karaf.features.core:4.0.3]

at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1079)[7:org.apache.karaf.features.core:4.0.3]

at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:975)[7:org.apache.karaf.features.core:4.0.3]

at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_45]

at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_45]

at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_45]

at java.lang.Thread.run(Thread.java:745)[:1.8.0_45]

Caused by: org.osgi.framework.BundleException: Activator start error in bundle 
org.apache.openjpa [151].

at 
org.apache.felix.framework.Felix.activateBundle(Felix.java:2276)[org.apache.felix.framework-5.4.0.jar:]

at 
org.apache.felix.framework.Felix.startBundle(Felix.java:2144)[org.apache.felix.framework-5.4.0.jar:]

at 
org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)[org.apache.felix.framework-5.4.0.jar:]

at 
org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)[org.apache.felix.framework-5.4.0.jar:]

at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1189)[7:org.apache.karaf.features.core:4.0.3]

at 
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:836)[7:org.apache.karaf.features.core:4.0.3]

... 6 more

Caused by: java.lang.NoClassDefFoundError: javax/transaction/SystemException

at 
org.apache.openjpa.persistence.osgi.PersistenceActivator.start(PersistenceActivator.java:61)

at 
org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)

at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226)

... 11 more

Caused by: java.lang.ClassNotFoundException: javax.transaction.SystemException 
not found by org.apache.openjpa [151]

at 
org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1574)[org.apache.felix.framework-5.4.0.jar:]

at 
org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:79)[org.apache.felix.framework-5.4.0.jar:]

at 
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2018)[org.apache.felix.framework-5.4.0.jar:]

at java.lang.ClassLoader.loadClass(ClassLoader.java:357)[:1.8.0_45]


However, the transaction packages are visible:

karaf@root()> exports | grep javax.transaction

javax.transaction.xa
   | 0.0.0| 0   | org.apache.felix.framework

javax.transaction.xa
   | 1.1.0| 119 | 
org.apache.geronimo.specs.geronimo-jta_1.1_spec

javax.transaction.xa
   | 1.2.0| 30  | javax.transaction-api

javax.transaction   
   | 0.0.0| 0   | org.apache.felix.framework

javax.transaction   
   | 1.1.0| 119 | 
org.apache.geronimo.specs.geronimo-jta_1.1_spec

javax.transaction   
   | 1.2.0| 30  | javax.transaction-api


Regards,
Jason

On 11/30/2015 10:31 AM, Christian Schneider wrote:

On 30.11.2015 16:13, Jason Reilly wrote:

Thanks Christian,



Then in the pom.xml for building the custom distribution, I have the 
following relevant bootFeatures:


aries-blueprint

cxf

jdbc

transaction-api/1.1.0
This is wrong. You need to install the "transaction" feature. This is 
just the API.
Also for transaction you do not need to specify a version. The feature 
will install the old and the new transaction blueprint bundle.




jpa/1.0.4
Also not sure about this one. As you use the annotations there you 
could as well install the "jpa" feature which will give you the new 
2.x version.


openjpa/${openjpa.version}



Christian

Re: Karaf 4.0.3 & JPA

[Jason Reilly]

Thanks Christian,

Based on this info, I have changed the blueprint xml to the following:

http://www.osgi.org/xmlns/blueprint/v1.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:tx="http://aries.apache.org/xmlns/transactions/v1.2.0";

  xmlns:jpa="http://aries.apache.org/xmlns/jpa/v1.1.0";>

  

  



  


...snip...



And in my BaseDAO class, I have the following:

@PersistenceContext(name = "hearsay", unitName = "hearsay")

private EntityManager entityManager;


Then in the pom.xml for building the custom distribution, I have the 
following relevant bootFeatures:


aries-blueprint

cxf

jdbc

transaction-api/1.1.0

jpa/1.0.4

openjpa/${openjpa.version}

hearsay-commons




At this point, when Karaf 4.0.3 starts up, there are no 
errors/warningsall looks good.  Then I run, 'feature:install 
hearsay:dao', which installs the dao api & impl bundles.  The api is 
active, but the impl is in a graceperiod state.  The log has the following:


2015-11-30 09:46:39,881 | INFO  | pool-51-thread-1 | BlueprintContainerImpl 
  | 37 - org.apache.aries.blueprint.core - 1.4.5 | Bundle 
hearsay-dao-jpa/0.0.46.SNAPSHOT is waiting for namespace handlers 
[http://aries.apache.org/xmlns/transactions/v1.2.0]


What am I missing?

Thanks,
Jason


On 11/25/2015 02:05 AM, Christian Schneider wrote:
The old namespace for jpa is not supported anymore by Aries JPA 2.x. 
Can you try with the new namespaces like used in my

tutorial code? You will need to use annoations then.

For transactions you can still use the old namespace but I would also 
recommend the new one.


Christian


On 24.11.2015 17:22, Jason Reilly wrote:



http://www.osgi.org/xmlns/blueprint/v1.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:tx="http://aries.apache.org/xmlns/transactions/v1.0.0";


  xmlns:jpa="http://aries.apache.org/xmlns/jpa/v1.0.0"; 
default-activation="eager">


  class="org.renci.hearsay.dao.jpa.AlignmentDAOImpl">






  

...snip

  interface="org.renci.hearsay.dao.AlignmentDAO" />


...snip

  class="org.renci.hearsay.dao.HearsayDAOBean">




...snip

  

  interface="org.renci.hearsay.dao.HearsayDAOBeanService" />





On 11/24/2015 11:19 AM, Jean-Baptiste Onofré wrote:

Can you share the blueprint XML in your hearsay-dao-jpa bundle ?

On 11/24/2015 04:57 PM, Jason Reilly wrote:

I tried 1.0.0 for those urls & here is the error message:

2015-11-24 10:56:12,317 | INFO  | pool-47-thread-1 |
BlueprintContainerImpl   | 34 - 
org.apache.aries.blueprint.core

- 1.4.5 | Bundle hearsay-dao-jpa/0.0.46.SNAPSHOT is waiting for
namespace handlers [http://aries.apache.org/xmlns/transactions/v1.0.0,
http://aries.apache.org/xmlns/jpa/v1.0.0]


On 11/24/2015 10:55 AM, Jason Reilly wrote:

I gave that a whirl...here are the details:

In my pom.xml which builds my custom Karaf distribution:

...snip..

 

feature

shell

bundle

config

diagnostic

instance

jaas

log

package

service

system

ssh

management

deployer

obr

http

war

jetty

scr

jndi

aries-blueprint

cxf

jdbc

transaction-api/1.1.0

openjpa/${openjpa.version}

spring/${spring.version}_1

spring-orm/${spring.version}_1

spring-web/${spring.version}_1

hearsay-commons



  

...snip...


From the Karaf prompt:

karaf@root()> list

START LEVEL 100 , List Threshold: 50

 ID | State  | Lvl | Version| Name

-- 




  8 | Active |  80 | 1.5.0  | OPS4J Base - Lang

  9 | Active |  80 | 1.5.0  | OPS4J Base - Service
Provider Access

 10 | Active |  80 | 0.7.0  | OPS4J Pax JDBC Generic
Driver Extender

 11 | Active |  80 | 0.7.0  | OPS4J Pax JDBC Config

 12 | Active |  80 | 1.8.1  | OPS4J Pax Swissbox :: 
OSGi Core


 13 | Active |  80 | 1.8.1  | OPS4J Pax Swissbox :: 
Extender


 14 | Active |  80 | 1.8.1  | OPS4J Pax Swissbox :: 
Lifecycle


 15 | Active |  80 | 1.0.0.201505202023 | 
org.osgi:org.osgi.service.jdbc


 16 | Active |  80 | 2.4.1  | Jackson-annotations

 17 | Active |  80 | 2.4.1  | Jackson-core

 18 | Active |  80 | 2.4.1  | jackson-databind

 19 | Active |  80 | 2.4.1  | Jackson-JAXRS-base

 20 | Active |  80 | 2.4.1  | Jackson-JAXRS-JSON

 21 | Active |  80 | 2.4.1  | 
Jackson-module-JAXB-annotations


 27

Re: Karaf 4.0.3 & JPA

[Jason Reilly]

http://www.osgi.org/xmlns/blueprint/v1.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:tx="http://aries.apache.org/xmlns/transactions/v1.0.0";

  xmlns:jpa="http://aries.apache.org/xmlns/jpa/v1.0.0"; 
default-activation="eager">

  





  

...snip

  

...snip

  



...snip

  

  




On 11/24/2015 11:19 AM, Jean-Baptiste Onofré wrote:

Can you share the blueprint XML in your hearsay-dao-jpa bundle ?

On 11/24/2015 04:57 PM, Jason Reilly wrote:

I tried 1.0.0 for those urls & here is the error message:

2015-11-24 10:56:12,317 | INFO  | pool-47-thread-1 |
BlueprintContainerImpl   | 34 - org.apache.aries.blueprint.core
- 1.4.5 | Bundle hearsay-dao-jpa/0.0.46.SNAPSHOT is waiting for
namespace handlers [http://aries.apache.org/xmlns/transactions/v1.0.0,
http://aries.apache.org/xmlns/jpa/v1.0.0]


On 11/24/2015 10:55 AM, Jason Reilly wrote:

I gave that a whirl...here are the details:

In my pom.xml which builds my custom Karaf distribution:

...snip..

 

feature

shell

bundle

config

diagnostic

instance

jaas

log

package

service

system

ssh

management

deployer

obr

http

war

jetty

scr

jndi

aries-blueprint

cxf

jdbc

transaction-api/1.1.0

openjpa/${openjpa.version}

spring/${spring.version}_1

spring-orm/${spring.version}_1

spring-web/${spring.version}_1

hearsay-commons



  

...snip...


From the Karaf prompt:

karaf@root()> list

START LEVEL 100 , List Threshold: 50

 ID | State  | Lvl | Version| Name

-- 




  8 | Active |  80 | 1.5.0  | OPS4J Base - Lang

  9 | Active |  80 | 1.5.0  | OPS4J Base - Service
Provider Access

 10 | Active |  80 | 0.7.0  | OPS4J Pax JDBC Generic
Driver Extender

 11 | Active |  80 | 0.7.0  | OPS4J Pax JDBC Config

 12 | Active |  80 | 1.8.1  | OPS4J Pax Swissbox :: OSGi 
Core


 13 | Active |  80 | 1.8.1  | OPS4J Pax Swissbox :: 
Extender


 14 | Active |  80 | 1.8.1  | OPS4J Pax Swissbox :: 
Lifecycle


 15 | Active |  80 | 1.0.0.201505202023 | 
org.osgi:org.osgi.service.jdbc


 16 | Active |  80 | 2.4.1  | Jackson-annotations

 17 | Active |  80 | 2.4.1  | Jackson-core

 18 | Active |  80 | 2.4.1  | jackson-databind

 19 | Active |  80 | 2.4.1  | Jackson-JAXRS-base

 20 | Active |  80 | 2.4.1  | Jackson-JAXRS-JSON

 21 | Active |  80 | 2.4.1  | 
Jackson-module-JAXB-annotations


 27 | Active |  80 | 1.1.0.Final| Bean Validation API

 49 | Active |  80 | 1.8.3  | Commons BeanUtils

 50 | Active |  80 | 1.2| Commons CLI

 52 | Active |  80 | 3.2.1  | Commons Collections

 53 | Active |  80 | 4.0.0  | Apache Commons Collections

 54 | Active |  80 | 1.4.0  | Commons Compress

 55 | Active |  80 | 0.5| Commons Discovery

 56 | Active |  80 | 1.3.1  | Commons Email

 57 | Active |  80 | 2.4.0  | Commons IO

 59 | Active |  80 | 3.4.0  | Apache Commons Lang

 60 | Active |  80 | 3.5.0  | Apache Commons Math

 61 | Active |  80 | 3.3.0  | Commons Net

 62 | Active |  80 | 1.5.6  | Commons Pool

105 | Active |  80 | 1.1.1  | geronimo-jms_1.1_spec

106 | Active |  80 | 1.1| Apache Geronimo JSR-317 JPA
2.0 Spec API

107 | Active |  80 | 1.1.1  | geronimo-jta_1.1_spec

123 | Active |  80 | 4.0.3  | Apache Karaf :: JDBC :: Core

137 | Active |  80 | 2.0.9  | Apache MINA Core

139 | Active |  80 | 2.4.0  | OpenJPA Aggregate Jar

141 | Active |  80 | 1.7.0.6| Apache ServiceMix :: Bundles
:: ant

143 | Active |  80 | 1.7.4.1| Apache ServiceMix :: Bundles
:: aspectj

145 | Active |  80 | 1.4.0.3| Apache ServiceMix :: Bundles
:: commons-dbcp

154 | Active |  80 | 1.14.1.1   | Apache ServiceMix :: Bundles
:: serp

162 | Active |  80 | 1.3.2.RELEASE_2| Apache ServiceMix :: Bundles
:: spring-ldap

180 | Active |  80 | 4.3.0  | Apache XBean :: ASM 5 shaded
(repackaged)

229 | Active |  80 | 9.4.0.build-1205   | PostgreSQL JDBC Driver JDBC41

230 | Active |  80 | 2.2.7.RELEASE  | Spring Batch Core

231 | Active |  80 | 2.2.7.RELEASE  | Spring Batch Infrastructure

232 | Active |  80 | 1.4.1.RELEASE  | Spring Data Commons Core

237 | Active |  80 | 3.2.8.RELEASE  | Spring Security LDAP

242 | Active |  80 | 0.0.1 

Re: Karaf 4.0.3 & JPA

[Jason Reilly]

I tried 1.0.0 for those urls & here is the error message:

2015-11-24 10:56:12,317 | INFO  | pool-47-thread-1 | BlueprintContainerImpl 
  | 34 - org.apache.aries.blueprint.core - 1.4.5 | Bundle 
hearsay-dao-jpa/0.0.46.SNAPSHOT is waiting for namespace handlers 
[http://aries.apache.org/xmlns/transactions/v1.0.0, 
http://aries.apache.org/xmlns/jpa/v1.0.0]


On 11/24/2015 10:55 AM, Jason Reilly wrote:

I gave that a whirl...here are the details:

In my pom.xml which builds my custom Karaf distribution:

...snip..

 

feature

shell

bundle

config

diagnostic

instance

jaas

log

package

service

system

ssh

management

deployer

obr

http

war

jetty

scr

jndi

aries-blueprint

cxf

jdbc

transaction-api/1.1.0

openjpa/${openjpa.version}

spring/${spring.version}_1

spring-orm/${spring.version}_1

spring-web/${spring.version}_1

hearsay-commons



  

...snip...


From the Karaf prompt:

karaf@root()> list

START LEVEL 100 , List Threshold: 50

 ID | State  | Lvl | Version| Name

-- 



  8 | Active |  80 | 1.5.0  | OPS4J Base - Lang

  9 | Active |  80 | 1.5.0  | OPS4J Base - Service 
Provider Access


 10 | Active |  80 | 0.7.0  | OPS4J Pax JDBC Generic 
Driver Extender


 11 | Active |  80 | 0.7.0  | OPS4J Pax JDBC Config

 12 | Active |  80 | 1.8.1  | OPS4J Pax Swissbox :: OSGi Core

 13 | Active |  80 | 1.8.1  | OPS4J Pax Swissbox :: Extender

 14 | Active |  80 | 1.8.1  | OPS4J Pax Swissbox :: Lifecycle

 15 | Active |  80 | 1.0.0.201505202023 | org.osgi:org.osgi.service.jdbc

 16 | Active |  80 | 2.4.1  | Jackson-annotations

 17 | Active |  80 | 2.4.1  | Jackson-core

 18 | Active |  80 | 2.4.1  | jackson-databind

 19 | Active |  80 | 2.4.1  | Jackson-JAXRS-base

 20 | Active |  80 | 2.4.1  | Jackson-JAXRS-JSON

 21 | Active |  80 | 2.4.1  | Jackson-module-JAXB-annotations

 27 | Active |  80 | 1.1.0.Final| Bean Validation API

 49 | Active |  80 | 1.8.3  | Commons BeanUtils

 50 | Active |  80 | 1.2| Commons CLI

 52 | Active |  80 | 3.2.1  | Commons Collections

 53 | Active |  80 | 4.0.0  | Apache Commons Collections

 54 | Active |  80 | 1.4.0  | Commons Compress

 55 | Active |  80 | 0.5| Commons Discovery

 56 | Active |  80 | 1.3.1  | Commons Email

 57 | Active |  80 | 2.4.0  | Commons IO

 59 | Active |  80 | 3.4.0  | Apache Commons Lang

 60 | Active |  80 | 3.5.0  | Apache Commons Math

 61 | Active |  80 | 3.3.0  | Commons Net

 62 | Active |  80 | 1.5.6  | Commons Pool

105 | Active |  80 | 1.1.1  | geronimo-jms_1.1_spec

106 | Active |  80 | 1.1| Apache Geronimo JSR-317 JPA 
2.0 Spec API


107 | Active |  80 | 1.1.1  | geronimo-jta_1.1_spec

123 | Active |  80 | 4.0.3  | Apache Karaf :: JDBC :: Core

137 | Active |  80 | 2.0.9  | Apache MINA Core

139 | Active |  80 | 2.4.0  | OpenJPA Aggregate Jar

141 | Active |  80 | 1.7.0.6| Apache ServiceMix :: Bundles 
:: ant


143 | Active |  80 | 1.7.4.1| Apache ServiceMix :: Bundles 
:: aspectj


145 | Active |  80 | 1.4.0.3| Apache ServiceMix :: Bundles 
:: commons-dbcp


154 | Active |  80 | 1.14.1.1   | Apache ServiceMix :: Bundles 
:: serp


162 | Active |  80 | 1.3.2.RELEASE_2| Apache ServiceMix :: Bundles 
:: spring-ldap


180 | Active |  80 | 4.3.0  | Apache XBean :: ASM 5 shaded 
(repackaged)


229 | Active |  80 | 9.4.0.build-1205   | PostgreSQL JDBC Driver JDBC41

230 | Active |  80 | 2.2.7.RELEASE  | Spring Batch Core

231 | Active |  80 | 2.2.7.RELEASE  | Spring Batch Infrastructure

232 | Active |  80 | 1.4.1.RELEASE  | Spring Data Commons Core

237 | Active |  80 | 3.2.8.RELEASE  | Spring Security LDAP

242 | Active |  80 | 0.0.1  | RENCI :: OSGi :: Bundle :: 
XZ 1.0




At this point, everything looks good.  Then I install the hearsay-dao 
feature & the list command shows the following additional bundles:


243 | Active  |  80 | 0.0.46.SNAPSHOT| Hearsay :: DAO :: API

244 | GracePeriod |  80 | 0.0.46.SNAPSHOT| Hearsay :: DAO :: JPA

245 | Active  |  80 | 0.0.46.SNAPSHOT| Hearsay :: Datasource


From the karaf.log file, I see the following:

2015-11-24 10:51:15,958 | INFO  | pool-48-thread-1 | 
BlueprintCo

Re: Karaf 4.0.3 & JPA

[Jason Reilly]

I gave that a whirl...here are the details:

In my pom.xml which builds my custom Karaf distribution:

...snip..

 

feature

shell

bundle

config

diagnostic

instance

jaas

log

package

service

system

ssh

management

deployer

obr

http

war

jetty

scr

jndi

aries-blueprint

cxf

jdbc

transaction-api/1.1.0

openjpa/${openjpa.version}

spring/${spring.version}_1

spring-orm/${spring.version}_1

spring-web/${spring.version}_1

hearsay-commons



  

...snip...


From the Karaf prompt:

karaf@root()> list

START LEVEL 100 , List Threshold: 50

 ID | State  | Lvl | Version| Name

--

  8 | Active |  80 | 1.5.0  | OPS4J Base - Lang

  9 | Active |  80 | 1.5.0  | OPS4J Base - Service Provider Access

 10 | Active |  80 | 0.7.0  | OPS4J Pax JDBC Generic Driver Extender

 11 | Active |  80 | 0.7.0  | OPS4J Pax JDBC Config

 12 | Active |  80 | 1.8.1  | OPS4J Pax Swissbox :: OSGi Core

 13 | Active |  80 | 1.8.1  | OPS4J Pax Swissbox :: Extender

 14 | Active |  80 | 1.8.1  | OPS4J Pax Swissbox :: Lifecycle

 15 | Active |  80 | 1.0.0.201505202023 | org.osgi:org.osgi.service.jdbc

 16 | Active |  80 | 2.4.1  | Jackson-annotations

 17 | Active |  80 | 2.4.1  | Jackson-core

 18 | Active |  80 | 2.4.1  | jackson-databind

 19 | Active |  80 | 2.4.1  | Jackson-JAXRS-base

 20 | Active |  80 | 2.4.1  | Jackson-JAXRS-JSON

 21 | Active |  80 | 2.4.1  | Jackson-module-JAXB-annotations

 27 | Active |  80 | 1.1.0.Final| Bean Validation API

 49 | Active |  80 | 1.8.3  | Commons BeanUtils

 50 | Active |  80 | 1.2| Commons CLI

 52 | Active |  80 | 3.2.1  | Commons Collections

 53 | Active |  80 | 4.0.0  | Apache Commons Collections

 54 | Active |  80 | 1.4.0  | Commons Compress

 55 | Active |  80 | 0.5| Commons Discovery

 56 | Active |  80 | 1.3.1  | Commons Email

 57 | Active |  80 | 2.4.0  | Commons IO

 59 | Active |  80 | 3.4.0  | Apache Commons Lang

 60 | Active |  80 | 3.5.0  | Apache Commons Math

 61 | Active |  80 | 3.3.0  | Commons Net

 62 | Active |  80 | 1.5.6  | Commons Pool

105 | Active |  80 | 1.1.1  | geronimo-jms_1.1_spec

106 | Active |  80 | 1.1| Apache Geronimo JSR-317 JPA 2.0 Spec 
API

107 | Active |  80 | 1.1.1  | geronimo-jta_1.1_spec

123 | Active |  80 | 4.0.3  | Apache Karaf :: JDBC :: Core

137 | Active |  80 | 2.0.9  | Apache MINA Core

139 | Active |  80 | 2.4.0  | OpenJPA Aggregate Jar

141 | Active |  80 | 1.7.0.6| Apache ServiceMix :: Bundles :: ant

143 | Active |  80 | 1.7.4.1| Apache ServiceMix :: Bundles :: 
aspectj

145 | Active |  80 | 1.4.0.3| Apache ServiceMix :: Bundles :: 
commons-dbcp

154 | Active |  80 | 1.14.1.1   | Apache ServiceMix :: Bundles :: serp

162 | Active |  80 | 1.3.2.RELEASE_2| Apache ServiceMix :: Bundles :: 
spring-ldap

180 | Active |  80 | 4.3.0  | Apache XBean :: ASM 5 shaded 
(repackaged)

229 | Active |  80 | 9.4.0.build-1205   | PostgreSQL JDBC Driver JDBC41

230 | Active |  80 | 2.2.7.RELEASE  | Spring Batch Core

231 | Active |  80 | 2.2.7.RELEASE  | Spring Batch Infrastructure

232 | Active |  80 | 1.4.1.RELEASE  | Spring Data Commons Core

237 | Active |  80 | 3.2.8.RELEASE  | Spring Security LDAP

242 | Active |  80 | 0.0.1  | RENCI :: OSGi :: Bundle :: XZ 1.0



At this point, everything looks good.  Then I install the hearsay-dao 
feature & the list command shows the following additional bundles:


243 | Active  |  80 | 0.0.46.SNAPSHOT| Hearsay :: DAO :: API

244 | GracePeriod |  80 | 0.0.46.SNAPSHOT| Hearsay :: DAO :: JPA

245 | Active  |  80 | 0.0.46.SNAPSHOT| Hearsay :: Datasource


From the karaf.log file, I see the following:

2015-11-24 10:51:15,958 | INFO  | pool-48-thread-1 | BlueprintContainerImpl 
  | 34 - org.apache.aries.blueprint.core - 1.4.5 | Bundle 
hearsay-dao-jpa/0.0.46.SNAPSHOT is waiting for namespace handlers 
[http://aries.apache.org/xmlns/transactions/v1.1.0, 
http://aries.apache.org/xmlns/jpa/v1.1.0]


Should the Aries transaction/jpa versions be 1.0.0 instead?

Thanks,
Jason

On 11/24/2015 10:22 AM, Jean-Baptiste Onofré wrote:
Basically, you should have transaction-api 1.1.0 in

Re: Karaf 4.0.3 & JPA

[Jason Reilly]

For hibernate & eclipselink, I was specifying transaction-api/1.2.0.  
For openjpa, I was using transaction-api/1.1.0.


On 11/24/2015 10:21 AM, Jean-Baptiste Onofré wrote:

Sorry, I meant transaction-api feature.

Whick one do you have installed ? 1.1.0 or 1.2.0 ?

Regards
JB


On 11/24/2015 04:13 PM, Jason Reilly wrote:

Hi JB,

I was using what I could find out-of-the-boxwhich I think is
transaction/1.3.0.  I didn't know of a transaction 2.x feature. What is
the repo for that?

Regards,
Jason

On 11/24/2015 10:05 AM, Jean-Baptiste Onofré wrote:

Hi Jason,

did you install transaction 2.x feature ?

Regards
JB

On 11/24/2015 03:41 PM, Jason Reilly wrote:

Hi all,

I am trying to migrate an application to Karaf 4.0.3 & am using 
Java8. I

have tried a few permutations of persistence providers (hibernate,
openjpa, & eclipselink).  I got Hibernate to work, but ran into a 
number
of problems (like not having all the collections in a 
@NamedEntityGraph

loaded & this bug: https://hibernate.atlassian.net/browse/HHH-9270).
Wanting to continue with JPA 2.1, I tried out eclipselink. One of the
problems I had with eclipselink was the following:

2015-11-23 16:28:10,754 | INFO  | rint Extender: 3 |
BlueprintContainerImpl   | 31 - 
org.apache.aries.blueprint.core

- 1.4.5 | Bundle hearsay-dao-jpa/0.0.46.SNAPSHOT is waiting for
namespace handlers [http://aries.apache.org/xmlns/transactions/v2.0.0]


I have transaction & jpa features installed, but the hearsay-dao-jpa
bundle is never activated when I use a blueprint xml file to register
the services.  When I use the pax-cdi annotations (as in Christian's
KarafTutorial example), the hearsay-dao-jpa bundle is activated, but
throws an NPE on getEntityManager() despite using the 
PersistentContext

annotation.  I think this might be related to the Aries JPA 2.2.0
problem mentioned in another thread (Problem with JPA 2.2.0 in Karaf
4.0.2).

When I try openjpa/2.4.0 & JPA 2.0, the openjpa bundle is in a 
resolved

state.  When I try to start that bundle the following is thrown:

ERROR: Bundle org.apache.aries.jpa.container [55] EventDispatcher: 
Error

during dispatch. (java.lang.NoClassDefFoundError:
javax/transaction/Synchronization)

java.lang.NoClassDefFoundError: javax/transaction/Synchronization


However, the packages are available:

karaf@root()> exports | grep javax.transaction

javax.transaction.xa
| 0.0.0| 0   | org.apache.felix.framework

javax.transaction.xa
| 1.1.0| 122 |
org.apache.geronimo.specs.geronimo-jta_1.1_spec

javax.transaction.xa
| 1.2.0| 256 | javax.transaction-api

javax.transaction
| 0.0.0| 0   | org.apache.felix.framework

javax.transaction
| 1.1.0| 122 |
org.apache.geronimo.specs.geronimo-jta_1.1_spec

javax.transaction
| 1.2.0| 256 | javax.transaction-api


I also see the following in the log after messing with which
transaction-api/persistence-api features I have installed:

Caused by: java.lang.NoClassDefFoundError:
javax/transaction/SystemException

 at
org.apache.openjpa.persistence.osgi.PersistenceActivator.start(PersistenceActivator.java:61) 






Before reverting back to Karaf 3.0.5...is there anything else I can
try?  Suggestions?

Thanks,
Jason

Re: Karaf 4.0.3 & JPA

[Jason Reilly]

Hi JB,

I was using what I could find out-of-the-boxwhich I think is 
transaction/1.3.0.  I didn't know of a transaction 2.x feature. What is 
the repo for that?


Regards,
Jason

On 11/24/2015 10:05 AM, Jean-Baptiste Onofré wrote:

Hi Jason,

did you install transaction 2.x feature ?

Regards
JB

On 11/24/2015 03:41 PM, Jason Reilly wrote:

Hi all,

I am trying to migrate an application to Karaf 4.0.3 & am using Java8. I
have tried a few permutations of persistence providers (hibernate,
openjpa, & eclipselink).  I got Hibernate to work, but ran into a number
of problems (like not having all the collections in a @NamedEntityGraph
loaded & this bug: https://hibernate.atlassian.net/browse/HHH-9270).
Wanting to continue with JPA 2.1, I tried out eclipselink.  One of the
problems I had with eclipselink was the following:

2015-11-23 16:28:10,754 | INFO  | rint Extender: 3 |
BlueprintContainerImpl   | 31 - org.apache.aries.blueprint.core
- 1.4.5 | Bundle hearsay-dao-jpa/0.0.46.SNAPSHOT is waiting for
namespace handlers [http://aries.apache.org/xmlns/transactions/v2.0.0]


I have transaction & jpa features installed, but the hearsay-dao-jpa
bundle is never activated when I use a blueprint xml file to register
the services.  When I use the pax-cdi annotations (as in Christian's
KarafTutorial example), the hearsay-dao-jpa bundle is activated, but
throws an NPE on getEntityManager() despite using the PersistentContext
annotation.  I think this might be related to the Aries JPA 2.2.0
problem mentioned in another thread (Problem with JPA 2.2.0 in Karaf
4.0.2).

When I try openjpa/2.4.0 & JPA 2.0, the openjpa bundle is in a resolved
state.  When I try to start that bundle the following is thrown:

ERROR: Bundle org.apache.aries.jpa.container [55] EventDispatcher: Error
during dispatch. (java.lang.NoClassDefFoundError:
javax/transaction/Synchronization)

java.lang.NoClassDefFoundError: javax/transaction/Synchronization


However, the packages are available:

karaf@root()> exports | grep javax.transaction

javax.transaction.xa
| 0.0.0| 0   | org.apache.felix.framework

javax.transaction.xa
| 1.1.0| 122 | 
org.apache.geronimo.specs.geronimo-jta_1.1_spec


javax.transaction.xa
| 1.2.0| 256 | javax.transaction-api

javax.transaction
| 0.0.0| 0   | org.apache.felix.framework

javax.transaction
| 1.1.0| 122 | 
org.apache.geronimo.specs.geronimo-jta_1.1_spec


javax.transaction
| 1.2.0| 256 | javax.transaction-api


I also see the following in the log after messing with which
transaction-api/persistence-api features I have installed:

Caused by: java.lang.NoClassDefFoundError:
javax/transaction/SystemException

 at
org.apache.openjpa.persistence.osgi.PersistenceActivator.start(PersistenceActivator.java:61) 





Before reverting back to Karaf 3.0.5...is there anything else I can
try?  Suggestions?

Thanks,
Jason

Karaf 4.0.3 & JPA

[Jason Reilly]

Hi all,

I am trying to migrate an application to Karaf 4.0.3 & am using Java8.  
I have tried a few permutations of persistence providers (hibernate, 
openjpa, & eclipselink).  I got Hibernate to work, but ran into a number 
of problems (like not having all the collections in a @NamedEntityGraph 
loaded & this bug: https://hibernate.atlassian.net/browse/HHH-9270). 
Wanting to continue with JPA 2.1, I tried out eclipselink.  One of the 
problems I had with eclipselink was the following:


2015-11-23 16:28:10,754 | INFO  | rint Extender: 3 | BlueprintContainerImpl 
  | 31 - org.apache.aries.blueprint.core - 1.4.5 | Bundle 
hearsay-dao-jpa/0.0.46.SNAPSHOT is waiting for namespace handlers 
[http://aries.apache.org/xmlns/transactions/v2.0.0]


I have transaction & jpa features installed, but the hearsay-dao-jpa 
bundle is never activated when I use a blueprint xml file to register 
the services.  When I use the pax-cdi annotations (as in Christian's 
KarafTutorial example), the hearsay-dao-jpa bundle is activated, but 
throws an NPE on getEntityManager() despite using the PersistentContext 
annotation.  I think this might be related to the Aries JPA 2.2.0 
problem mentioned in another thread (Problem with JPA 2.2.0 in Karaf 
4.0.2).


When I try openjpa/2.4.0 & JPA 2.0, the openjpa bundle is in a resolved 
state.  When I try to start that bundle the following is thrown:


ERROR: Bundle org.apache.aries.jpa.container [55] EventDispatcher: Error during 
dispatch. (java.lang.NoClassDefFoundError: javax/transaction/Synchronization)

java.lang.NoClassDefFoundError: javax/transaction/Synchronization


However, the packages are available:

karaf@root()> exports | grep javax.transaction

javax.transaction.xa
   | 0.0.0| 0   | org.apache.felix.framework

javax.transaction.xa
   | 1.1.0| 122 | 
org.apache.geronimo.specs.geronimo-jta_1.1_spec

javax.transaction.xa
   | 1.2.0| 256 | javax.transaction-api

javax.transaction   
   | 0.0.0| 0   | org.apache.felix.framework

javax.transaction   
   | 1.1.0| 122 | 
org.apache.geronimo.specs.geronimo-jta_1.1_spec

javax.transaction   
   | 1.2.0| 256 | javax.transaction-api


I also see the following in the log after messing with which 
transaction-api/persistence-api features I have installed:


Caused by: java.lang.NoClassDefFoundError: javax/transaction/SystemException

at 
org.apache.openjpa.persistence.osgi.PersistenceActivator.start(PersistenceActivator.java:61)


Before reverting back to Karaf 3.0.5...is there anything else I can 
try?  Suggestions?


Thanks,
Jason

RE: scheduling service in karaf 3.0.4

[Pratt, Jason]

Awesome, thanks JB

-Original Message-
From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] 
Sent: Friday, November 06, 2015 9:55 PM
To: user@karaf.apache.org
Subject: Re: scheduling service in karaf 3.0.4

Hi,

I will update the schedule (I'm released 4.0.3 now).

Basically, I plan next 3.0.6 end of next week.

Sorry about that.

Regards
JB

On 11/06/2015 08:15 PM, Pratt, Jason wrote:
> I've seen there is a scheduler in 4.0.x of karaf, is there a reason 
> it's not available in 3.0.x?
>

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

scheduling service in karaf 3.0.4

[Pratt, Jason]

I've seen there is a scheduler in 4.0.x of karaf, is there a reason it's not 
available in 3.0.x?

RE: exploded war file karaf-3.0.4

[Pratt, Jason]

I’ve follow the user guide for using a war file and have setup my pom 
accordingly. I’ve tried as an exploded war (rnt) and with a .war suffix 
(rnt.war), both throw an error and won’t deploy. However, a standard war file 
works as expected. Is there something I am missing like an obscure war command?

I am getting the following error for just a directory added:
2015-10-28 10:05:27,950 | ERROR | raf-3.0.4/deploy | fileinstall
  | 7 - org.apache.felix.fileinstall - 3.5.0 | Failed to install artifact: 
C:\tools\apache-karaf-3.0.4\deploy\rnt
java.net.MalformedURLException: Invalid syntax for instruction 
[Bundle-SymbolicName=C:\tools\apache-karaf]. Take a look at 
http://www.aqute.biz/Code/Bnd.
at 
org.ops4j.pax.swissbox.bnd.BndUtils.parseInstructions(BndUtils.java:302)[2:org.ops4j.pax.url.wrap:2.4.1]
at 
org.ops4j.pax.url.wrap.internal.Parser.(Parser.java:116)[2:org.ops4j.pax.url.wrap:2.4.1]
at 
org.ops4j.pax.url.wrap.internal.Connection.(Connection.java:67)[2:org.ops4j.pax.url.wrap:2.4.1]
at 
org.ops4j.pax.url.wrap.internal.Activator$1.createConnection(Activator.java:59)[2:org.ops4j.pax.url.wrap:2.4.1]
at 
org.ops4j.pax.url.wrap.internal.Activator$1.createConnection(Activator.java:49)[2:org.ops4j.pax.url.wrap:2.4.1]
at 
org.ops4j.pax.url.commons.handler.HandlerActivator$Handler.openConnection(HandlerActivator.java:222)[2:org.ops4j.pax.url.wrap:2.4.1]
at 
org.apache.felix.framework.URLHandlersStreamHandlerProxy.openConnection(URLHandlersStreamHandlerProxy.java:271)[org.apache.felix.framework-4.2.1.jar:]
at java.net.URL.openConnection(URL.java:971)[:1.7.0_79]
at java.net.URL.openStream(URL.java:1037)[:1.7.0_79]
at 
org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:943)[7:org.apache.felix.fileinstall:3.5.0]
at 
org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:865)[7:org.apache.felix.fileinstall:3.5.0]
at 
org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:482)[7:org.apache.felix.fileinstall:3.5.0]
at 
org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:358)[7:org.apache.felix.fileinstall:3.5.0]
at 
org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:310)[7:org.apache.felix.fileinstall:3.5.0]

I get this error for a exploded war with a .war suffix:
2015-10-28 10:09:45,272 | ERROR | raf-3.0.4/deploy | fileinstall
  | 7 - org.apache.felix.fileinstall - 3.5.0 | Failed to install artifact: 
C:\tools\apache-karaf-3.0.4\deploy\rnt.war
java.net.MalformedURLException: Invalid syntax for instruction 
[Bundle-SymbolicName=C:\tools\apache-karaf]. Take a look at 
http://www.aqute.biz/Code/Bnd.
at 
org.ops4j.pax.swissbox.bnd.BndUtils.parseInstructions(BndUtils.java:302)[2:org.ops4j.pax.url.wrap:2.4.1]
at 
org.ops4j.pax.url.wrap.internal.Parser.(Parser.java:116)[2:org.ops4j.pax.url.wrap:2.4.1]
at 
org.ops4j.pax.url.wrap.internal.Connection.(Connection.java:67)[2:org.ops4j.pax.url.wrap:2.4.1]
at 
org.ops4j.pax.url.wrap.internal.Activator$1.createConnection(Activator.java:59)[2:org.ops4j.pax.url.wrap:2.4.1]
at 
org.ops4j.pax.url.wrap.internal.Activator$1.createConnection(Activator.java:49)[2:org.ops4j.pax.url.wrap:2.4.1]
at 
org.ops4j.pax.url.commons.handler.HandlerActivator$Handler.openConnection(HandlerActivator.java:222)[2:org.ops4j.pax.url.wrap:2.4.1]
at 
org.apache.felix.framework.URLHandlersStreamHandlerProxy.openConnection(URLHandlersStreamHandlerProxy.java:271)[org.apache.felix.framework-4.2.1.jar:]
at java.net.URL.openConnection(URL.java:971)[:1.7.0_79]
at java.net.URL.openStream(URL.java:1037)[:1.7.0_79]
at 
org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:943)[7:org.apache.felix.fileinstall:3.5.0]
at 
org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:865)[7:org.apache.felix.fileinstall:3.5.0]
at 
org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:482)[7:org.apache.felix.fileinstall:3.5.0]
at 
org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:358)[7:org.apache.felix.fileinstall:3.5.0]
at 
org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:310)[7:org.apache.felix.fileinstall:3.5.0]




From: Achim Nierbeck [mailto:bcanh...@googlemail.com]
Sent: Wednesday, October 28, 2015 1:02 AM
To: user@karaf.apache.org
Subject: Re: exploded war file karaf-3.0.4

Hi,

an exploded war only works if you put that exploded war directory into the 
deploy folder.

regards, Achim


2015-10-28 1:12 GMT+01:00 Pratt, Jason 
mailto:jason.pr...@windriver.com>>:
Yes, I can deploy a standard war file with no issues.

I need to deploy an ex

RE: exploded war file karaf-3.0.4

[Pratt, Jason]

Yes, I can deploy a standard war file with no issues.

I need to deploy an exploded version of this war file, what I've read is that 
it can hand a directory/folder with a .war suffix
But this is not working for me.

I have a SPA app that needs some json files updated in the war by a camel route

-Original Message-
From: Jamie G. [mailto:jamie.goody...@gmail.com] 
Sent: Tuesday, October 27, 2015 5:09 PM
To: user@karaf.apache.org
Subject: Re: exploded war file karaf-3.0.4

Have you followed the instructions on
http://karaf.apache.org/manual/latest-3.0.x/users-guide/webcontainer.html
?

On Tue, Oct 27, 2015 at 9:06 PM, Pratt, Jason  wrote:
> is there a trick to getting exploded war files to work?
>
>
>
> Using the mvn war:exploded doesn’t seem to make karaf happy and load it
>
>

exploded war file karaf-3.0.4

[Pratt, Jason]

is there a trick to getting exploded war files to work?

Using the mvn war:exploded doesn't seem to make karaf happy and load it

Karaf 4, PAX Web JSF samples

[Jason Reilly]

Hi all,

I am trying to get a JSF based application to deploy on Karaf 4 via a 
custom distribution.  I keep running into the following exception:


2015-10-27 12:48:53,146 | ERROR | ool-167-thread-1 | WebAppPublisher
  | 262 - org.ops4j.pax.web.pax-web-extender-war - 4.2.2 | Error deploying 
web application

java.lang.RuntimeException: javax.xml.parsers.FactoryConfigurationError: 
Provider for class javax.xml.parsers.DocumentBuilderFactory cannot be created

at 
com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:280)[275:org.glassfish.javax.faces:2.2.8]

at 
org.ops4j.pax.web.service.jetty.internal.HttpServiceContext$3.call(HttpServiceContext.java:338)[264:org.ops4j.pax.web.pax-web-jetty:4.2.2]

Caused by: javax.xml.parsers.FactoryConfigurationError: Provider for class 
javax.xml.parsers.DocumentBuilderFactory cannot be created

at 
javax.xml.parsers.FactoryFinder.findServiceProvider(FactoryFinder.java:311)[:1.8.0_45]

at javax.xml.parsers.FactoryFinder.find(FactoryFinder.java:267)[:1.8.0_45]

Caused by: java.lang.RuntimeException: Provider for class 
javax.xml.parsers.DocumentBuilderFactory cannot be created

at 
javax.xml.parsers.FactoryFinder.findServiceProvider(FactoryFinder.java:308)[:1.8.0_45]

Caused by: java.util.ServiceConfigurationError: 
javax.xml.parsers.DocumentBuilderFactory: Provider 
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found

at java.util.ServiceLoader.fail(ServiceLoader.java:239)[:1.8.0_45]

at java.util.ServiceLoader.access$300(ServiceLoader.java:185)[:1.8.0_45]


I have tried adding "javax.xml.parsers" as an import.  Doing so produces 
another exceptionsomething to the effect of NoClassDefFoundException 
for org.w3c.dom.ElementTraversal.


I have tried using pax-jsf-support (MyFaces) which produced a similar 
exception.


Thanks for the help,
Jason

RE: OpenJPA 2.4.0

[Pratt, Jason]

I suppose not, I'll look at moving to 4.x this week.
What are the major benefits to 4.x vs 3.x?

-Original Message-
From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] 
Sent: Monday, October 05, 2015 11:20 AM
To: user@karaf.apache.org
Subject: Re: OpenJPA 2.4.0

You are right: I added OpenJPA 2.4.0 only on Karaf 4.x.

Do you need it on Karaf 3.x ?

Regards
JB

On 10/05/2015 08:12 PM, Pratt, Jason wrote:
> Sorry everyone, it was near end of day Friday when I sent it.
>
> I am using karaf-3.0.4 and migrating from Hibernate to OpenJPA, we've started 
> encountering a lot of entitymanager errors and wanted to switch to openjpa.
> For 3.0.4 I see
> karaf@root()> feature:list | grep -i openjpa
> openjpa | 2.2.2|   | 
> enterprise-3.0.4 | Apache OpenJPA 2.2.x persistence engine support
> openjpa | 2.3.0| x | 
> enterprise-3.0.4 | Apache OpenJPA 2.3.x persistence engine support
>
> -Original Message-
> From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net]
> Sent: Sunday, October 04, 2015 7:11 AM
> To: user@karaf.apache.org
> Subject: Re: OpenJPA 2.4.0
>
> Hi Jason,
>
> with Karaf 4.0.1:
>
> karaf@root()> feature:list |grep -i openjpa
> openjpa   | 2.2.2|  |
> Uninstalled | enterprise-4.0.1 | Apache OpenJPA 2.2.x
> persistence engine support
> openjpa   | 2.3.0|  |
> Uninstalled | enterprise-4.0.1 | Apache OpenJPA 2.3.x
> persistence engine support
> openjpa   | 2.4.0|  |
> Uninstalled | enterprise-4.0.1 | Apache OpenJPA 2.4.x
> persistence engine support
>
>
> So, we can see OpenJPA 2.4.0 feature available.
>
> Which Karaf version do you use ?
>
> Regards
> JB
>
> On 10/03/2015 01:22 AM, Pratt, Jason wrote:
>> I can't seem to add this feature, is it not available?
>>
>

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

RE: OpenJPA 2.4.0

[Pratt, Jason]

Sorry everyone, it was near end of day Friday when I sent it.

I am using karaf-3.0.4 and migrating from Hibernate to OpenJPA, we've started 
encountering a lot of entitymanager errors and wanted to switch to openjpa.
For 3.0.4 I see
karaf@root()> feature:list | grep -i openjpa
openjpa | 2.2.2|   | 
enterprise-3.0.4 | Apache OpenJPA 2.2.x persistence engine support
openjpa | 2.3.0| x | 
enterprise-3.0.4 | Apache OpenJPA 2.3.x persistence engine support

-Original Message-
From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] 
Sent: Sunday, October 04, 2015 7:11 AM
To: user@karaf.apache.org
Subject: Re: OpenJPA 2.4.0

Hi Jason,

with Karaf 4.0.1:

karaf@root()> feature:list |grep -i openjpa
openjpa   | 2.2.2|  | 
Uninstalled | enterprise-4.0.1 | Apache OpenJPA 2.2.x 
persistence engine support
openjpa   | 2.3.0|  | 
Uninstalled | enterprise-4.0.1 | Apache OpenJPA 2.3.x 
persistence engine support
openjpa   | 2.4.0|  | 
Uninstalled | enterprise-4.0.1 | Apache OpenJPA 2.4.x 
persistence engine support


So, we can see OpenJPA 2.4.0 feature available.

Which Karaf version do you use ?

Regards
JB

On 10/03/2015 01:22 AM, Pratt, Jason wrote:
> I can't seem to add this feature, is it not available?
>

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

OpenJPA 2.4.0

[Pratt, Jason]

I can't seem to add this feature, is it not available?

RE: karaf-3.0.4 download link for linux broken

[Pratt, Jason]

Interesting, they all failed expect for the waterloo one

-Original Message-
From: Jamie G. [mailto:jamie.goody...@gmail.com] 
Sent: Monday, August 17, 2015 10:35 AM
To: user@karaf.apache.org
Subject: Re: karaf-3.0.4 download link for linux broken

Is that happen for all the mirror links ?

http://www.apache.org/dyn/closer.cgi/karaf/3.0.4/apache-karaf-3.0.4.tar.gz

http://mirror.its.dal.ca/apache/karaf/3.0.4/apache-karaf-3.0.4.tar.gz
http://apache.parentingamerica.com/karaf/3.0.4/apache-karaf-3.0.4.tar.gz
http://mirror.csclub.uwaterloo.ca/apache/karaf/3.0.4/apache-karaf-3.0.4.tar.gz

I'm getting 15.7 MB for the ones above.

On Mon, Aug 17, 2015 at 2:55 PM, Pratt, Jason  wrote:
> The link is always 4.7kb no matter browser is used and I can’t find an 
> FTP server or other mirror to download from

karaf-3.0.4 download link for linux broken

[Pratt, Jason]

The link is always 4.7kb no matter browser is used and I can't find an FTP 
server or other mirror to download from

RE: How to avoid getting two servicemix-specs versions when installing camel or cxf 's feature

[Pratt, Jason]

#2 sounds like it'd give the developer/admin more control

-Original Message-
From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] 
Sent: Wednesday, August 05, 2015 12:17 PM
To: user@karaf.apache.org
Subject: Re: How to avoid getting two servicemix-specs versions when installing 
camel or cxf 's feature

Hi Aki,

let's see what the others think: if all agree, I will go for approach 2.

Regards
JB

On 08/05/2015 07:12 PM, Aki Yoshida wrote:
> Hi JB,
>
> Thanks for the explanation.
>
> For the current snapshot version of camel (2.16-SNAPSHOT and 
> 2.15.3-SNAPSHOT), we used approach 1 to solve this problem for now.
> If the spec features are made available in one of the Karaf's repos as 
> in approach 2, that will be great. This can avoid this problem for 
> other combination in the future or with a combination with other 
> components that also can use this shared features to avoid getting 
> into this problem.
> Will you be providing the spec features as in approach 2?
>
> Regards, aki
>
>
>
> 2015-08-05 17:28 GMT+02:00 Jean-Baptiste Onofré :
>> Hi Aki,
>>
>> We have different ways:
>> 1/ we "align" CXF and Camel to the same spec bundle version. As spec 
>> bundles are pretty stable in term of release, I think it's probably 
>> the easiest move, but we don't actually fix the problem if we use old 
>> version of one of the two.
>> 2/ remove spec from CXF and Camel and put a spec feature directly in 
>> Karaf, as we do for jetty, etc.
>> 3/ provision spec bundle in the lib folder as we do for activator 
>> spec bundle
>>
>> Probably 2 would make sense. Anyway, we will have to update CXF and 
>> Camel to refer to provided spec feature. With Karaf 4 and the new 
>> feature resolver, it would be better to use feature requirements and 
>> let the resolver deals with spec bundle.
>>
>> Regards
>> JB
>>
>>
>> On 08/05/2015 11:38 AM, Aki Yoshida wrote:
>>>
>>> Originally, I posted the following mail to dev@camel regarding this issue.
>>>
>>> http://camel.465427.n5.nabble.com/Installing-camel-cxf-2-15-2-featur
>>> e-leads-to-two-versions-of-ServiceMix-Stax-API-bundles-installed-td5
>>> 769830.html
>>>
>>> Currently, both camel and cxf have their features that directly 
>>> installing some servicemix-specs bundles. This leads to the problem 
>>> mentioned in the above mail thread that installing camel-cxf leads 
>>> to installing two versions of servicemix-spec because camel-2.15.2 
>>> is using smx-specs 2.2.0 while cxf-3.0.4 referred in camel-2.15.2 is 
>>> using smx-specs 2.4.0.
>>>
>>> I am wondering if we need to define this feature (e.g., feature
>>> stax-api-1.0) outside of camel and cxf and both refer to this 
>>> external feature using the appropriate version range e.g. [2.2,3) or 
>>> we can locally solve this problem within camel and cxf's feature 
>>> definitions?
>>>
>>> I would appreciate for your comments.
>>>
>>> regards, aki
>>>
>>
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com

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

RE: Understanding dependency in features.xml...

[Pratt, Jason]

Hi Ed,
They should show up like:

344 | Active |  50 | 1.3.5  | jettison
345 | Active |  50 | 2.4.1  | Jackson-core
346 | Active |  50 | 2.4.1  | jackson-databind
347 | Active |  50 | 2.4.1  | Jackson-annotations

I’ve found the “dependency” is sometimes flaky and use the install=auto flag 
when I want something to be installed

Here is my feature for Jackson:

mvn:com.fasterxml.jackson.core/jackson-core/2.5.4

mvn:com.fasterxml.jackson.core/jackson-annotations/2.5.4
mvn:com.fasterxml.jackson.core/jackson-databind/2.5.4

mvn:com.fasterxml.jackson.jaxrs/jackson-jaxrs-json-provider/2.5.4
 
mvn:com.fasterxml.jackson.jaxrs/jackson-jaxrs-base/2.5.4
 mvn:org.codehaus.jackson/jackson-jaxrs/1.9.13
 mvn:org.codehaus.jackson/jackson-core-asl/1.9.13
 mvn:org.codehaus.jackson/jackson-mapper-asl/1.9.13


I had to include the old codehaus jars for some CXF issues, hope this helps

Kind regards,
Jason

From: Ed Hillmann [mailto:ed.hillm...@gmail.com]
Sent: Thursday, July 23, 2015 7:07 PM
To: user@karaf.apache.org
Subject: Understanding dependency in features.xml...

Hi.  I am attempting to define bundles as dependencies, but am getting some 
unexpected behaviour.  My presumption is I don't understand how it's meant to 
be used.  The doco around this is short and sweet: "A bundle can be flagged as 
being a dependency, using the dependency attribute set to true on the  
element."

My interpretation is this means "If the bundle is not there already, install 
it, I depend on it.  If not, just use it".  Perhaps I have interpreted it wrong.

I have a feature xml file that contains these definitions:


mvn:com.fasterxml.jackson.core/jackson-core/2.5.4
mvn:com.fasterxml.jackson.core/jackson-annotations/2.5.4
mvn:com.fasterxml.jackson.core/jackson-databind/2.5.4
mvn:com.fasterxml.jackson.module/jackson-module-jaxb-annotations/2.5.4


mvn:com.fasterxml.jackson.jaxrs/jackson-jaxrs-base/2.5.4
mvn:com.fasterxml.jackson.jaxrs/jackson-jaxrs-json-provider/2.5.4



In the same file, I have a third feature that references these jackson features:


Features or bundles needed to support my code
gemini-blueprint
war
hibernate
jackson
jackson-jaxrs
cxf
spring
spring-jdbc
spring-orm
spring-tx
spring-data-cassandra
mvn:org.apache.commons/commons-math3/3.5
mvn:com.hazelcast/hazelcast/3.5
mvn:io.reactivex/rxjava/1.0.12


I can add my feature repository, and I can install my feature.  And it works, 
apparently without an error.  If I list my installed features, it says the 
Jackson features are started...

minestar-core-bundles| 1.0.4.SNAPSHOT   | x| Started | 
my-core-features-1.0.4-SNAPSHOT | myCore Bundles
jackson  | 2.5.4|  | Started | 
minestar-core-features-1.0.4-SNAPSHOT | Jackson libraries
jackson-jaxrs| 2.5.4|  | Started | 
minestar-core-features-1.0.4-SNAPSHOT | Jackson JAX-RS libraries

However, the jackson bundles are not visible when I list the bundles.  They're 
not even installed.  Anything I use which depends on Jackson won't resolve 
because it can't find anything.

If I define my Jackson feature without the "dependency" attribute, it works 
more like I expected.

Is my understanding of what the dependency attribute for a bundle in the 
features.xml incorrect?  If not, am I doing something else incorrectly?

Thanks for any help,
Ed

RE: installing activemq and seeing very strange behavior

[Pratt, Jason]

Upon further investigation, this still happens on installation via KAR or from 
the CLI command. My team can reproduce it consistently.
However, it doesn’t happen after a restart of the karaf container.

Should I log this as a bug, since James has seen the same behavior?

Regards,
Jason

From: Jason Pratt [mailto:jpratt3...@gmail.com]
Sent: Saturday, July 18, 2015 7:38 AM
To: user@karaf.apache.org
Subject: Re: installing activemq and seeing very strange behavior


It happens on 5.9.1 to 5.11.1
On Jul 17, 2015 9:04 PM, "Jean-Baptiste Onofré" 
mailto:j...@nanthrax.net>> wrote:
What's the ActiveMQ version ?

On 07/17/2015 10:17 PM, Pratt, Jason wrote:
Hello – While installing ActiveMQ via a KAR I am seeing strange
behavior. Tailing the log to watch the install, I experience:

1.Log entry saying the Blueprint container is being destroyed

2.Exiting the log to the main Karaf shell

3.Then seeing the initial banner loading anywhere from 2 – 5 times

4.Final error is a PermGen, but I have that set to 1024M and 2G
respectively

What would be causing this?

2015-07-17 13:10:43,537 | INFO  | xFrameworkWiring |
BlueprintExtender| 15 - org.apache.aries.blueprint.core
- 1.4.3 | Destroying BlueprintContainer for bundle
org.apache.karaf.system.command

2015-07-17 13:10:43,577 | INFO  | xFrameworkWiring |
BlueprintExtender| 15 - org.apache.aries.blueprint.core
- 1.4.3 | Destroying BlueprintContainer for bundle
org.apache.karaf.bundle.core

2015-07-17 13:10:43,647 | INFO  | xFrameworkWiring |
Activator| 122 -
org.ops4j.pax.web.pax-web-extender-war - 3.2.3 | Destroying extension
for bundle org.apache.activemq.activemq-web-console

2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring |
activemq-web-console - 204}  | 108 -
org.eclipse.jetty.aggregate.jetty-all-server - 8.1.17.v20150415 |
Destroying Spring FrameworkServlet 'dispatcher'

2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring |
XmlWebApplicationContext | 204 -
org.apache.activemq.activemq-web-console - 5.11.1 | Closing
WebApplicationContext for namespace 'dispatcher-servlet': startup date
[Fri Jul 17 13:10:41 PDT 2015]; parent: Root WebApplicationContext

2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring |
DefaultListableBeanFactory   | 204 -
org.apache.activemq.activemq-web-console - 5.11.1 | Destroying
singletons in
org.springframework.beans.factory.support.DefaultListableBeanFactory@5f8bdda8<mailto:org.springframework.beans.factory.support.DefaultListableBeanFactory@5f8bdda8>:
defining beans
[handlerMapping,/createDestination.action,/deleteDestination.action,/createSubscriber.action,/deleteSubscriber.action,/sendMessage.action,/purgeDestination.action,/deleteMessage.action,/copyMessage.action,/moveMessage.action,/deleteJob

.action,exceptionResolver]; parent:
org.springframework.beans.factory.support.DefaultListableBeanFactory@63eb624a<mailto:org.springframework.beans.factory.support.DefaultListableBeanFactory@63eb624a>

2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring |
XmlWebApplicationContext | 204 -
org.apache.activemq.activemq-web-console - 5.11.1 | Closing Root
WebApplicationContext: startup date [Fri Jul 17 13:10:41 PDT 2015]; root
of context hierarchy

2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring |
DefaultListableBeanFactory   | 204 -
org.apache.activemq.activemq-web-console - 5.11.1 | Destroying
singletons in
org.springframework.beans.factory.support.DefaultListableBeanFactory@63eb624a<mailto:org.springframework.beans.factory.support.DefaultListableBeanFactory@63eb624a>:
defining beans
[queueBrowser,messageQuery,queueConsumerQuery,queueProducerQuery,topicProducerQuery,topicSubscriberQuery,connectionQuery,placeholderConfig,sessionPool,configuration,brokerQuery,connectionFactory];
root of factory hierarchy

2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring |
ContextHandler   | 108 -
org.eclipse.jetty.aggregate.jetty-all-server - 8.1.17.v20150415 |
stopped
HttpServiceContext{httpContext=WebAppHttpContext{org.apache.activemq.activemq-web-console
- 204}}

2015-07-17 13:10:43,667 | INFO  | xFrameworkWiring |
HttpServiceFactoryImpl   | 116 -
org.ops4j.pax.web.pax-web-runtime - 3.2.3 | Unbinding bundle:
[org.apache.activemq.activemq-web-console [204]]

2015-07-17 13:10:43,687 | INFO  | xFrameworkWiring |
BlueprintExtender| 15 - org.apache.aries.blueprint.core
- 1.4.3 | Destroying BlueprintContainer for bundle
org.apache.karaf.kar.command

2015-07-17 13:10:43,707 | INFO  | xFrameworkWiring |
BlueprintExtender| 15 - org.apache.aries.blueprint.core
- 1.4.3 | Destroying BlueprintContainer for bundle
org.apache.camel.karaf.camel-karaf-commands

2015-07-17 13:10:43,767 | INFO  | xFrameworkWiring |
BlueprintExtender| 15 - org.apache.aries.blueprint.core
- 1.4.3 | Destroying BlueprintContainer for bundle
org.apache.karaf.webconsole.http

2015

Re: installing activemq and seeing very strange behavior

[Jason Pratt]

It happens on 5.9.1 to 5.11.1
On Jul 17, 2015 9:04 PM, "Jean-Baptiste Onofré"  wrote:

> What's the ActiveMQ version ?
>
> On 07/17/2015 10:17 PM, Pratt, Jason wrote:
>
>> Hello – While installing ActiveMQ via a KAR I am seeing strange
>> behavior. Tailing the log to watch the install, I experience:
>>
>> 1.Log entry saying the Blueprint container is being destroyed
>>
>> 2.Exiting the log to the main Karaf shell
>>
>> 3.Then seeing the initial banner loading anywhere from 2 – 5 times
>>
>> 4.Final error is a PermGen, but I have that set to 1024M and 2G
>> respectively
>>
>> What would be causing this?
>>
>> 2015-07-17 13:10:43,537 | INFO  | xFrameworkWiring |
>> BlueprintExtender| 15 - org.apache.aries.blueprint.core
>> - 1.4.3 | Destroying BlueprintContainer for bundle
>> org.apache.karaf.system.command
>>
>> 2015-07-17 13:10:43,577 | INFO  | xFrameworkWiring |
>> BlueprintExtender| 15 - org.apache.aries.blueprint.core
>> - 1.4.3 | Destroying BlueprintContainer for bundle
>> org.apache.karaf.bundle.core
>>
>> 2015-07-17 13:10:43,647 | INFO  | xFrameworkWiring |
>> Activator| 122 -
>> org.ops4j.pax.web.pax-web-extender-war - 3.2.3 | Destroying extension
>> for bundle org.apache.activemq.activemq-web-console
>>
>> 2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring |
>> activemq-web-console - 204}  | 108 -
>> org.eclipse.jetty.aggregate.jetty-all-server - 8.1.17.v20150415 |
>> Destroying Spring FrameworkServlet 'dispatcher'
>>
>> 2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring |
>> XmlWebApplicationContext | 204 -
>> org.apache.activemq.activemq-web-console - 5.11.1 | Closing
>> WebApplicationContext for namespace 'dispatcher-servlet': startup date
>> [Fri Jul 17 13:10:41 PDT 2015]; parent: Root WebApplicationContext
>>
>> 2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring |
>> DefaultListableBeanFactory   | 204 -
>> org.apache.activemq.activemq-web-console - 5.11.1 | Destroying
>> singletons in
>>
>> org.springframework.beans.factory.support.DefaultListableBeanFactory@5f8bdda8
>> :
>> defining beans
>>
>> [handlerMapping,/createDestination.action,/deleteDestination.action,/createSubscriber.action,/deleteSubscriber.action,/sendMessage.action,/purgeDestination.action,/deleteMessage.action,/copyMessage.action,/moveMessage.action,/deleteJob
>>
>> .action,exceptionResolver]; parent:
>>
>> org.springframework.beans.factory.support.DefaultListableBeanFactory@63eb624a
>>
>> 2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring |
>> XmlWebApplicationContext | 204 -
>> org.apache.activemq.activemq-web-console - 5.11.1 | Closing Root
>> WebApplicationContext: startup date [Fri Jul 17 13:10:41 PDT 2015]; root
>> of context hierarchy
>>
>> 2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring |
>> DefaultListableBeanFactory   | 204 -
>> org.apache.activemq.activemq-web-console - 5.11.1 | Destroying
>> singletons in
>>
>> org.springframework.beans.factory.support.DefaultListableBeanFactory@63eb624a
>> :
>> defining beans
>>
>> [queueBrowser,messageQuery,queueConsumerQuery,queueProducerQuery,topicProducerQuery,topicSubscriberQuery,connectionQuery,placeholderConfig,sessionPool,configuration,brokerQuery,connectionFactory];
>> root of factory hierarchy
>>
>> 2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring |
>> ContextHandler   | 108 -
>> org.eclipse.jetty.aggregate.jetty-all-server - 8.1.17.v20150415 |
>> stopped
>>
>> HttpServiceContext{httpContext=WebAppHttpContext{org.apache.activemq.activemq-web-console
>> - 204}}
>>
>> 2015-07-17 13:10:43,667 | INFO  | xFrameworkWiring |
>> HttpServiceFactoryImpl   | 116 -
>> org.ops4j.pax.web.pax-web-runtime - 3.2.3 | Unbinding bundle:
>> [org.apache.activemq.activemq-web-console [204]]
>>
>> 2015-07-17 13:10:43,687 | INFO  | xFrameworkWiring |
>> BlueprintExtender| 15 - org.apache.aries.blueprint.core
>> - 1.4.3 | Destroying BlueprintContainer for bundle
>> org.apache.karaf.kar.command
>>
>> 2015-07-17 13:10:43,707 | INFO  | xFrameworkWiring |
>> BlueprintExtender| 15 - org.apache.aries.blueprint.core
>> - 1.4.3 | Destroying BlueprintContainer for bundle
>> org.apache.camel.karaf.camel-karaf-commands
>>
>> 2015-07-17 13:10:43,767 | INFO  | xFrameworkWiring |
>> BlueprintExtender| 15 - org.apache.aries.b

RE: installing activemq and seeing very strange behavior

[Pratt, Jason]

It appears to be the activemq-blueprint bundle.

After going all the way down to 5.9.1 with the current KAR of

·Activemq

·Activemq-broker-noweb

·Activemq-camel

·Activemq-blueprint

I am letting that sit on the back burner until I can get a basic activemq 
working with out all these errors. I have started to install via the CLI.
For ActiveMQ 5.11.1 from the CLI when I install blueprint it just hangs and I 
have to kill the JVM its in and restart again.

CLI output:

karaf@root(feature)> install activemq-blueprint
Refreshing bundles org.apache.activemq.activemq-osgi (104)

__ __  
   / //_/ __ _/ __/
  / ,<  / __ `/ ___/ __ `/ /_
 / /| |/ /_/ / /  / /_/ / __/
/_/ |_|\__,_/_/   \__,_/_/

  Apache Karaf (3.0.4)

Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.

karaf@root()> Error executing command: Invalid BundleContext.

From: James Carman [mailto:ja...@carmanconsulting.com]
Sent: Friday, July 17, 2015 5:21 PM
To: user@karaf.apache.org
Subject: Re: installing activemq and seeing very strange behavior

Yes, we ran into it too, but noweb did start for us. Let us know if you find 
the version where it goes wonky.
On Fri, Jul 17, 2015 at 7:19 PM Pratt, Jason 
mailto:jason.pr...@windriver.com>> wrote:
I did try that, its still having the same effect. I am going to try version 
5.10.2 next and keep downgrading until I find one that works with 3.0.4
This is very frustrating.

From: James Carman 
[mailto:ja...@carmanconsulting.com<mailto:ja...@carmanconsulting.com>]
Sent: Friday, July 17, 2015 4:53 PM
To: user@karaf.apache.org<mailto:user@karaf.apache.org>
Subject: Re: installing activemq and seeing very strange behavior

Try installing the activemq-broker-noweb feature. Something is wrong with the 
webconsole it seems.
On Fri, Jul 17, 2015 at 6:43 PM Pratt, Jason 
mailto:jason.pr...@windriver.com>> wrote:
I’ve confirmed this happening on other team members pc’s as well. I assume 
there is an undocumented trick to getting activemq to install properly?

From: Pratt, Jason 
[mailto:jason.pr...@windriver.com<mailto:jason.pr...@windriver.com>]
Sent: Friday, July 17, 2015 1:17 PM
To: user@karaf.apache.org<mailto:user@karaf.apache.org>
Subject: installing activemq and seeing very strange behavior

Hello – While installing ActiveMQ via a KAR I am seeing strange behavior. 
Tailing the log to watch the install, I experience:

1.  Log entry saying the Blueprint container is being destroyed

2.  Exiting the log to the main Karaf shell

3.  Then seeing the initial banner loading anywhere from 2 – 5 times

4.  Final error is a PermGen, but I have that set to 1024M and 2G 
respectively

What would be causing this?


2015-07-17 13:10:43,537 | INFO  | xFrameworkWiring | BlueprintExtender  
  | 15 - org.apache.aries.blueprint.core - 1.4.3 | Destroying 
BlueprintContainer for bundle org.apache.karaf.system.command
2015-07-17 13:10:43,577 | INFO  | xFrameworkWiring | BlueprintExtender  
  | 15 - org.apache.aries.blueprint.core - 1.4.3 | Destroying 
BlueprintContainer for bundle org.apache.karaf.bundle.core
2015-07-17 13:10:43,647 | INFO  | xFrameworkWiring | Activator  
  | 122 - org.ops4j.pax.web.pax-web-extender-war - 3.2.3 | Destroying 
extension for bundle org.apache.activemq.activemq-web-console
2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring | activemq-web-console - 
204}  | 108 - org.eclipse.jetty.aggregate.jetty-all-server - 
8.1.17.v20150415 | Destroying Spring FrameworkServlet 'dispatcher'
2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring | XmlWebApplicationContext   
  | 204 - org.apache.activemq.activemq-web-console - 5.11.1 | Closing 
WebApplicationContext for namespace 'dispatcher-servlet': startup date [Fri Jul 
17 13:10:41 PDT 2015]; parent: Root WebApplicationContext
2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring | DefaultListableBeanFactory 
  | 204 - org.apache.activemq.activemq-web-console - 5.11.1 | Destroying 
singletons in 
org.springframework.beans.factory.support.DefaultListableBeanFactory@5f8bdda8<mailto:org.springframework.beans.factory.support.DefaultListableBeanFactory@5f8bdda8>:
 defining beans 
[handlerMapping,/createDestination.action,/deleteDestination.action,/createSubscriber.action,/deleteSubscriber.action,/sendMessage.action,/purgeDestination.action,/deleteMessage.action,/copyMessage.action,/moveMessage.action,/deleteJob
.action,exceptionResolver]; parent: 
org.springframework.beans.factory.support.DefaultListableBeanFactory@63eb624a<mailto:org.springframework.beans.factory.support.DefaultListableBeanFactory@63eb624a>
2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring | XmlWebApplicationContext   
   

RE: installing activemq and seeing very strange behavior

[Pratt, Jason]

I did try that, its still having the same effect. I am going to try version 
5.10.2 next and keep downgrading until I find one that works with 3.0.4
This is very frustrating.

From: James Carman [mailto:ja...@carmanconsulting.com]
Sent: Friday, July 17, 2015 4:53 PM
To: user@karaf.apache.org
Subject: Re: installing activemq and seeing very strange behavior

Try installing the activemq-broker-noweb feature. Something is wrong with the 
webconsole it seems.
On Fri, Jul 17, 2015 at 6:43 PM Pratt, Jason 
mailto:jason.pr...@windriver.com>> wrote:
I’ve confirmed this happening on other team members pc’s as well. I assume 
there is an undocumented trick to getting activemq to install properly?

From: Pratt, Jason 
[mailto:jason.pr...@windriver.com<mailto:jason.pr...@windriver.com>]
Sent: Friday, July 17, 2015 1:17 PM
To: user@karaf.apache.org<mailto:user@karaf.apache.org>
Subject: installing activemq and seeing very strange behavior

Hello – While installing ActiveMQ via a KAR I am seeing strange behavior. 
Tailing the log to watch the install, I experience:

1.  Log entry saying the Blueprint container is being destroyed

2.  Exiting the log to the main Karaf shell

3.  Then seeing the initial banner loading anywhere from 2 – 5 times

4.  Final error is a PermGen, but I have that set to 1024M and 2G 
respectively

What would be causing this?


2015-07-17 13:10:43,537 | INFO  | xFrameworkWiring | BlueprintExtender  
  | 15 - org.apache.aries.blueprint.core - 1.4.3 | Destroying 
BlueprintContainer for bundle org.apache.karaf.system.command
2015-07-17 13:10:43,577 | INFO  | xFrameworkWiring | BlueprintExtender  
  | 15 - org.apache.aries.blueprint.core - 1.4.3 | Destroying 
BlueprintContainer for bundle org.apache.karaf.bundle.core
2015-07-17 13:10:43,647 | INFO  | xFrameworkWiring | Activator  
  | 122 - org.ops4j.pax.web.pax-web-extender-war - 3.2.3 | Destroying 
extension for bundle org.apache.activemq.activemq-web-console
2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring | activemq-web-console - 
204}  | 108 - org.eclipse.jetty.aggregate.jetty-all-server - 
8.1.17.v20150415 | Destroying Spring FrameworkServlet 'dispatcher'
2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring | XmlWebApplicationContext   
  | 204 - org.apache.activemq.activemq-web-console - 5.11.1 | Closing 
WebApplicationContext for namespace 'dispatcher-servlet': startup date [Fri Jul 
17 13:10:41 PDT 2015]; parent: Root WebApplicationContext
2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring | DefaultListableBeanFactory 
  | 204 - org.apache.activemq.activemq-web-console - 5.11.1 | Destroying 
singletons in 
org.springframework.beans.factory.support.DefaultListableBeanFactory@5f8bdda8<mailto:org.springframework.beans.factory.support.DefaultListableBeanFactory@5f8bdda8>:
 defining beans 
[handlerMapping,/createDestination.action,/deleteDestination.action,/createSubscriber.action,/deleteSubscriber.action,/sendMessage.action,/purgeDestination.action,/deleteMessage.action,/copyMessage.action,/moveMessage.action,/deleteJob
.action,exceptionResolver]; parent: 
org.springframework.beans.factory.support.DefaultListableBeanFactory@63eb624a<mailto:org.springframework.beans.factory.support.DefaultListableBeanFactory@63eb624a>
2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring | XmlWebApplicationContext   
  | 204 - org.apache.activemq.activemq-web-console - 5.11.1 | Closing Root 
WebApplicationContext: startup date [Fri Jul 17 13:10:41 PDT 2015]; root of 
context hierarchy
2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring | DefaultListableBeanFactory 
  | 204 - org.apache.activemq.activemq-web-console - 5.11.1 | Destroying 
singletons in 
org.springframework.beans.factory.support.DefaultListableBeanFactory@63eb624a<mailto:org.springframework.beans.factory.support.DefaultListableBeanFactory@63eb624a>:
 defining beans 
[queueBrowser,messageQuery,queueConsumerQuery,queueProducerQuery,topicProducerQuery,topicSubscriberQuery,connectionQuery,placeholderConfig,sessionPool,configuration,brokerQuery,connectionFactory];
 root of factory hierarchy
2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring | ContextHandler 
  | 108 - org.eclipse.jetty.aggregate.jetty-all-server - 8.1.17.v20150415 | 
stopped 
HttpServiceContext{httpContext=WebAppHttpContext{org.apache.activemq.activemq-web-console
 - 204}}
2015-07-17 13:10:43,667 | INFO  | xFrameworkWiring | HttpServiceFactoryImpl 
  | 116 - org.ops4j.pax.web.pax-web-runtime - 3.2.3 | Unbinding bundle: 
[org.apache.activemq.activemq-web-console [204]]
2015-07-17 13:10:43,687 | INFO  | xFrameworkWiring | BlueprintExtender  
  | 15 - org.apache.aries.blueprint.core - 1.4.3 | Destroying 
BlueprintContainer for bundle org.apache.karaf.kar.command
2015-07-17 13:10:43,707 | INFO  | xFrameworkWiring | BlueprintExtender  
  | 15 - org.apache.aries

RE: installing activemq and seeing very strange behavior

[Pratt, Jason]

I've confirmed this happening on other team members pc's as well. I assume 
there is an undocumented trick to getting activemq to install properly?

From: Pratt, Jason [mailto:jason.pr...@windriver.com]
Sent: Friday, July 17, 2015 1:17 PM
To: user@karaf.apache.org
Subject: installing activemq and seeing very strange behavior

Hello - While installing ActiveMQ via a KAR I am seeing strange behavior. 
Tailing the log to watch the install, I experience:

1.  Log entry saying the Blueprint container is being destroyed

2.  Exiting the log to the main Karaf shell

3.  Then seeing the initial banner loading anywhere from 2 - 5 times

4.  Final error is a PermGen, but I have that set to 1024M and 2G 
respectively

What would be causing this?


2015-07-17 13:10:43,537 | INFO  | xFrameworkWiring | BlueprintExtender  
  | 15 - org.apache.aries.blueprint.core - 1.4.3 | Destroying 
BlueprintContainer for bundle org.apache.karaf.system.command
2015-07-17 13:10:43,577 | INFO  | xFrameworkWiring | BlueprintExtender  
  | 15 - org.apache.aries.blueprint.core - 1.4.3 | Destroying 
BlueprintContainer for bundle org.apache.karaf.bundle.core
2015-07-17 13:10:43,647 | INFO  | xFrameworkWiring | Activator  
  | 122 - org.ops4j.pax.web.pax-web-extender-war - 3.2.3 | Destroying 
extension for bundle org.apache.activemq.activemq-web-console
2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring | activemq-web-console - 
204}  | 108 - org.eclipse.jetty.aggregate.jetty-all-server - 
8.1.17.v20150415 | Destroying Spring FrameworkServlet 'dispatcher'
2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring | XmlWebApplicationContext   
  | 204 - org.apache.activemq.activemq-web-console - 5.11.1 | Closing 
WebApplicationContext for namespace 'dispatcher-servlet': startup date [Fri Jul 
17 13:10:41 PDT 2015]; parent: Root WebApplicationContext
2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring | DefaultListableBeanFactory 
  | 204 - org.apache.activemq.activemq-web-console - 5.11.1 | Destroying 
singletons in 
org.springframework.beans.factory.support.DefaultListableBeanFactory@5f8bdda8<mailto:org.springframework.beans.factory.support.DefaultListableBeanFactory@5f8bdda8>:
 defining beans 
[handlerMapping,/createDestination.action,/deleteDestination.action,/createSubscriber.action,/deleteSubscriber.action,/sendMessage.action,/purgeDestination.action,/deleteMessage.action,/copyMessage.action,/moveMessage.action,/deleteJob
.action,exceptionResolver]; parent: 
org.springframework.beans.factory.support.DefaultListableBeanFactory@63eb624a<mailto:org.springframework.beans.factory.support.DefaultListableBeanFactory@63eb624a>
2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring | XmlWebApplicationContext   
  | 204 - org.apache.activemq.activemq-web-console - 5.11.1 | Closing Root 
WebApplicationContext: startup date [Fri Jul 17 13:10:41 PDT 2015]; root of 
context hierarchy
2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring | DefaultListableBeanFactory 
  | 204 - org.apache.activemq.activemq-web-console - 5.11.1 | Destroying 
singletons in 
org.springframework.beans.factory.support.DefaultListableBeanFactory@63eb624a<mailto:org.springframework.beans.factory.support.DefaultListableBeanFactory@63eb624a>:
 defining beans 
[queueBrowser,messageQuery,queueConsumerQuery,queueProducerQuery,topicProducerQuery,topicSubscriberQuery,connectionQuery,placeholderConfig,sessionPool,configuration,brokerQuery,connectionFactory];
 root of factory hierarchy
2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring | ContextHandler 
  | 108 - org.eclipse.jetty.aggregate.jetty-all-server - 8.1.17.v20150415 | 
stopped 
HttpServiceContext{httpContext=WebAppHttpContext{org.apache.activemq.activemq-web-console
 - 204}}
2015-07-17 13:10:43,667 | INFO  | xFrameworkWiring | HttpServiceFactoryImpl 
  | 116 - org.ops4j.pax.web.pax-web-runtime - 3.2.3 | Unbinding bundle: 
[org.apache.activemq.activemq-web-console [204]]
2015-07-17 13:10:43,687 | INFO  | xFrameworkWiring | BlueprintExtender  
  | 15 - org.apache.aries.blueprint.core - 1.4.3 | Destroying 
BlueprintContainer for bundle org.apache.karaf.kar.command
2015-07-17 13:10:43,707 | INFO  | xFrameworkWiring | BlueprintExtender  
  | 15 - org.apache.aries.blueprint.core - 1.4.3 | Destroying 
BlueprintContainer for bundle org.apache.camel.karaf.camel-karaf-commands
2015-07-17 13:10:43,767 | INFO  | xFrameworkWiring | BlueprintExtender  
  | 15 - org.apache.aries.blueprint.core - 1.4.3 | Destroying 
BlueprintContainer for bundle org.apache.karaf.webconsole.http
2015-07-17 13:10:43,767 | INFO  | xFrameworkWiring | HttpPlugin 
  | 148 - org.apache.karaf.webconsole.http - 3.0.4 | Http plugin deactivated
2015-07-17 13:10:43,777 | INFO  | xFrameworkWiring | BlueprintExtender  
  | 15 - org.apache.aries.blueprint.core - 1

installing activemq and seeing very strange behavior

[Pratt, Jason]

Hello - While installing ActiveMQ via a KAR I am seeing strange behavior. 
Tailing the log to watch the install, I experience:

1.  Log entry saying the Blueprint container is being destroyed

2.  Exiting the log to the main Karaf shell

3.  Then seeing the initial banner loading anywhere from 2 - 5 times

4.  Final error is a PermGen, but I have that set to 1024M and 2G 
respectively

What would be causing this?


2015-07-17 13:10:43,537 | INFO  | xFrameworkWiring | BlueprintExtender  
  | 15 - org.apache.aries.blueprint.core - 1.4.3 | Destroying 
BlueprintContainer for bundle org.apache.karaf.system.command
2015-07-17 13:10:43,577 | INFO  | xFrameworkWiring | BlueprintExtender  
  | 15 - org.apache.aries.blueprint.core - 1.4.3 | Destroying 
BlueprintContainer for bundle org.apache.karaf.bundle.core
2015-07-17 13:10:43,647 | INFO  | xFrameworkWiring | Activator  
  | 122 - org.ops4j.pax.web.pax-web-extender-war - 3.2.3 | Destroying 
extension for bundle org.apache.activemq.activemq-web-console
2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring | activemq-web-console - 
204}  | 108 - org.eclipse.jetty.aggregate.jetty-all-server - 
8.1.17.v20150415 | Destroying Spring FrameworkServlet 'dispatcher'
2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring | XmlWebApplicationContext   
  | 204 - org.apache.activemq.activemq-web-console - 5.11.1 | Closing 
WebApplicationContext for namespace 'dispatcher-servlet': startup date [Fri Jul 
17 13:10:41 PDT 2015]; parent: Root WebApplicationContext
2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring | DefaultListableBeanFactory 
  | 204 - org.apache.activemq.activemq-web-console - 5.11.1 | Destroying 
singletons in 
org.springframework.beans.factory.support.DefaultListableBeanFactory@5f8bdda8: 
defining beans 
[handlerMapping,/createDestination.action,/deleteDestination.action,/createSubscriber.action,/deleteSubscriber.action,/sendMessage.action,/purgeDestination.action,/deleteMessage.action,/copyMessage.action,/moveMessage.action,/deleteJob
.action,exceptionResolver]; parent: 
org.springframework.beans.factory.support.DefaultListableBeanFactory@63eb624a
2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring | XmlWebApplicationContext   
  | 204 - org.apache.activemq.activemq-web-console - 5.11.1 | Closing Root 
WebApplicationContext: startup date [Fri Jul 17 13:10:41 PDT 2015]; root of 
context hierarchy
2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring | DefaultListableBeanFactory 
  | 204 - org.apache.activemq.activemq-web-console - 5.11.1 | Destroying 
singletons in 
org.springframework.beans.factory.support.DefaultListableBeanFactory@63eb624a: 
defining beans 
[queueBrowser,messageQuery,queueConsumerQuery,queueProducerQuery,topicProducerQuery,topicSubscriberQuery,connectionQuery,placeholderConfig,sessionPool,configuration,brokerQuery,connectionFactory];
 root of factory hierarchy
2015-07-17 13:10:43,657 | INFO  | xFrameworkWiring | ContextHandler 
  | 108 - org.eclipse.jetty.aggregate.jetty-all-server - 8.1.17.v20150415 | 
stopped 
HttpServiceContext{httpContext=WebAppHttpContext{org.apache.activemq.activemq-web-console
 - 204}}
2015-07-17 13:10:43,667 | INFO  | xFrameworkWiring | HttpServiceFactoryImpl 
  | 116 - org.ops4j.pax.web.pax-web-runtime - 3.2.3 | Unbinding bundle: 
[org.apache.activemq.activemq-web-console [204]]
2015-07-17 13:10:43,687 | INFO  | xFrameworkWiring | BlueprintExtender  
  | 15 - org.apache.aries.blueprint.core - 1.4.3 | Destroying 
BlueprintContainer for bundle org.apache.karaf.kar.command
2015-07-17 13:10:43,707 | INFO  | xFrameworkWiring | BlueprintExtender  
  | 15 - org.apache.aries.blueprint.core - 1.4.3 | Destroying 
BlueprintContainer for bundle org.apache.camel.karaf.camel-karaf-commands
2015-07-17 13:10:43,767 | INFO  | xFrameworkWiring | BlueprintExtender  
  | 15 - org.apache.aries.blueprint.core - 1.4.3 | Destroying 
BlueprintContainer for bundle org.apache.karaf.webconsole.http
2015-07-17 13:10:43,767 | INFO  | xFrameworkWiring | HttpPlugin 
  | 148 - org.apache.karaf.webconsole.http - 3.0.4 | Http plugin deactivated
2015-07-17 13:10:43,777 | INFO  | xFrameworkWiring | BlueprintExtender  
  | 15 - org.apache.aries.blueprint.core - 1.4.3 | Destroying 
BlueprintContainer for bundle org.apache.karaf.features.command
2015-07-17 13:10:43,817 | INFO  | xFrameworkWiring | BlueprintExtender  
  | 15 - org.apache.aries.blueprint.core - 1.4.3 | Destroying 
BlueprintContainer for bundle org.apache.karaf.instance.command
2015-07-17 13:10:43,867 | INFO  | xFrameworkWiring | BlueprintExtender  
  | 15 - org.apache.aries.blueprint.core - 1.4.3 | Destroying 
BlueprintContainer for bundle org.apache.karaf.webconsole.console
2015-07-17 13:10:43,887 | INFO  | xFrameworkWiring | HttpServiceFactoryImpl 
  | 116 - org.ops4j.pax.web.pax-web-runtime - 3.2.3

LDAP examples

[Pratt, Jason]

Are there any good LDAP examples for Karaf-3.0.4 around?
I cannot seem to find any.

Regards,
Jason

RE: kar feature help

[Pratt, Jason]

When I do not include it, I receive the error below for both CXF and Spring.
Which doesn't make sense to me as /etc/org.apache.karaf.features.repos.cfg 
lists CXF and Spring with the latest features repo.
Why is this happening, is there a better way to reference these feature repos 
in my KAR?

java.lang.Exception: No feature named 'cxf' with version '3.1.1' available
at 
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatureDependency(FeaturesServiceImpl.java:636)[20:org.apache.karaf.features.core:3.0.4]
at 
org.apache.karaf.features.internal.FeaturesServiceImpl.doInstallFeature(FeaturesServiceImpl.java:564)[20:org.apache.karaf.features.core:3.0.4]
at 
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatureDependency(FeaturesServiceImpl.java:642)[20:org.apache.karaf.features.core:3.0.4]
at 
org.apache.karaf.features.internal.FeaturesServiceImpl.doInstallFeature(FeaturesServiceImpl.java:564)[20:org.apache.karaf.features.core:3.0.4]
at 
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:436)[20:org.apache.karaf.features.core:3.0.4]
at 
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:417)[20:org.apache.karaf.features.core:3.0.4]
at Proxyb3e2e50c_eabd_4835_806c_20c4bccdfcc9.installFeature(Unknown 
Source)[:]
at Proxy2509653b_3cba_4c20_8207_a6119b48e042.installFeature(Unknown 
Source)[:]
at 
org.apache.karaf.kar.internal.KarServiceImpl.installFeatures(KarServiceImpl.java:215)[45:org.apache.karaf.kar.core:3.0.4]
at 
org.apache.karaf.kar.internal.KarServiceImpl.install(KarServiceImpl.java:96)[45:org.apache.karaf.kar.core:3.0.4]
at 
org.apache.karaf.kar.internal.KarServiceImpl.install(KarServiceImpl.java:84)[45:org.apache.karaf.kar.core:3.0.4]
at Proxy3cd2476e_4be1_49bf_b66d_26b3e1015efd.install(Unknown Source)[:]
at Proxy7bd24bd0_890b_4622_9fb8_1642deac82ac.install(Unknown Source)[:]
at 
org.apache.karaf.deployer.kar.KarArtifactInstaller.install(KarArtifactInstaller.java:50)[47:org.apache.karaf.deployer.kar:3.0.4]
at Proxy69d3d736_1630_4837_b418_931f76243a61.install(Unknown Source)[:]
at 
org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:931)[7:org.apache.felix.fileinstall:3.5.0]
at 
org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:865)[7:org.apache.felix.fileinstall:3.5.0]
at 
org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:482)[7:org.apache.felix.fileinstall:3.5.0]
at 
org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:358)[7:org.apache.felix.fileinstall:3.5.0]
at 
org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:310)[7:org.apache.felix.fileinstall:3.5.0]


-Original Message-
From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] 
Sent: Wednesday, July 08, 2015 12:25 PM
To: user@karaf.apache.org
Subject: Re: kar feature help

You should not refer Karaf provided features repositories in your features XML 
(like spring for instance).

It seems that your classes use jersey for JAX-RS annotation, instead of CXF-RS. 
Can you double check there ?

Regards
JB

On 07/08/2015 09:13 PM, Pratt, Jason wrote:
> Hello,
>
> I am stumbling on why my CXF restful calls are failing now. I've asked 
> on the CXF user group and Sergey suggested I look at Christian's 
> tutorial code, which is what I used to setup the myapp up initially. 
> It was working when I was on Karaf-3.0.3 with no issues, but since 
> upgrading to 3.0.4 I began to use a KAR file to make team development 
> easier.
>
> I am hoping that I am just missing a bundle in my CXF feature, but I 
> am not sure. I have included it along with the error below.
>
> 
>
>  xmlns=/"http://karaf.apache.org/xmlns/features/v1.2.0"/>
>
> mvn:org.apache.cxf.karaf/_apache_-_cxf_/3.1.1/_xml_/featur
> es
>
> mvn:org.apache.camel.karaf/_apache_-camel/2.15.2/_xml_/fea
> tures
>
> mvn:org.ops4j.pax.jdbc/_pax_-_jdbc_-features/0.6.0/_xml_/f
> eatures
>
> mvn:org.apache.karaf.features/spring/3.0.3/_xml_/features<
> /repository>
>
>  2.1 persistence engine support"/ install=/"manual"/ 
> version=/"4.3.10"/>
>
> mvn:org.apache.geronimo.specs/_geronimo_-jta
> _1.1_spec/1.1.1
>
> mvn:org.hibernate.javax.persistence/_hiberna
> te_-_jpa_-2.1-_api_/1.0.0.Final
>
> mvn:org.apache.geronimo.specs/_geronimo_-ser
> vlet_3.0_spec/1.0
>
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundle
> s.antlr/2.7.7_5
>
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundle
> s.ant/1.8.4_1
>
> mvn:org.apache.servic

RE: kar feature help

[Pratt, Jason]

Hi JB - thanks for the response.

I double checked my POMs and there are no references to Jersey declared or 
resolved for any of the bundles. 

This is what I am using in my POM for the JAX-RS 



javax.ws.rs
jsr311-api
1.1.1


org.apache.cxf
cxf-rt-frontend-jaxrs
${cxf.version}


org.apache.cxf
cxf-rt-transports-http
${cxf.version}


org.apache.cxf
cxf-rt-transports-http-jetty
${cxf.version}


-Original Message-
From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] 
Sent: Wednesday, July 08, 2015 12:25 PM
To: user@karaf.apache.org
Subject: Re: kar feature help

You should not refer Karaf provided features repositories in your features XML 
(like spring for instance).

It seems that your classes use jersey for JAX-RS annotation, instead of CXF-RS. 
Can you double check there ?

Regards
JB

On 07/08/2015 09:13 PM, Pratt, Jason wrote:
> Hello,
>
> I am stumbling on why my CXF restful calls are failing now. I've asked 
> on the CXF user group and Sergey suggested I look at Christian's 
> tutorial code, which is what I used to setup the myapp up initially. 
> It was working when I was on Karaf-3.0.3 with no issues, but since 
> upgrading to 3.0.4 I began to use a KAR file to make team development 
> easier.
>
> I am hoping that I am just missing a bundle in my CXF feature, but I 
> am not sure. I have included it along with the error below.
>
> 
>
>  xmlns=/"http://karaf.apache.org/xmlns/features/v1.2.0"/>
>
> mvn:org.apache.cxf.karaf/_apache_-_cxf_/3.1.1/_xml_/featur
> es
>
> mvn:org.apache.camel.karaf/_apache_-camel/2.15.2/_xml_/fea
> tures
>
> mvn:org.ops4j.pax.jdbc/_pax_-_jdbc_-features/0.6.0/_xml_/f
> eatures
>
> mvn:org.apache.karaf.features/spring/3.0.3/_xml_/features<
> /repository>
>
>  2.1 persistence engine support"/ install=/"manual"/ 
> version=/"4.3.10"/>
>
> mvn:org.apache.geronimo.specs/_geronimo_-jta
> _1.1_spec/1.1.1
>
> mvn:org.hibernate.javax.persistence/_hiberna
> te_-_jpa_-2.1-_api_/1.0.0.Final
>
> mvn:org.apache.geronimo.specs/_geronimo_-ser
> vlet_3.0_spec/1.0
>
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundle
> s.antlr/2.7.7_5
>
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundle
> s.ant/1.8.4_1
>
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundle
> s.dom4j/1.6.1_5
>
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundle
> s.serp/1.15.1_1
>
> mvn:com.fasterxml/classmate/1.1.0
>
> mvn:org.javassist/_javassist_/3.18.2-GA
>
> mvn:org.jboss.spec.javax.security.jacc/_jboss_-_jacc_-api_1.4_
> spec/1.0.2.Final
>
> wrap:mvn:org.jboss/_jandex_/1.2.4.Final
>
> mvn:org.jboss.logging/_jboss_-logging/3.1.4.GA
>
> mvn:org.hibernate.common/_hibernate_-commons-annotations/4.0.5
> .Final
>
> mvn:com.zaxxer/HikariCP-java6/2.3.8
>
> mvn:org.hibernate/_hibernate_-core/4.3.10.Final
>
> mvn:org.hibernate/_hibernate_-_hikaricp_/4.3.10.Final
>
> mvn:org.hibernate/_hibernate_-_envers_/4.3.10.Final
>
> mvn:org.hibernate/_hibernate_-_entitymanager_/4.3.10.Final ndle>
>
> mvn:org.hibernate/_hibernate_-_osgi_/4.3.10.Final
>
> 
>
>  requirements for Karaf"/ install=/"auto"/ version=/"1.0.0"/>
>
> _jndi_
>
> _jdbc_
>
> _jms_
>
> _http_
>
> _http_-_whiteboard_
>
> _jetty_
>
> war
>
> _webconsole_
>
> _eventadmin_
>
> blueprint-web
>
> _aries_-annotation
>
> mvn:javax.annotation/javax.annotation-_api_/1.2
>
> 
>
>  requirements for Karaf"/ install=/"manual"/ version=/"1.0.0"/>
>
> _jpa_
>
> transaction
>
> _pax_-_jdbc_-_mysql_
>
> _pax_-_jdbc_-pool-dbcp2
>
> _pax_-_jdbc_-_config_
>
> mvn:mysql/_mysql_-connector-java/5.1.35 dle>
>
> mvn:org.apache.aries.jpa/org.apache.aries.jp
> a.blueprint.aries/1.0.2
>
> 
>
>  Karaf"/ install=/"manual"/ version=/"3.1.1"/>
>
> _cxf_
>
> _cxf_-core
>
> _cxf_-_wsdl_
>
> _cxf_-_http_
>
> _cxf_-_http_-_jetty_
>
> _cxf_-_jaxws_
>
> _cxf_-_jaxrs_
>
> mvn:org.apache.cxf/_cxf_-_rt_-_frontend_-_jaxrs_/3.1.1 >
>
> mvn:javax.ws.rs/javax.ws.rs-_api_/2.0.1
>
> 
>
>  for Karaf"/ install=/"auto"/ ve

kar feature help

[Pratt, Jason]

Hello,
I am stumbling on why my CXF restful calls are failing now. I've asked on the 
CXF user group and Sergey suggested I look at Christian's tutorial code, which 
is what I used to setup the myapp up initially. It was working when I was on 
Karaf-3.0.3 with no issues, but since upgrading to 3.0.4 I began to use a KAR 
file to make team development easier.

I am hoping that I am just missing a bundle in my CXF feature, but I am not 
sure. I have included it along with the error below.




http://karaf.apache.org/xmlns/features/v1.2.0";>
   
mvn:org.apache.cxf.karaf/apache-cxf/3.1.1/xml/features
   
mvn:org.apache.camel.karaf/apache-camel/2.15.2/xml/features
   
mvn:org.ops4j.pax.jdbc/pax-jdbc-features/0.6.0/xml/features
   
mvn:org.apache.karaf.features/spring/3.0.3/xml/features

   
mvn:org.apache.geronimo.specs/geronimo-jta_1.1_spec/1.1.1
mvn:org.hibernate.javax.persistence/hibernate-jpa-2.1-api/1.0.0.Final
mvn:org.apache.geronimo.specs/geronimo-servlet_3.0_spec/1.0

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.antlr/2.7.7_5

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.ant/1.8.4_1

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.dom4j/1.6.1_5

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.serp/1.15.1_1
mvn:com.fasterxml/classmate/1.1.0
mvn:org.javassist/javassist/3.18.2-GA

mvn:org.jboss.spec.javax.security.jacc/jboss-jacc-api_1.4_spec/1.0.2.Final
wrap:mvn:org.jboss/jandex/1.2.4.Final
mvn:org.jboss.logging/jboss-logging/3.1.4.GA

mvn:org.hibernate.common/hibernate-commons-annotations/4.0.5.Final
mvn:com.zaxxer/HikariCP-java6/2.3.8
mvn:org.hibernate/hibernate-core/4.3.10.Final
mvn:org.hibernate/hibernate-hikaricp/4.3.10.Final
mvn:org.hibernate/hibernate-envers/4.3.10.Final
mvn:org.hibernate/hibernate-entitymanager/4.3.10.Final
mvn:org.hibernate/hibernate-osgi/4.3.10.Final



jndi
jdbc
jms
http
http-whiteboard
jetty
war
webconsole
eventadmin
blueprint-web
aries-annotation
mvn:javax.annotation/javax.annotation-api/1.2



jpa
transaction
pax-jdbc-mysql
pax-jdbc-pool-dbcp2
pax-jdbc-config
mvn:mysql/mysql-connector-java/5.1.35
mvn:org.apache.aries.jpa/org.apache.aries.jpa.blueprint.aries/1.0.2



cxf
cxf-core
cxf-wsdl
cxf-http
cxf-http-jetty
cxf-jaxws
cxf-jaxrs
mvn:org.apache.cxf/cxf-rt-frontend-jaxrs/3.1.1
mvn:javax.ws.rs/javax.ws.rs-api/2.0.1


mvn:com.fasterxml.jackson.core/jackson-core/2.5.4

mvn:com.fasterxml.jackson.core/jackson-annotations/2.5.4
mvn:com.fasterxml.jackson.core/jackson-databind/2.5.4

mvn:com.fasterxml.jackson.jaxrs/jackson-jaxrs-json-provider/2.5.4
 
mvn:com.fasterxml.jackson.jaxrs/jackson-jaxrs-base/2.5.4
 mvn:org.codehaus.jackson/jackson-jaxrs/1.9.13
 mvn:org.codehaus.jackson/jackson-core-asl/1.9.13
 mvn:org.codehaus.jackson/jackson-mapper-asl/1.9.13



camel
camel-base64
camel-cache
camel-context
camel-couchdb
camel-eventadmin
camel-jetty
camel-jackson
camel-jdbc
camel-jms
camel-jmx
camel-jpa
camel-jsonpath
camel-paxlogging
camel-quartz2
camel-rabbitmq
camel-stream
camel-sql
camel-test





spring-dm
spring
spring-jdbc
spring-jms
spring-orm
spring-tx
spring-web




${project.description}
karaf-general
karaf-database
hibernate-4-jpa21
karaf-cxf
karaf-jackson
karaf-camel
karaf-spring








2015-07-07 12:39:37,869 | WARN  | tp1522718697-168 | PhaseInterceptorChain  
  | 181 - org.apache.cxf.cxf-core - 3.1.1 | Interceptor for 
{http://xxx/}$ProductLineServiceImpl777114985 has thrown exception, unwinding 
now

java.lang.RuntimeException: java.lang.ClassNotFoundException: 
org.glassfish.jersey.internal.RuntimeDelegateImpl not found by javax.ws.rs-api 
[244]

   at 
javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:152)

   at 
javax.ws.rs.ext.RuntimeDelegate.getInstance(RuntimeDelegate.java:120)

   at 
javax.ws.rs.core.Response$ResponseBuilder.newInstance(Response.java:848)

   at javax.ws.rs.core.Response.status(Response.java:613)

   at 
org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.processResponse(JAXRSOutInterceptor.java:111)[195:org.apache.cxf.cxf-rt-frontend-jaxrs:3.1.1]

   at 
org.apache.cxf.jaxrs.interceptor

K304 not releasing

[Pratt, Jason]

Hello - I've noticed that when redeploying a bundle into the /deploy directory 
that karaf is not able to release the old version and startup the new one. This 
also happens on a restart without "clean" enabled. However, when starting karaf 
using "clean" it starts up as expected. I am using a KAR file to ensure the 
require features and bundles are in place before adding my application bundles 
by hand.

Why is this happening?

KARAF-3.0.4
CXF-3.0.5
CAMEL-2.15.2
JDK-1.7


2015-07-08 11:41:21,122 | ERROR | FelixStartLevel  | BlueprintContainerImpl 
  | 15 - org.apache.aries.blueprint.core - 1.4.3 | Unable to start 
blueprint container for bundle core-product
org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to 
initialize bean checklistRestfulService
at 
org.apache.aries.blueprint.container.BeanRecipe.runBeanProcInit(BeanRecipe.java:714)[15:org.apache.aries.blueprint.core:1.4.3]
at 
org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:824)[15:org.apache.aries.blueprint.core:1.4.3]
at 
org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:787)[15:org.apache.aries.blueprint.core:1.4.3]
at 
org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:79)[15:org.apache.aries.blueprint.core:1.4.3]
at java.util.concurrent.FutureTask.run(FutureTask.java:262)[:1.7.0_79]
at 
org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:88)[15:org.apache.aries.blueprint.core:1.4.3]
at 
org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:245)[15:org.apache.aries.blueprint.core:1.4.3]
at 
org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:183)[15:org.apache.aries.blueprint.core:1.4.3]
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:682)[15:org.apache.aries.blueprint.core:1.4.3]
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:377)[15:org.apache.aries.blueprint.core:1.4.3]
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:269)[15:org.apache.aries.blueprint.core:1.4.3]
at 
org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:294)[15:org.apache.aries.blueprint.core:1.4.3]
at 
org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:263)[15:org.apache.aries.blueprint.core:1.4.3]
at 
org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:253)[15:org.apache.aries.blueprint.core:1.4.3]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)[9:org.apache.aries.util:1.1.0]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)[9:org.apache.aries.util:1.1.0]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)[9:org.apache.aries.util:1.1.0]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)[9:org.apache.aries.util:1.1.0]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)[9:org.apache.aries.util:1.1.0]
at 
org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1103)[org.apache.felix.framework-4.2.1.jar:]
at 
org.apache.felix.framework.util.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:695)[org.apache.felix.framework-4.2.1.jar:]
at 
org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:483)[org.apache.felix.framework-4.2.1.jar:]
at 
org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4403)[org.apache.felix.framework-4.2.1.jar:]
at 
org.apache.felix.framework.Felix.startBundle(Felix.java:2092)[org.apache.felix.framework-4.2.1.jar:]
at 
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1291)[org.apache.felix.framework-4.2.1.jar:]
at 
org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)[org.apache.felix.framework-4.2.1.jar:]
at java.lang.Thread.run(Thread.java:745)[:1.7.0_79]
Caused by: org.apache.cxf.service.factory.ServiceConstructionException
at 
org.apache.cxf.jaxrs.JAXRSServerFactoryBean.create(JAXRSServerFactoryBean.java:219)
at 
org.apache.cxf.jaxrs.JAXRSServerFactoryBean.init(JAXRSServerFactoryBean.java:142)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)[:1.7.0_79]
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImp

RE: blueprint spring error

[Pratt, Jason]

(AbstractRecipe.java:88)[15:org.apache.aries.blueprint.core:1.4.3]
at 
org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:245)[15:org.apache.aries.blueprint.core:1.4.3]
at 
org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:183)[15:org.apache.aries.blueprint.core:1.4.3]
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:682)[15:org.apache.aries.blueprint.core:1.4.3]
... 21 more
Caused by: java.lang.ClassNotFoundException: 
org.springframework.web.context.support.XmlWebApplicationContext not found by 
org.apache.cxf.cxf-rt-transports-http [201]
at 
org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1532)[org.apache.felix.framework-4.2.1.jar:]
at 
org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:75)[org.apache.felix.framework-4.2.1.jar:]
at 
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1955)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)[:1.8.0_45]
... 35 more

From: developm...@mobigov.com [mailto:developm...@mobigov.com]
Sent: Monday, July 06, 2015 9:24 AM
To: user@karaf.apache.org
Cc: Pratt, Jason
Subject: RE: blueprint spring error


does cxf 3.1.0 work ok with jetty 8.  I thought they moved to jetty 9 which is 
supported by karaf 4 for cxf 3.1.0 and greater.  It may be backwards compatible 
though.  I have not tested it.




On 2015-07-06 12:17, Pratt, Jason wrote:

I wasn't installing any spring feature, which is why I has some confusion. I 
thought perhaps CXF had something embedded that required it, but the site says 
after 3.1.0 it's been removed.

I am working through it today on karaf-3.0.4 to see.



-Original Message-

From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net<mailto:j...@nanthrax.net>]

Sent: Thursday, July 02, 2015 10:40 PM

To: user@karaf.apache.org<mailto:user@karaf.apache.org>

Subject: Re: blueprint spring error



By the what's the spring features you installed ?



If you karaf-spring, I don't see spring-dm-web and spring-web (which install 
spring-web and spring-webmvv). As the missing class is 
org/springframework/web/context/support/XmlWebApplicationContext, it's probably 
related.



Regards

JB



On 07/03/2015 01:38 AM, Pratt, Jason wrote:
I just started seeing this in my karaf-3.0.3 container after moving to using a 
KAR for provisioning. I am using CXF, Camel and Jackson to string a restful app 
together: 2015-07-02 16:28:22,889 | ERROR | FelixStartLevel | 
BlueprintContainerImpl | 15 - org.apache.aries.blueprint.core - 1.4.2 | Unable 
to start blueprint container for bundle core-product 
org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to 
instantiate components at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiat 
eEagerComponents(BlueprintContainerImpl.java:686)[15:org.apache.aries. 
blueprint.core:1.4.2] at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(Blue 
printContainerImpl.java:377)[15:org.apache.aries.blueprint.core:1.4.2] at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.run(Bluepr 
intContainerImpl.java:269)[15:org.apache.aries.blueprint.core:1.4.2] at 
org.apache.aries.blueprint.container.BlueprintExtender.createContainer 
(BlueprintExtender.java:294)[15:org.apache.aries.blueprint.core:1.4.2] at 
org.apache.aries.blueprint.container.BlueprintExtender.createContainer 
(BlueprintExtender.java:263)[15:org.apache.aries.blueprint.core:1.4.2] at 
org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle( 
BlueprintExtender.java:253)[15:org.apache.aries.blueprint.core:1.4.2] at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.cus 
tomizerModified(BundleHookBundleTracker.java:500)[9:org.apache.aries.u 
til:1.1.0] at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.cus 
tomizerModified(BundleHookBundleTracker.java:433)[9:org.apache.aries.u 
til:1.1.0] at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTra 
cked.track(BundleHookBundleTracker.java:725)[9:org.apache.aries.util:1 .1.0] at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bun 
dleChanged(BundleHookBundleTracker.java:463)[9:org.apache.aries.util:1 .1.0] at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEvent 
Hook.event(BundleHookBundleTracker.java:422)[9:org.apache.aries.util:1 .1.0] at 
org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(Sec 
ureAction.java:1103)[org.apache.felix.framework-4.2.1.jar:] at 
org.apache.felix.framework.util.EventDispatcher.createWhitelistFromHoo 
ks(EventDispatcher.java:695)[org.apache.felix.framework-4.2.1.jar:] at 
org.apache.felix.framework.util.EventDispatcher.fireB

RE: blueprint spring error

[Pratt, Jason]

I wasn't installing any spring feature, which is why I has some confusion. I 
thought perhaps CXF had something embedded that required it, but the site says 
after 3.1.0 it's been removed.
I am working through it today on karaf-3.0.4 to see.

-Original Message-
From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] 
Sent: Thursday, July 02, 2015 10:40 PM
To: user@karaf.apache.org
Subject: Re: blueprint spring error

By the what's the spring features you installed ?

If you karaf-spring, I don't see spring-dm-web and spring-web (which install 
spring-web and spring-webmvv). As the missing class is 
org/springframework/web/context/support/XmlWebApplicationContext, it's probably 
related.

Regards
JB

On 07/03/2015 01:38 AM, Pratt, Jason wrote:
> I just started seeing this in my karaf-3.0.3 container after moving to 
> using a KAR for provisioning. I am using CXF, Camel and Jackson to 
> string a restful app together:
>
> 2015-07-02 16:28:22,889 | ERROR | FelixStartLevel  |
> BlueprintContainerImpl   | 15 - org.apache.aries.blueprint.core
> - 1.4.2 | Unable to start blueprint container for bundle core-product
>
> org.osgi.service.blueprint.container.ComponentDefinitionException:
> Unable to instantiate components
>
>  at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiat
> eEagerComponents(BlueprintContainerImpl.java:686)[15:org.apache.aries.
> blueprint.core:1.4.2]
>
>  at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(Blue
> printContainerImpl.java:377)[15:org.apache.aries.blueprint.core:1.4.2]
>
>  at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(Bluepr
> intContainerImpl.java:269)[15:org.apache.aries.blueprint.core:1.4.2]
>
>  at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer
> (BlueprintExtender.java:294)[15:org.apache.aries.blueprint.core:1.4.2]
>
>  at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer
> (BlueprintExtender.java:263)[15:org.apache.aries.blueprint.core:1.4.2]
>
>  at
> org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(
> BlueprintExtender.java:253)[15:org.apache.aries.blueprint.core:1.4.2]
>
>  at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.cus
> tomizerModified(BundleHookBundleTracker.java:500)[9:org.apache.aries.u
> til:1.1.0]
>
>  at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.cus
> tomizerModified(BundleHookBundleTracker.java:433)[9:org.apache.aries.u
> til:1.1.0]
>
>  at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTra
> cked.track(BundleHookBundleTracker.java:725)[9:org.apache.aries.util:1
> .1.0]
>
>  at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bun
> dleChanged(BundleHookBundleTracker.java:463)[9:org.apache.aries.util:1
> .1.0]
>
>  at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEvent
> Hook.event(BundleHookBundleTracker.java:422)[9:org.apache.aries.util:1
> .1.0]
>
>  at
> org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(Sec
> ureAction.java:1103)[org.apache.felix.framework-4.2.1.jar:]
>
>  at
> org.apache.felix.framework.util.EventDispatcher.createWhitelistFromHoo
> ks(EventDispatcher.java:695)[org.apache.felix.framework-4.2.1.jar:]
>
>  at
> org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventD
> ispatcher.java:483)[org.apache.felix.framework-4.2.1.jar:]
>
>  at
> org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4403)[org.
> apache.felix.framework-4.2.1.jar:]
>
>  at
> org.apache.felix.framework.Felix.startBundle(Felix.java:2092)[org.apac
> he.felix.framework-4.2.1.jar:]
>
>  at
> org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1291)[
> org.apache.felix.framework-4.2.1.jar:]
>
>  at
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartL
> evelImpl.java:304)[org.apache.felix.framework-4.2.1.jar:]
>
>  at java.lang.Thread.run(Thread.java:745)[:1.8.0_45]
>
> Caused by: java.lang.NoClassDefFoundError:
> Lorg/springframework/web/context/support/XmlWebApplicationContext;
>
>  at java.lang.Class.getDeclaredFields0(Native 
> Method)[:1.8.0_45]
>
>  at
> java.lang.Class.privateGetDeclaredFields(Class.java:2583)[:1.8.0_45]
>
>  at 
> java.lang.Class.getDeclaredFields(Class.java:1916)[:1.8.0_45]
>
>  at
> org.apache.camel.blueprint.handler.CamelNamespaceHandler$CamelInjector
> .injectFields(CamelNamespaceHandler.java:787)
&

blueprint spring error

[Pratt, Jason]

I just started seeing this in my karaf-3.0.3 container after moving to using a 
KAR for provisioning. I am using CXF, Camel and Jackson to string a restful app 
together:

2015-07-02 16:28:22,889 | ERROR | FelixStartLevel  | BlueprintContainerImpl 
  | 15 - org.apache.aries.blueprint.core - 1.4.2 | Unable to start 
blueprint container for bundle core-product
org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to 
instantiate components
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:686)[15:org.apache.aries.blueprint.core:1.4.2]
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:377)[15:org.apache.aries.blueprint.core:1.4.2]
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:269)[15:org.apache.aries.blueprint.core:1.4.2]
at 
org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:294)[15:org.apache.aries.blueprint.core:1.4.2]
at 
org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:263)[15:org.apache.aries.blueprint.core:1.4.2]
at 
org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:253)[15:org.apache.aries.blueprint.core:1.4.2]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)[9:org.apache.aries.util:1.1.0]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)[9:org.apache.aries.util:1.1.0]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)[9:org.apache.aries.util:1.1.0]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)[9:org.apache.aries.util:1.1.0]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)[9:org.apache.aries.util:1.1.0]
at 
org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1103)[org.apache.felix.framework-4.2.1.jar:]
at 
org.apache.felix.framework.util.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:695)[org.apache.felix.framework-4.2.1.jar:]
at 
org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:483)[org.apache.felix.framework-4.2.1.jar:]
at 
org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4403)[org.apache.felix.framework-4.2.1.jar:]
at 
org.apache.felix.framework.Felix.startBundle(Felix.java:2092)[org.apache.felix.framework-4.2.1.jar:]
at 
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1291)[org.apache.felix.framework-4.2.1.jar:]
at 
org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)[org.apache.felix.framework-4.2.1.jar:]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_45]
Caused by: java.lang.NoClassDefFoundError: 
Lorg/springframework/web/context/support/XmlWebApplicationContext;
at java.lang.Class.getDeclaredFields0(Native Method)[:1.8.0_45]
at java.lang.Class.privateGetDeclaredFields(Class.java:2583)[:1.8.0_45]
at java.lang.Class.getDeclaredFields(Class.java:1916)[:1.8.0_45]
at 
org.apache.camel.blueprint.handler.CamelNamespaceHandler$CamelInjector.injectFields(CamelNamespaceHandler.java:787)
at 
org.apache.camel.blueprint.handler.CamelNamespaceHandler$CamelInjector.afterInit(CamelNamespaceHandler.java:918)
at 
org.apache.aries.blueprint.container.BeanRecipe.runBeanProcPostInit(BeanRecipe.java:744)
at 
org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:826)
at 
org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:787)
at 
org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:79)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_45]
at 
org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:88)[15:org.apache.aries.blueprint.core:1.4.2]
at 
org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:245)[15:org.apache.aries.blueprint.core:1.4.2]
at 
org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:183)[15:org.apache.aries.blueprint.core:1.4.2]
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:682)[15:org.apache.aries.blueprint.core:1.4.2]
... 18 more
Caused by: java.lang.ClassNotFoundException: 
org.springframework.web.context.support.XmlWebApplicationContext not found by 
or

RE: feature.xml

[Pratt, Jason]

So lowering the xmls to 1.2.0 and the karaf-maven-plugin to 3.0.3 now has the 
features installing and starting as desired.

I did have to modify my feature.xml and removed the dependency="true" from my 
bundle tags for it to work.

Is this a bug in the 1.3.0 and 4.0.0 of the xml and plugin?

-Original Message-
From: Pratt, Jason [mailto:jason.pr...@windriver.com] 
Sent: Wednesday, July 01, 2015 10:59 AM
To: user@karaf.apache.org
Subject: RE: feature.xml

Yes it works from the command line as expected.

I am using xmlns-1.3.0 with karaf-maven-plugin-4.0.0 

I am dropping the feature.xml into the /deploy directory. 

I'll drop to 1.2.0 and see if that has any effect, then drop to karaf-maven 
3.0.3 as well

-Original Message-
From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net]
Sent: Wednesday, July 01, 2015 10:15 AM
To: user@karaf.apache.org
Subject: Re: feature.xml

I guess it works with feature:repo-add && feature:install, right ?

What xmlns are you using ? Can you try with 1.2.0 ?

Regards
JB

On 07/01/2015 07:11 PM, Pratt, Jason wrote:
> Hello – I am trying out karaf-4.0.0 and wanted to see how feature.xml 
> are working in the /deploy directory. Is there a way to add a feature 
> to a feature.xml and have it install itself?
>
> Example:
>
>  install=/"auto"/ version=/"1.0.0"/>
>
> _jndi_
>
> 
>
> I see it does add the repo, but doesn’t install the feature.
>
> If I am reading http://karaf.apache.org/xmlns/features/v1.3.0
> correctly, install=auto won’t work for the jndi feature. Is there 
> another way to have it install itself from a features xml file?
>
> Thanks,
>
> Jason
>

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

RE: feature.xml

[Pratt, Jason]

Yes it works from the command line as expected.

I am using xmlns-1.3.0 with karaf-maven-plugin-4.0.0 

I am dropping the feature.xml into the /deploy directory. 

I'll drop to 1.2.0 and see if that has any effect, then drop to karaf-maven 
3.0.3 as well

-Original Message-
From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] 
Sent: Wednesday, July 01, 2015 10:15 AM
To: user@karaf.apache.org
Subject: Re: feature.xml

I guess it works with feature:repo-add && feature:install, right ?

What xmlns are you using ? Can you try with 1.2.0 ?

Regards
JB

On 07/01/2015 07:11 PM, Pratt, Jason wrote:
> Hello – I am trying out karaf-4.0.0 and wanted to see how feature.xml 
> are working in the /deploy directory. Is there a way to add a feature 
> to a feature.xml and have it install itself?
>
> Example:
>
>  install=/"auto"/ version=/"1.0.0"/>
>
> _jndi_
>
> 
>
> I see it does add the repo, but doesn’t install the feature.
>
> If I am reading http://karaf.apache.org/xmlns/features/v1.3.0 
> correctly, install=auto won’t work for the jndi feature. Is there 
> another way to have it install itself from a features xml file?
>
> Thanks,
>
> Jason
>

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

feature.xml

[Pratt, Jason]

Hello - I am trying out karaf-4.0.0 and wanted to see how feature.xml are 
working in the /deploy directory. Is there a way to add a feature to a 
feature.xml and have it install itself?

Example:


jndi


I see it does add the repo, but doesn't install the feature.

If I am reading http://karaf.apache.org/xmlns/features/v1.3.0 correctly, 
install=auto won't work for the jndi feature. Is there another way to have it 
install itself from a features xml file?

Thanks,
Jason

RE: karaf cxf jpa issue

[Pratt, Jason]

The entityManager getSingleResut() went off into the wild. I switched to using 
the List return and everything started working.

-Original Message-
From: Sobkowiak Krzysztof [mailto:krzys.sobkow...@gmail.com] 
Sent: Thursday, June 25, 2015 10:48 PM
To: user@karaf.apache.org
Subject: Re: karaf cxf jpa issue

Hi

What was the problem?

Regards
Krzysztof

On 26.06.2015 01:39, Pratt, Jason wrote:
>
> Fixed it
>
>  
>
> *From:*Pratt, Jason [mailto:jason.pr...@windriver.com]
> *Sent:* Thursday, June 25, 2015 9:12 AM
> *To:* user@karaf.apache.org
> *Subject:* karaf cxf jpa issue
>
>  
>
> Hello - I am getting a strange cast exception I haven't run into 
> before. I am trying to simply return a json document via a restful 
> call that loads a jpa entity by id number. The stack says I can't cast 
> from X to X, which doesn't make sense to me. I've followed
>
>  
>
> http://www.liquid-reality.de/display/liquid/2012/07/20/Apache+Karaf+Tu
> torial+Part+7+-+Camel+JPA+and+JTA+transactions
>
> http://www.liquid-reality.de/display/liquid/2011/12/22/Karaf+Tutorial+
> Part+4+-+CXF+Services+in+OSGi
>
>  
>
> in making this test up. I am not sure what I am doing wrong, any help 
> would be greatly appreciated
>
>  
>
>  
>
> @GET
>
> @Path("{id}")
>
> @Produces(MediaType.*/APPLICATION_JSON/*)
>
> *public*Test getTestById(@PathParam("id") Long id) {
>
>Test myTest= *null*;
>
>*/log/*.info("\n\n\n** getTestById id = "+ 
> id+"\n\n");
>
>
>
>*try*{
>
>myTest= (TestBean) 
> getEm().find(TestBean.*class*, id);
>
>*/log/*.info("test = "+ myTest.toString());
>
>} *catch*(Exception e) {
>
>*/log/*.error(">>> Caught getTestById: ", e);
>
>}
>
>*return*myTest;
>
> }
>
>  
>
> ID: 14
>
> Address: http://localhost:8181/cxf/test/600
>
> Http-Method: GET
>
> Content-Type:
>
> Headers: 
> {Accept=[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0
> .8], accept-encoding=[gzip, deflate], Accept-Language=[null], 
> connection=[keep-alive], Content-Type=[null], Host=[loc
>
> --
>
> 2015-06-24 18:43:26,240 | INFO  | qtp713727344-65  | TestServiceImpl  
> | 564 - product - 1.0.0 |
>
>  
>
>  
>
> ** getTestById id = 600
>
>  
>
>  
>
> 2015-06-24 18:43:57,610 | ERROR | qtp713727344-65  | TestServiceImpl  
> | 564 - product - 1.0.0 | >>> Caught getTestById:
>
> java.lang.ClassCastException: product.domain.TestBean cannot be cast 
> to product.domain.TestBean
>
> at 
> com.wrs.ept.dart.core.product.service.TestServiceImpl.getTestById(Test
> ServiceImpl.java:118)[564: product:1.0.0]
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)[:1.8.0_45]
>
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
> ava:62)[:1.8.0_45]
>
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
> orImpl.java:43)[:1.8.0_45]
>
> at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_45]
>
> at 
> org.apache.aries.proxy.impl.ProxyHandler$1.invoke(ProxyHandler.java:54
> )
>
> at 
> org.apache.aries.proxy.impl.ProxyHandler.invoke(ProxyHandler.java:119)
>
> at 
> com.wrs.ept.dart.core.product.service.$TestServiceImpl571557319.getTes
> tById(Unknown Source)[564: product:1.0.0]
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)[:1.8.0_45]
>
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
> ava:62)[:1.8.0_45]
>
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
> orImpl.java:43)[:1.8.0_45]
>
> at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_45]
>
> at 
> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(Abstr
> actInvoker.java:181)[317:org.apache.cxf.cxf-core:3.0.4]
>
> at 
> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.
> java:97)[317:org.apache.cxf.cxf-core:3.0.4]
>
> at 
> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:200)[441:or
> g.apache.cxf.cxf-rt-frontend-jaxrs:3.0.4]
>
> at 
> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:99)[441:org
> .apache.