Look like the persistence bundle you created cannot get the data source.
Check the data source configuration first whether you get the data source
from "jta-data-source" or "non-jta-data-source" inside persistence.xml
By the way, there is a bug inside OpenJPA under Osgi platform, this bug
prevents to get the data source from "jta-data-source" or from
"non-jta-data-source"
You must define the data source as bellows:
<properties>
<property name="openjpa.ConnectionURL"
value="jdbc:mysql://localhost:3306/office_pos"/>
<property name="openjpa.ConnectionDriverName"
value="com.mysql.jdbc.Driver"/>
<property name="openjpa.ConnectionUserName" value="username"/>
<property name="openjpa.ConnectionPassword" value="xxxx"/>
</properties>
and MUST remove jta-data-source and non-jta-data-source elements from
persistence.xml
best Rgds,
Tom
From: FERJANI [mailto:[email protected]]
Sent: Saturday, May 04, 2013 12:06 AM
To: [email protected]
Subject: Re: Waiting for namespace handlers
Hello Tim,
I added those bundles, and it worked ! thanks alot :)
Right know I have the following message, does it mean there are still
missing bundles to install ?
org.ops4j.pax.logging.pax-logging-api[org.apache.aries.blueprint.container.B
lueprintContainerImpl] : Bundle com.mycompany.me.clientjpa is waiting for
dependencies
[(&(&(!(org.apache.aries.jpa.proxy.factory=*))(osgi.unit.name=openjpa.osgi.i
test))(objectClass=javax.persistence.EntityManagerFactory))]
org.ops4j.pax.logging.pax-logging-api[org.apache.aries.blueprint.container.B
lueprintEventDispatcher] : Sending blueprint container event
BlueprintEvent[type=GRACE_PERIOD,
dependencies=[(&(&(!(org.apache.aries.jpa.proxy.factory=*))(osgi.unit.name=o
penjpa.osgi.itest))(objectClass=javax.persistence.EntityManagerFactory))]]
for bundle com.mycompany.me.clientjpa
Regards,
Khadija
On 05/03/2013 04:39 PM, Timothy Ward wrote:
>From the list of bundles you supplied it doesn't look like you have the jpa
or transaction namespace handlers installed. Any blueprint bundles you add
that use those namespaces won't work without them.
You need org.apache.aries.jpa.blueprint.aries and
org.apache.aries.transaction.blueprint to be installed and started.
Tim Ward
-------------------
Apache Aries PMC member & Enterprise OSGi advocate
Enterprise OSGi in Action (http://www.manning.com/cummins)
-------------------
_____
Date: Fri, 3 May 2013 16:24:36 +0100
From: [email protected]
To: [email protected]
Subject: Waiting for namespace handlers
Hello everyone,
I'm trying to run an example using blueprint and JPA but whenever I try to
start it, I have the following error:
[org.apache.aries.blueprint.container.BlueprintContainerImpl] : Running
blueprint container for bundle com.mycompany.me.clientjpa in state Unknown
[org.apache.aries.blueprint.container.BlueprintEventDispatcher] : Sending
blueprint container event BlueprintEvent[type=CREATING] for bundle
com.mycompany.me.clientjpa
[org.apache.aries.blueprint.container.BlueprintContainerImpl] : Running
blueprint container for bundle com.mycompany.me.clientjpa in state
WaitForNamespaceHandlers
[org.apache.aries.blueprint.container.BlueprintContainerImpl] : Bundle
com.mycompany.me.clientjpa is waiting for namespace handlers
[http://aries.apache.org/xmlns/jpa/v1.1.0]
[org.apache.aries.blueprint.container.BlueprintEventDispatcher] : Sending
blueprint container event BlueprintEvent[type=GRACE_PERIOD,
dependencies=[(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(os
gi.service.blueprint.namespace=http://aries.apache.org/xmlns/jpa/v1.1.0))]]
for bundle com.mycompany.me.clientjpa
It seems like blueprint container can not resolve the namespace for JPA
(transaction neither) and I don't know why or how to resolve it.
Here is a list of my installed bundles :
ID|State |Level|Name
0|Active | 0|System Bundle (4.2.1)
2|Active | 1|geronimo-jta_1.1_spec (1.1.1)
3|Active | 1|geronimo-servlet_2.5_spec (1.2.0)
4|Active | 1|Geronimo TxManager :: Transaction (2.1.3)
7|Active | 1|Aries JPA Container API (1.0.0)
8|Active | 1|Apache Aries Proxy Bundle (1.0.0)
9|Active | 1|Apache Aries Transaction Manager (1.0.0)
10|Active | 1|Apache Aries Util (1.0.0)
11|Active | 1|Apache Felix Bundle Repository (1.6.6)
12|Active | 1|Apache Felix Gogo Command (0.12.0)
13|Active | 1|Apache Felix Gogo Runtime (0.10.0)
14|Active | 1|Apache Felix Gogo Shell (0.10.0)
15|Active | 1|Apache Felix Log Service (1.0.1)
17|Active | 1|OSGi Release 4.0.1 Services (3.1.200.v20070605)
18|Active | 1|geronimo-j2ee-connector_1.5_spec (2.0.0)
19|Active | 1|Apache Geronimo JSR-317 JPA 2.0 Spec API (1.1.0)
21|Active | 1|OpenJPA OSGi Client Bundle (2.1.0.SNAPSHOT)
22|Active | 1|Apache Derby 10.5 (10.5.3000000.802917)
23|Active | 1|Commons Collections (3.2.1)
24|Active | 1|Commons Lang (2.5.0)
25|Active | 1|Commons Pool (1.5.4)
31|Active | 1|Apache Aries Application Default local platform
(1.0.0)
32|Active | 1|Apache Aries Application API (1.0.0)
34|Active | 1|Apache Aries Application Deployment Management
(1.0.0)
35|Active | 1|Apache Aries Application Installer (1.0.0)
36|Active | 1|Apache Aries Application No-op Resolver (1.0.0)
37|Active | 1|Apache Felix File Install (3.1.4)
38|Active | 1|Apache Aries Application Modelling (1.0.0)
39|Active | 1|Apache Aries Application Utils (1.0.0)
42|Active | 1|Apache Aries Application Management (1.0.0)
47|Active | 1|Apache Aries Blueprint Bundle (1.1.0)
53|Active | 1|osgi.enterprise (4.2.0.201003190513)
56|Active | 1|osgi.cmpn (4.3.1.201210102024)
57|Active | 1|osgi.core (5.0.0.201203141902)
58|Active | 1|osgi (3.0.0)
59|Active | 1|OPS4J Pax Web - Extender - WAR (0.8.1)
Regards,
Khadija
