Antw: Re: Problem with NamedXAResource.

Hi Benjamin! Thank you very much! That's indeed solved the issue. Best, Alexander >>> > Hi Alexander, you didn't name your JMS XA resource. Set a name property at JcaPooledConnectionFactory e.g. amq. That should solve this Exception Regards, Benjamin Am 15.12.2017 um 16:41 schrieb

Problem with NamedXAResource.

Hi there. Following the description on http://cxf.apache.org/docs/jms-transactions.html, I set up a JMS XA transaction together with pax-jdbc datasource in karaf 4.1.2. The datasource looks like this: osgi.jdbc.driver.name = mariadb dataSourceName = jmsTest databaseName = test user = test

Antw: Re: vaadin 8 wrapped jar dependency doesn't go active

Hi. Vaadin 8.1.4 uses gentyref version 1.2.0.vaadin1. I included that in my feature. Maybe working for 8.1.5 as well. http http-whiteboard mvn:org.jsoup/jsoup/1.8.3 mvn:com.vaadin.external/gentyref/1.2.0.vaadin1

Re: Antw: Re: OSGi Transaction control fails with hibernate

I'll give it a try. Maybe with a little guidance of you guys. First of all I'll try to inject a JTA TransactionManager into tx-control instead of the internal one. If that is working, I'll let you know. >>> On 14 Sep 2017, at 10:46, Guillaume Nodet wrote: 2017-09-14

RE: Antw: RE: pax-web-jetty bundle is unable to find class com.ctc.wstx.stax.WstxInputFactory

Hi Stephan. OMG, it's so easy! 1st of all, you are right. It's (if anyways) an issue of war support, not pax-web. 2nd: It's not an issue at all. I didn't have the Import-Package for com.ctc.wstx.stax in the war bundle. As soon as I add it, I don't need the fragment any more. Thanks! Bast

Re: Antw: Re: OSGi Transaction control fails with hibernate

Hi Tim. I'm using the 2.6.1 version of aries jpa support already. Normal transaction control with blueprint and @Transactional annotation was working fine. To have better control over startup dependencies and cope with disappearing and appearing services during runtime we invest some time in a

Re: Antw: Re: OSGi Transaction control fails with hibernate

Thanks Tim for the update. I tried the approach with providing a factory config in karaf.dir/etc/org.apache.aries.tx.control.jpa.xa.cfg with config as: osgi.unit.name=DSContext2 osgi.jdbc.driver.class=org.h2.Driver url=jdbc:h2:mem:article user=sa password= whilst having a mininmal

Antw: Re: OSGi Transaction control fails with hibernate

Hi Tim, I use a JPAEntityManagerProviderFactory (providerFactory) which I inject as a service reference into my repository class. Furthermore, I inject a EntityManagerFactory (emf) into the repository class as well as the TransactionControl (txControl). The provider Factory is created by

OSGi Transaction control fails with hibernate

Hello. I'm trying to get tx-control with XA transactions running (local is working). I found that tx-control opens a JTA transaction using RecoveryWorkAroundTransactionManager (derived from geronimo's TransactionManager Implementation) explicitly instead of using the registered

Antw: RE: pax-web-jetty bundle is unable to find class com.ctc.wstx.stax.WstxInputFactory

Hi Matt. Well, setting the thread's class loader clearly assumes knowledge of the internals of the used components. When the implementation of the dependent components change changes, your implementation may break or cease to work correctly. I consider setting the bundle classloader a code

pax-web-jetty bundle is unable to find class com.ctc.wstx.stax.WstxInputFactory

Hi all. I wrote a servlet filter to be used in a web (WAR) deployment. The servlet filter performs a remote request to a SOAP service with a configurable WSDL location. So the wsdl is not known locally to the web project. When creating the SOAP client, I get an exception the stacktrace of

Re: Antw: Re: Require-Capability with effective:=active not ignored

Hello Tim. How am I to use DS with @Component annotaition when having blueprint-maven-plugin in place! Is it possible anyways? Regards, Alexander. >>> Hi Tim. Well, maybe I made myself not completely clear. Of course it is possible to mix DS and blueprint even in the same bundle when you use

Re: Antw: Re: Require-Capability with effective:=active not ignored

Hi Tim. Well, maybe I made myself not completely clear. Of course it is possible to mix DS and blueprint even in the same bundle when you use services for communication but as you say, it's normally not a good idea. > Mixing blueprint and DS in the same bundle isn’t > normally a good idea, but

Antw: Re: Require-Capability with effective:=active not ignored

Hello Tim. Thanks for the quick response and the clarification. In fact it's exactly like you described. My intention is to postpone the STARTING/ACTIVE state until a certain requirement is fulfilled. Using DS is currently not an option as the whole project uses blueprint and the mix of DS and

Require-Capability with effective:=active not ignored

Hi there. According to http://osgi-dev.mail.osgi.narkive.com/GfJqfPGZ/require-capability-osgi-service-filter-effective-active-and-blueprint (and the OSGi spec), a R-C header with effective:=active should be ignored by OSGi framework. But when I create a R-C header like Require-Capability:

Antw: Re: Pax-JDBC 1.1 hikari pool and XA Support

I thought I was using Aries Transaction Manager still? Does it mean, that hikari pooling does not support XA? When I use aries pooling, it complains about "Unable to recover XADataSource: aries.xa.name property not set". I tried to set it in the pax-jdbc datasource file but it doesn't seem to

Pax-JDBC 1.1 hikari pool and XA Support

When using pax-jdbc 1.1.0 (on karaf 4.0.8) to be able to use hikari pool support everything is working fine until I switch on XA support. In this case the DataSource is not created! When I comment out the XA support from the datasource factory config file, the DataSource pops up again. I have

Antw: Using maven bundle plugin to compile and bundle code not in src/main/java

Hello Tom. It's nothing to do with the bundle plugin at all. All you have to do is to set the sourceDirectory tag in the pom file (as subnode of build node). Please have a look here: https://maven.apache.org/guides/mini/guide-using-one-source-directory.html