On Fri, Mar 7, 2008 at 7:33 PM, Rajini Sivaram <[EMAIL PROTECTED]> wrote:
> itest/osgi-tuscany contains tests for an OSGi-based Tuscany runtime. I > haven't included the tests in itests/pom.xml because they need to create > bundles corresponding to Tuscany, and hence require around 100 megabytes. > Since we currently dont have other tests for a multi-classloader Tuscany > environment, and because it is very difficult to ensure that changes to > Tuscany dont add more problems for an OSGi-based Tuscany, I would like to > add itest/osgi-tuscany to the main build if there are no objections. > > There are still many outstanding issues with running Tuscany under OSGi, > but > the test directory contains a harness to enable Tuscany samples to be run > using an OSGi-based Tuscany runtime, and hence provides test cases for all > the known outstanding issues (the broken tests are currently commented > out, > but can be turned on as each problem is fixed). > > Thoughts? Objections? > > Thank you... > > Regards, > > Rajini > Could you explain a bit about why the bundles are split up this way (runtime/extensions/3rdparty), not saying i think its wrong and I think you've posted about this in the past, i'm just trying to understand properly how it all hangs together. For example, would be possible to have something like a tuscany-base module that includes the runtime and its dependencies as one bundle (similar to as described in [1]), and then have other bundles for extensions such as a ws bundle that includes the tuscany axis2 extension and all its dependencies? ...ant [1] http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200803.mbox/[EMAIL PROTECTED]
