Hi Are you working with the 1.x code base or the 2.x code base?
More work has been done on the 2.x codebase to make Tuscany fit into the OSGi world better, for example, the manifests are right and all of the third party dependencies are treated properly as bundles. If you build the 2.x code base (or take one of the milestone distributions) you'll see all of the bundles in the modules directory (at the top level in the binary distro or in distribution/all/target/modules if you build it). Also, as we are bringing up 2.x incrementally there are less Tuscany bundles to deal with at the moment. This may be a bad thing it you need the full range of features that 1.x offers but is a good thing if you just want to experiment with OBR installation. We don't have a "main" bundle as such. The Tuscany runtime is designed around a core into which extensions fit. The core doesn't depend on the extensions on purpose, so you have to include whichever extensions you required when you configure your runtime environment. A good way to get a view of how the modules are grouped in 2.x is to look in the "features" directory. This holds some maven modules that group the Tuscany modules into api, core, ejava etc. groups. Regards Simon
