Hi Aries developers,
This Blueprint :
bean id=xmiSiteCatalogSupplier
class=org.soluvas.commons.XmiObjectLoaderlt;org.soluvas.web.site.SiteCataloggt;
argument value=org.soluvas.web.site.SitePackage /
argument value=id.co.bippo.common.PersonRef /
argument value=bippo.SiteCatalog.xmi /
/bean
While you are still on-line, may I ask you for some clarifications;
persistence.xml: the following apparently doesn't work:
jta-data-sourceosgi:service/javax.sql.DataSource/(osgi.jndi.service.name=jpa/jtaStagingDb
xa=true)/jta-data-source
datasource blueprint? : neither this
service
Hi
The bit in brackets for the jndi name is an ldap filter (just like a service
lookup). What you want is
((osgi.jndi.service.name=jpa/jtaStagingDb)(xa=true))
You don't need to add entry key=xa value=true / to your service
export, that gets added by the transaction wrappers bundle when
... my progress so far :
With this line in the persistence.xml
jta-data-sourceosgi:service/javax.sql.DataSource/(amp;(osgi.jndi.service.name=jpa/jtaStagingDb)(xa=true))/jta-data-source
Yet, the result is still as before: all the participating transactions
apart from the offending one got
Yes.
On 21/10/2012 12:48 AM, Timothy Ward wrote:
This was in addition to changing your datasource blueprint to:
service id=xaDataSource ref=stagingXADataSource
interface=javax.sql.XADataSource
service-properties
entry key=osgi.jndi.service.name value=jpa/jtaStagingDb /
In which case it is starting to sound as though there might be a problem with
the db driver. Have you tried it with derby or similar?
Tim
Date: Sun, 21 Oct 2012 00:49:14 +1030
From: a...@solveitsoftware.com
To: user@aries.apache.org
Subject: Re: Aries eclipselink.adapter
What John describes should work, but will tie imports to the specific
provider bundle. If you're using equinox, it exports all packages at
version 0.0.0 but the resolver will still prefer system packages
unless you set osgi.resolver.preferSystemPackages=false. Once you've
done the import for
