Hi Nicole, I'm working with the current open code line, although things have been a bit active since I submitted this work. I hope it still compiles!
As for your other questions (about missing bundles), here're the manifests: Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-Name: Tuscany_spec_sca Plug-in Bundle-SymbolicName: tuscany.spec.sca Bundle-Version: 1.0.0 Bundle-Localization: plugin Import-Package: org.osgi.framework;version="1.3.0" Export-Package: org.osoa.sca, org.osoa.sca.annotations Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-Name: Tuscany_osgi_sca_spi Plug-in Bundle-SymbolicName: tuscany.osgi.sca.spi Bundle-Version: 1.0.0 Bundle-Localization: plugin Import-Package: org.osgi.framework;version="1.3.0", org.osoa.sca, org.osoa.sca.annotations Require-Bundle: tuscany_external_dependencies Export-Package: org.apache.tuscany.spi, org.apache.tuscany.spi.annotation, org.apache.tuscany.spi.bootstrap, org.apache.tuscany.spi.builder, org.apache.tuscany.spi.component, org.apache.tuscany.spi.deployer, org.apache.tuscany.spi.event, org.apache.tuscany.spi.extension, org.apache.tuscany.spi.host, org.apache.tuscany.spi.loader, org.apache.tuscany.spi.model, org.apache.tuscany.spi.monitor, org.apache.tuscany.spi.policy, org.apache.tuscany.spi.services, org.apache.tuscany.spi.services.artifact, org.apache.tuscany.spi.services.info, org.apache.tuscany.spi.services.work, org.apache.tuscany.spi.services.wsdl, org.apache.tuscany.spi.wire Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-Name: Tuscany_external_dependencies Plug-in Bundle-SymbolicName: tuscany_external_dependencies Bundle-Version: 1.0.0 Bundle-Activator: tuscany_external_dependencies.Activator Bundle-Localization: plugin Import-Package: org.osgi.framework;version="1.3.0" Bundle-ClassPath: lib/commonj-twm.jar, lib/geronimo-connector-1.0.jar, lib/geronimo-j2ee_1.4_spec-1.0.jar, lib/geronimo-j2ee-connector_1.5_spec-1.0.jar, lib/geronimo-transaction-1.0.jar, lib/stax-api-1.0.jar, ., lib/wsdl4j-1.5.2.jar, lib/wstx-asl-2.9.3.jar Export-Package: com.ctc.wstx.api, com.ctc.wstx.cfg, com.ctc.wstx.compat, com.ctc.wstx.dom, com.ctc.wstx.dtd, com.ctc.wstx.ent, com.ctc.wstx.evt, com.ctc.wstx.exc, com.ctc.wstx.io, com.ctc.wstx.msv, com.ctc.wstx.sr, com.ctc.wstx.stax, com.ctc.wstx.sw, com.ctc.wstx.util, com.ibm.wsdl, com.ibm.wsdl.extensions, com.ibm.wsdl.extensions.http, com.ibm.wsdl.extensions.mime, com.ibm.wsdl.extensions.schema, com.ibm.wsdl.extensions.soap, com.ibm.wsdl.factory, com.ibm.wsdl.util, com.ibm.wsdl.util.xml, com.ibm.wsdl.xml, commonj.timers, commonj.work, javax.activation, javax.ejb, javax.ejb.spi, javax.enterprise.deploy.model, javax.enterprise.deploy.model.exceptions, javax.enterprise.deploy.shared, javax.enterprise.deploy.shared.factories, javax.enterprise.deploy.spi, javax.enterprise.deploy.spi.exceptions, javax.enterprise.deploy.spi.factories, javax.enterprise.deploy.spi.status, javax.jms, javax.mail, javax.mail.event, javax.mail.internet, javax.mail.search, javax.management.j2ee, javax.management.j2ee.statistics, javax.resource, javax.resource.cci, javax.resource.spi, javax.resource.spi.endpoint, javax.resource.spi.security, javax.resource.spi.work, javax.security.jacc, javax.servlet, javax.servlet.http, javax.servlet.jsp, javax.servlet.jsp.el, javax.servlet.jsp.tagext, javax.transaction, javax.transaction.xa, javax.wsdl, javax.wsdl.extensions, javax.wsdl.extensions.http, javax.wsdl.extensions.mime, javax.wsdl.extensions.schema, javax.wsdl.extensions.soap, javax.wsdl.factory, javax.wsdl.xml, javax.xml, javax.xml.namespace, javax.xml.registry, javax.xml.registry.infomodel, javax.xml.rpc, javax.xml.rpc.encoding, javax.xml.rpc.handler, javax.xml.rpc.handler.soap, javax.xml.rpc.holders, javax.xml.rpc.server, javax.xml.rpc.soap, javax.xml.soap, javax.xml.stream, javax.xml.stream.events, javax.xml.stream.util, org.apache.geronimo.connector, org.apache.geronimo.connector.outbound, org.apache.geronimo.connector.outbound.connectionmanagerconfig, org.apache.geronimo.connector.outbound.connectiontracking, org.apache.geronimo.connector.outbound.security, org.apache.geronimo.connector.outbound.transactionlog, org.apache.geronimo.connector.work, org.apache.geronimo.connector.work.pool, org.apache.geronimo.mail.handlers, org.apache.geronimo.transaction, org.apache.geronimo.transaction.context, org.apache.geronimo.transaction.log, org.apache.geronimo.transaction.manager, org.codehaus.stax2, org.codehaus.stax2.evt, org.codehaus.stax2.io, org.codehaus.stax2.validation, org.omg.BiDirPolicy, org.omg.CONV_FRAME, org.omg.CORBA, org.omg.CORBA.CodeBasePackage, org.omg.CORBA.ContainedPackage, org.omg.CORBA.ContainerPackage, org.omg.CORBA.InterfaceDefPackage, org.omg.CORBA.TSIdentificationPackage, org.omg.CORBA.ValueDefPackage, org.omg.CSI, org.omg.CSIIOP, org.omg.CosLifeCycle, org.omg.CosNaming, org.omg.CosNaming.NamingContextExtPackage, org.omg.CosNaming.NamingContextPackage, org.omg.CosTSInteroperation, org.omg.CosTSPortability, org.omg.CosTransactions, org.omg.Dynamic, org.omg.DynamicAny, org.omg.DynamicAny.DynAnyFactoryPackage, org.omg.DynamicAny.DynAnyPackage, org.omg.GIOP, org.omg.GSSUP, org.omg.IIOP, org.omg.IOP, org.omg.IOP.CodecFactoryPackage, org.omg.IOP.CodecPackage, org.omg.IOP_N, org.omg.IOP_N.CodecFactoryPackage, org.omg.IOP_N.CodecPackage, org.omg.LifeCycleService, org.omg.Messaging, org.omg.NRService, org.omg.PortableInterceptor, org.omg.PortableInterceptor.ORBInitInfoPackage, org.omg.SECIOP, org.omg.SSLIOP, org.omg.Security, org.omg.SecurityAdmin, org.omg.SecurityLevel1, org.omg.SecurityLevel2, org.omg.SecurityReplaceable, org.omg.TimeBase I basically took the api and spi code trees and made bundles of them. This could be done by creating a bundle wrapper around the distribution jars, too. The external dependencies bundle is just a collection of all the stuff I needed to get the test running - it's really just for convenience. The bundle dependency on this bundle in the osgi-core needs to be turned into a series of package imports before this stuff is real. That's why none of these were attached to the JIRA - they're still not fully baked. :-) I hope to get back to this code shortly - getting a fully build-able example will be top on the priority list. Cheers, Joel -----Original Message----- From: Nicole Wengatz (JIRA) [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 15, 2006 7:03 AM To: Hawkins, Joel Subject: [jira] Commented: (TUSCANY-610) Initial OSGi support effort [ http://issues.apache.org/jira/browse/TUSCANY-610?page=comments#action_12 428097 ] Nicole Wengatz commented on TUSCANY-610: ---------------------------------------- Hi Joel, are you working with the Tuscany M1 release? After importing your projects in Eclipse, I have some problems to find the required classes. The OSGiBinding class f.e. extends Binding, but I find only an interface Binding (org.apache.tuscany.model.assembly.Binding). Could you please send me (or link me to) the required classes? Thanks Nicole > Initial OSGi support effort > --------------------------- > > Key: TUSCANY-610 > URL: http://issues.apache.org/jira/browse/TUSCANY-610 > Project: Tuscany > Issue Type: New Feature > Environment: Equinox implementation of OSGi > Reporter: Joel Hawkins > Attachments: ClassloaderHook.java, OSGI-SCA.zip > > > An initial implementation of an OSGi binding for exposing SCA services as OSGi services. > An initial implementation of an OSGi implementation for reusing OSGi services as SCA atomic components > An OSGi-aware bootstrap environment (which can probably be reduced a bit) > A repackaging of some of the SupplyChain example > There's one class derived from an EPL-copyrighted class - I left the EPL copyright intact. > The zip contains the samples, the OSGi binding, and a patch for the core. Most of the patch is the OSGi launcher code. I don't think it belongs in the core, but that's where I had it while developing. The only other bit in the patch is a change of two of the Defaultbootstrapper's fields from private to protected. > Also, some of the OSGi packaging for existing jars (spi, commands, etc) aren't part of the zip. Not sure how you want to deal with the repackaging issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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]
