Re: Issues with namespace indicators

Chris, we seem to have 3 places where prefixes are generated, and not using the same algorithm. 1) BaseSDOXSDEcoreBuilder.getEPackage() 2) SDOXSDEcoreBuilder.lookupPrefix 3) EMFs BasicExtendedMetadata.computePrefix() The difference in behaviour here is explained by the fact that when the two

Simple use case problem

Hi, I'm new to SCA and I'm trying to do a little example. My very simple use case : A ProviderComponent implemented in Java in a Provider composite. All this in a jar file. Alone works fine. A ConsumerComponent implemented in Java in a Consumer composite in another jar file. This component

Re: Simple use case problem

Hi Patrick and welcome So it sounds like you have two composites in separate Jar files. Are these composites both being contributed to a Tuscany runtime in the same VM? I believe this should work but I've not tried it. I can have a look for you if you give me a little more detail. If you are

RE: Simple use case problem

Hi Simon, It's in the same VM. I have sent the full code (a 29K ZIP file) to your e-mail. Thanks Patrick -Message d'origine- De : Simon Laws [mailto:[EMAIL PROTECTED] Envoyé : mercredi 30 mai 2007 15:06 À : tuscany-user@ws.apache.org Objet : Re: Simple use case problem Hi Patrick

Re: Simple use case problem

Hi Patrick What is going on here is that the consumer module is not loading the provider composite. I can make this work by doing the following... 1 - Make the provider composite available to the consumer runtime copy the Provider.composite to consumer/src/main/resource 2 - Make the

[SDO Java] behaviour of generator with multiple namespaces

I'm applying a patch attached to [1] to the java generator which allows it to generate classes for multiple namespaces in a single run. The current fix is adopting the safe policy of not changing the default behaviour, which only exports classes for a single namespace. So as it stands, one new