I'd say that the scenario is valid, but as mentioned in [1], we were not handling cycles very well in our import/export model resolvers. Are you experiencing a specific issue that I could try helping ?
[1] http://www.mail-archive.com/[email protected]/msg28147.html On Mon, Apr 14, 2008 at 8:14 PM, Wang Feng <[EMAIL PROTECTED]> wrote: > Hi all > I have a scenario like this.There are two contributions and each one > contribution > contains one composite which has the same namespace. The namespace has been > imported and exported on every contribution. > I am not sure this scenario is right or wrong,can anybody give me an advice? > > Contribution metadata like below: > Contribution A > <contribution xmlns="http://www.osoa.org/xmlns/sca/1.0"; > targetNamespace="http://hello"; > xmlns:hello="http://hello";> > <deployable composite="hello:helloworldws"/> > <import namespace="http://hello"/> > <export namespace="http://hello"/> > </contribution> > > Contribution B > <contribution xmlns="http://www.osoa.org/xmlns/sca/1.0"; > targetNamespace="http://hello"; > xmlns:hello="http://hello";> > <deployable composite="hello:helloworld"/> > <import namespace="http://hello"/> > <export namespace="http://hello"/> > </contribution> > > -------------- > Wang Feng > 2008-04-15 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
