>> This is a new method added to the JPA service API in version 1.1. If
>> you’re seeing it appear as a LinkageError, a NoSuchMethodError, or
>> possibly an AbstractMethodError then this indicates that you have a 1.0
>> implementation deployed that has broken import metadata (i.e. it’s
>>
Hi Tim
Tim Ward-2 wrote
> I note that since the last set of logs/trace the version of EclipseLink
> has increased from 2.6.x to 2.7.x. This changes the JPA version from 2.1
> to 2.2, which currently isn’t supported by Aries JPA or the Tx Control JPA
> provider. This will be one of the issues.
I
Hi Tim
Tim Ward-2 wrote
> I note that since the last set of logs/trace the version of EclipseLink
> has increased from 2.6.x to 2.7.x. This changes the JPA version from 2.1
> to 2.2, which currently isn’t supported by Aries JPA or the Tx Control JPA
> provider. This will be one of the issues.
I
I can see that I am getting closer to the solution.
To install the version 1.0.0 of the Transaction Control, I had to install
version 2.7.1 of Aries JPA Container.
Now I am getting this error:
org.osgi.service.jpa.EntityManagerFactoryBuilder.getPersistenceProviderName()Ljava/lang/String;
I came
Hi,
The XA support that you are trying to use was added in
https://github.com/apache/aries/commit/6d1943b4d7c019968610256353abd36b34c54285
and so isn’t part of the (rather elderly) 0.0.3 release that you are using. If
you want working XA transactions with EclipseLink 2.6.0 then you will need
Hi Tim
Thanks for all your help.
I changed my code to use the JPAEntityManagerProvider that is created when I
drop in my configuration as explained by the "Creating a resource using a
factory configuration" part here:
http://aries.apache.org/modules/tx-control/xaJPA.html
Hi,
So using the EntityManagerFactoryBuilder and the
JPAEntityManagerProviderFactory services is the lowest level way to set this
up, and it requires a bit more setup than you are currently doing. I would
normally recommend using configuration to directly create the
JPAEntityManagerProvider
When switching to the vanilla DataSourceFactory the error disappears but now
when I try to access the entity manager from the JPAEntityManagerProvider it
throws this error:
/Unable to acquire a connection from driver [null], user [null] and URL
[null]. Verify that you have set the expected
Hi,
I don’t know the specifics of what is going on here, but it is not recommended
to use a pooled datasource factory wrapper with Transaction Control (which does
its own pooling). You would be better off using the vanilla DataSourceFactory
service for mysql.
Also, you may wish to update to
I am using Karaf 4.0.3 with the following features enabled:
jndi
transaction-api
transaction
jpa
eclipselink
pax-jdbc-config
pax-jdbc-mysql
pax-jdbc-pool-aries
mvn:javax.validation/validation-api/1.1.0.Final
10 matches
Mail list logo
