I have to say +0 for now... I can't understand why the getContext() needs to take a parameter.
As I see it, the ComponentMetaData contains information about a component instance, or all the data required to create a component. I cannot understand why it needs a factory-type method. I thought the ResourceProvider was supposed to handle that. I am +1 for a public Context getContext() method, though, in line with getConfiguration() etc... Stephen, could you be more specific why the method needs to be a factory? In particular, is it related to a standard factory that will initialize the ComponentMetaData from an XML file and that you thus need to mix an application specified context with the context data from the XML? In that case, I'd vote for passing in the parent context into the method creating the ComponentMetaData from XML. /LS -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
