Nicole, I've run into that as well. Sometime between the first and second versions, I managed to move the OSGiHost interface. For now, I've put it in the spi.host package, although it may finally reside in host-api.
Not having OSGiHost will cause the binding to fail to load. I'd imagine if you did an 'ss' (short status) on your osgi console, you'd find that the osgi binding bundle was not active. I've managed to get both the Axis2 and Spring extensions to install and resolve. I'm in the process of getting the supply chain example I sent you to work with a WS-bound client and a Spring bean shipper. I'll keep you posted on my progress. Cheers, Joel -----Original Message----- From: Wengatz, Nicole [mailto:[EMAIL PROTECTED] Sent: Friday, November 17, 2006 12:05 PM To: [email protected] Subject: RE: Bundles and OSGi Hi Joel, I have some problems to get your latest prototype running. In the source files I got from you the OSGiHost seems to be packaged in spi.host, e.g.: >import org.apache.tuscany.spi.host.OSGiHost in class OSGiReference In my installation it's in: >org.apache.tuscany.host.osgi.OSGiHost; What's the right location? This difference caused some problems with the Manifests. I was not able to start the Equinox bundle and the binding-osgi could not import the OSGiHost. After adapting manifests and source files I was able to start the four tuscany-osgi bundles :-) BUT, when starting the test bundles, I get the following exception: >org.apache.tuscany.spi.loader.UnrecognizedElementException: >{http://tuscany.apache.org/xmlns/osgi/1.0}binding.osgi >[{http://tuscany.apache.org/xmlns/osgi/1.0}binding.osgi] >Context stack trace: [default_shipper] > at org.apache.tuscany.core.loader.LoaderRegistryImpl.load(LoaderRegistryImp l.java:92) > at org.apache.tuscany.core.loader.ServiceLoader.load(ServiceLoader.java:84) > at org.apache.tuscany.core.loader.ServiceLoader.load(ServiceLoader.java:1) > at org.apache.tuscany.core.loader.LoaderRegistryImpl.load(LoaderRegistryImp l.java:94) > at org.apache.tuscany.core.implementation.composite.CompositeLoader.load(Co mpositeLoader.java:81) > at org.apache.tuscany.core.implementation.composite.CompositeLoader.load(Co mpositeLoader.java:1) > at org.apache.tuscany.core.loader.LoaderRegistryImpl.load(LoaderRegistryImp l.java:94) > at org.apache.tuscany.core.loader.LoaderRegistryImpl.load(LoaderRegistryImp l.java:112) > at org.apache.tuscany.core.implementation.composite.CompositeComponentTypeL oader. >loadFromSidefile(CompositeComponentTypeLoader.java:65) > at org.apache.tuscany.core.implementation.composite.CompositeComponentTypeL oader. >load(CompositeComponentTypeLoader.java:57) > at org.apache.tuscany.core.implementation.composite.CompositeComponentTypeL oader. >load(CompositeComponentTypeLoader.java:1) > at org.apache.tuscany.core.loader.LoaderRegistryImpl.loadComponentType(Load erRegistryImpl.java:163) > at org.apache.tuscany.core.deployer.DeployerImpl.load(DeployerImpl.java:101 ) > at org.apache.tuscany.core.deployer.DeployerImpl.deploy(DeployerImpl.java:7 6) > at org.apache.tuscany.sca.osgi.core.deployer.OSGiDeployer.deploy(OSGiDeploy er.java:42) > at org.apache.tuscany.core.runtime.AbstractRuntime.deployApplicationScdl(Ab stractRuntime.java:136) > at org.apache.tuscany.sca.osgi.core.runtime.OSGiRuntime.startApplication(OS GiRuntime.java:127) > at org.apache.tuscany.sca.osgi.core.impl.AbstractSCAComponentManager. >addBundleComponents(AbstractSCAComponentManager.java:144) > at org.apache.tuscany.sca.osgi.core.impl.AbstractSCAComponentManager. >processStartedBundle(AbstractSCAComponentManager.java:173) > at org.apache.tuscany.sca.osgi.core.impl.AbstractSCAComponentManager. >bundleChanged(AbstractSCAComponentManager.java:189) > at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent (BundleContextImpl.java:1206) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventMana ger.java:189) > at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchrono us(ListenerQueue.java:141) > at org.eclipse.osgi.framework.internal.core.Framework.publishBundleEvent(Fr amework.java:1432) > at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHo st.java:326) > at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractB undle.java:329) > at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framewor k.java:1037) > at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles (StartLevelManager.java:573) > at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(Start LevelManager.java:495) > at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLev el(StartLevelManager.java:275) > at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent (StartLevelManager.java:455) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventMana ger.java:189) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventMa nager.java:291) It seems that tuscany is not recognizing the OSGi-Binding anymore. Any idea what could be the problem? Thanks Nicole --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
