Never did get any answer on this. Having the class below in the rhino
container works as it uses the AbstractCompositeContext package name, but it
seesm a bit hacky:

package org.apache.tuscany.core.context.impl;

public class ComponentNamesAccessor {

   public static Set<String> getComponentNames(ModuleContext moduleContext)
{
       if (moduleContext instanceof AbstractCompositeContext) {
           Map<String, ScopeContext> x = ((AbstractCompositeContext)
moduleContext).scopeIndex;
           return x.keySet();
       }
       return null;
   }

}

  ...ant


On 5/24/06, ant elder <[EMAIL PROTECTED]> wrote:

Jim, this would be unmanaged code, not in a component, so it doesn't look
like there is any API for this. The idea of TUSCANY-417 is an interactive
JavaScript shell  along the lines of what Jeremy described as a "first-class
client environment for JavaScript".

   ...ant


On 5/24/06, Jim Marino <[EMAIL PROTECTED]> wrote:
>
> Can you explain why you need the list of components? For managed code
> (i.e. in a component) the spec defines a way to get the metadata
> associated with a module.
>
> Jim
>
> On May 24, 2006, at 1:30 AM, ant elder wrote:
>
> > I've a J2SE client that needs to get a list of all the components
> > defined in
> > the current module, is that possible? There used to be the getMetaData
> > method but thats been removed now.  If there is no easy way right
> > now could
> > i add something?
> >
> >   ...ant
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to