Hi Jean,
*
*
*IIRC contributions don't have a namespace.*
I didnt try out this yet, but I figured out that sca contributions
have an option to export namespaces :
export namespace=http://nuvemstandalone; /
*I'm not sure how to reuse feature composites, as you'll need to configure
their components for specific apps, hosts, ip addresses, user ids etc.*
I was actually looking into these options to see if we can avoid nuvem
client's to directly wire every components by referring
to implementation classes directly, instead thought it will be good
to just allow the client to refer to just few components with
their component names.
I am trying to find out if there is a way in tuscany which will allow
nuvem clients to define few global properties before importing
the contributions? if yes then I think we can resolve those values
before injecting the properties into the nuvem components.
Any Idea if tuscany has such features in place?
Thanks,
John
On Sun, Jun 5, 2011 at 8:29 AM, Jean-Sebastien Delfino
jsdelf...@gmail.comwrote:
Hi John,
Your proposal looks good to me, with a few comments:
IIRC contributions don't have a namespace.
I'm not sure how to reuse feature composites, as you'll need to configure
their components for specific apps, hosts, ip addresses, user ids etc.
They're useful though, as examples, templates or palettes that the
developer can review before creating his own. But then their namespaces
don't matter.
Thoughts?
--
Jean-Sebastien
Sent from my iPhone
On May 31, 2011, at 3:31 PM, john pradeep yehohan...@gmail.com wrote:
Hi,
I am trying to organize the composite and contribution files for all
modules
and thought of the below approach.
1. Each SCA contribution corresponding to a cloud platform will have a
specific namespace
*Example:* contribution xmlns=
http://docs.oasis-open.org/ns/opencsa/sca/200912;
xmlns:tuscany=http://tuscany.apache.org/xmlns/sca/1.1;
xmlns:xmpp=*http://nuvemstandalone*;
2. we will have a composite for each feature with the same namespace as
it
is defined in its sca contribution but the name of the composite itself
will
indicate the feature
* Example:*composite xmlns=
http://docs.oasis-open.org/ns/opencsa/sca/200912;
xmlns:tuscany=http://tuscany.apache.org/xmlns/sca/1.1;
*targetNamespace=http://nuvemstandalone; name=xmpp*
4. The component/service names within the composites will be Identified
with
the same names across all SCA contributions to keep it consistent.
5. Since the component names are maintained same across all platforms,
the
client will always refer to the same component/service name but will
import
the right namespace to choose the contribution (google, standalone etc)
I haven't tried to import a composite just by its name space in tuscany
yet,
but i assume it should be possible?
Please let me know your thoughts.
Regards,
John
