Hi Anatoly,
thank you for your answer. It did not help though, sorry. I do ignore
the message too now. In the meantime, I have another problem (posted it
to the mailing list).
Regards
Christian
Am 16.10.12 02:53, schrieb Anatoly Osiko:
I have the same log message and tend to ignore it.
I played with aries 1.0.0 + eclipselink + equinox 3.7.2 combination,
then switched to aries 1.0.0 + openjpa + equinox 3.7.2.
Transactions rollback don't work for me (both eclipselink or openjpa)
- I reported this issue in one of my earlier messages - but doubt this
one is the cause of the problem.
The excerpt from the log:
osgi> Time to load bundles: 214
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Enabling SLF4J API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Enabling Jakarta Commons Logging API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Enabling Log4J API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Enabling Avalon Logger API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Enabling JULI Logger API support.
org.apache.aries.jpa.container.context[org.apache.aries.jpa.container.context]
: A TransactionSynchronizationRegistry service is
now available in the runtime. Managed persistence contexts will now
integrate with JTA transactions using {javax.transaction.Tr
ansactionManager,
javax.transaction.TransactionSynchronizationRegistry,
javax.transaction.UserTransaction, org.apache.geronimo.t
ransaction.manager.RecoverableTransactionManager}={service.id=43}.
org.apache.aries.jpa.container.context[org.apache.aries.jpa.container.context]
: No quiesce support is available, so managed per
sistence units will not participate in quiesce operations.
org.apache.aries.jpa.container[org.apache.aries.jpa.container] : The
file org.apache.aries.jpa.container.properties was not foun
d in bundle org.apache.aries.jpa.container/1.0.0. The default
properties {} will be used.
org.apache.aries.jpa.container[org.apache.aries.jpa.container] :
Adding a provider: {javax.persistence.spi.PersistenceProvider}=
{javax.persistence.provider=org.apache.openjpa.persistence.PersistenceProviderImpl,
service.id=39}
org.apache.aries.jpa.container[org.apache.aries.jpa.container] :
Located Persistence descriptors: [META-INF/persistence-jta.xml]
in bundle com.solveit.integration.train_1.0.0.qualifier
org.apache.aries.jpa.container[org.apache.aries.jpa.container] : The
bundle com.solveit.integration.train/1.0.0.qualifier is alr
eady active, it may not be possible to create managed persistence
units for it.
org.apache.aries.jpa.container[org.apache.aries.jpa.container] :
Located Persistence units: [Persistence unit integration.train
in bundle com.solveit.integration.train_1.0.0.qualifier]
*org.apache.aries.jpa.container[org.apache.aries.jpa.container] : The
org.osgi.service.jdbc package is unavailable. As a result t**
**he Aries JPA container will not offer any DataSourceFactory
integration.*
org.apache.aries.jpa.container[org.apache.aries.jpa.container] :
Located Persistence descriptors: [META-INF/persistence-jta.xml]
in bundle com.solveit.integration.employee_1.0.0.qualifier
org.apache.aries.jpa.container[org.apache.aries.jpa.container] : The
bundle com.solveit.integration.employee/1.0.0.qualifier is
already active, it may not be possible to create managed persistence
units for it.
org.apache.aries.jpa.container[org.apache.aries.jpa.container] :
Located Persistence units: [Persistence unit integration.employ
ee in bundle com.solveit.integration.employee_1.0.0.qualifier]
org.apache.aries.jpa.container[org.apache.aries.jpa.container] : No
quiesce support is available, so managed persistence units w
ill not participate in quiesce operations.
[Framework Event Dispatcher] DEBUG
org.ops4j.pax.logging.pax-logging-service - BundleEvent STARTED
[Start Level Event Dispatcher] DEBUG
org.apache.aries.blueprint.container.BlueprintExtender - Starting
blueprint extender...
[Framework Event Dispatcher] DEBUG com.solveit.integration.util.osgi -
BundleEvent STARTED
[Start Level Event Dispatcher] DEBUG org.apache.aries.blueprint -
ServiceEvent REGISTERED
..............................................
Sorry, I am not able to shed more light on this log entry, whether
it's an issue or not - I am just a humble user, that wants to bring
the declarative transaction support, that I enjoyed on non-osgi
platform with Spring framework, back to osgi based platform.
Regards,
Anatoly
On 15/10/2012 8:31 PM, Christian Eugster wrote:
To learn blueprint and container managed jpa I have setup a simple
project with aries 1.0.0, eclipselink 2.4.0 (with
aries.eclipselink.adapter) and equinox 3.8.x.
I have a bundle ch.eugster.herakles.datasource.derby that provides
datasources for a memory database (heraklesdb).
The bundle ch.eugster.herakles.persistence contains the entity and
dao classes and a persistence.xml and an orm.xml.
When I run the example I get the following output (picked from the
console) in the console, that rise some questions:
...
INFO: The org.osgi.service.jdbc package is unavailable. As a result
the Aries JPA container will not offer any DataSourceFactory
integration.
...
I know, that I have the osgi.enterprise bundle on the classpath. Why
does it say, the org.osgi.service.jdbc package is unavailable? The
osgi container is set to default auto-start: true, default start
level is 4 the osgi.enterprise bundle I have set to start level 3.
Thank you!
--
Anatoly Osiko
Software Engineer, Integration
SolveIT Software Pty Ltd
Adelaide | Brisbane | Chisinau | Melbourne | Perth
D: +61 8 7071 4918
T: +61 8 8221 5533
M: +61 4 1980 0386
F: +61 8 8221 5677
SolveIT Software Building
Level 1, 99 Frome Street,
Adelaide, SA 5000
www.SolveITSoftware.com
