Hi Matt, On 1 June 2011 15:39, Matt Madhavan <[email protected]> wrote: > Hi Valentine, > When you say JPA namespace handler do you mean its a bundle itself? I'm not
Can you confirm your com.xxxx.osgi.samples.bank.persistence is waiting for namespace bundle is using either the http://aries.apache.org/xmlns/jpa/v1.0.0 or http://aries.apache.org/xmlns/jpa/v1.1.0 namespace in its blueprint xml? If so then you'll need to make sure Felix starts the org.apache.aries.jpa.blueprint.aries bundle. This bundle uses Blueprint itself to register the namespace handler for http://aries.apache.org/xmlns/jpa/v1.0.0 and http://aries.apache.org/xmlns/jpa/v1.1.0 > sure what to look for here! Also could you explain what do you mean by "If > the namespace handler does not become available"? One scenario would be if you haven't started the org.apache.aries.jpa.blueprint.aries bundle which contains the NS handler you need. > > In the console it says the Blueprint container for the persitence bundle was > unable to start. But the felix shows that it is "active"? The OSGi bundle state has reached 'active' but this doesn't reflect the Blueprint container state. Changes to the Blueprint container state will continue after the bundle has become active. > Any more ideas please! > Matt > > On Wed, Jun 1, 2011 at 1:46 AM, Valentin Mahrwald <[email protected]> > wrote: >> >> Hi Matt, >> the waiting for namespace handlers message comes up when a bundle uses >> additional namespaces in the Blueprint XML but at the time the bundle is >> started the namespace handler service is not available. In the case of the >> persistence bundle >> I would imagine it is probably waiting for the JPA namespace handler (the >> one that handles http://aries.apache.org/xmlns/jpa/v1.0.0 or 1.1.0 and lives >> in the org.apache.aries.jpa.blueprint.aries bundle). If that namespace >> handler does not become available then the Blueprint won't be created. >> You can check in the console if the Blueprint container gets registered >> for the persistence bundle then the namespace handler was found and the >> Blueprint was processed. In that case the problem you see must be something >> about the reference not matching the service. Otherwise the Blueprint for >> the persistence bundle never started and that explains the missing service >> for the BIZ bundle. >> Hope this helps a bit, >> Valentin >> On 31 May 2011, at 23:34, Matt Madhavan wrote: >> >> Hello, >> I'm running (trying to run) a web app inside Felix Container. One of my >> bundle (persistence bundle) is complaining as follows: >> g! [Blueprint Extender: 2] INFO >> org.apache.aries.blueprint.container.BlueprintContainerImpl - Bundle >> com.xxxx.osgi.samples.bank.persistence is waiting for namespace handlers >> This bundle exports a service named: >> com.xxxx.osgi.samples.bank.api.persistence.BankPersistenceService >> Meanwhile another bundle (BIZ bundle) timesout waiting for this service >> from the above bundle as follows: >> g! [Blueprint Extender: 2] ERROR >> org.apache.aries.blueprint.container.BlueprintContainerImpl - Unable to >> start blueprint container for bundle >> com.xxxx.osgi.samples.bank.biz due to unresolved dependencies >> (objectClass=com.xxxx.osgi.samples.bank.api.persistence.BankPersistenceService)] >> java.util.concurrent.TimeoutException >> at >> org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run >> >> >> Been stuck on this for a while? Any ideas please? >> >> Thanks in advance! >> Matt >> > >
