Ron, The current Tuscany implementation is a bit of a mess, including the GLOBAL registry limitation, but the plan is to fix it in the near future.
Currently in Tuscany it works like this: - Each TypeHelper instance represents a unique scope which encapsulates its own local EPackage registry. - Any metadata registered via XSDHelper.define or TypeHelper.define will be in this local scope. - Local registries currently delegate to the EMF GLOBAL registry for types that are not found in the local registry. - Statically generated classes (which currently use the EMF generator patterns) are registered in the GLOBAL registry. - As in EMF, the GLOBAL registry, when running standalone (not in Eclipse) actually delegates to another classloader-specific delegate registry. - The net of all this is that there is a sort of a spider registry configuration currently, with the EMF global registry in the middle (with nothing actually in it). The plan, moving forward, is to make generated classes register their metadata in scope specific registries (the TypeHelper-local ones), instead of using the EMF GLOBAL registry. This is actually part of a bigger effort to change the generated class pattern to not have EMF dependencies. We're also planning to allow TypeHelper's (registries) to be configured (wired) any way you want to support nesting of scopes, etc. I hope this answers your question. Frank. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
