Short background: Using "DynamicBlock" component that will call the component spec resolver to get a component. If the component is in a library, the component spec cannot find it. I initially thought the problem was with this little component, but this component merely calls the component resolver to get the component. This is where the failure is occuring.
I reviewed the ComponentSpecificationResolver class and it appears that when one passes a component name with the library prefix on it (i.e. "myapp:") , the resolver will get the CHILD namespace for that lib. This will work fine if you are running the resolver from your application namespace, but if you are running the resolver from your own custom library, the component will not resolve (unless you define the component library in your custom lib). Would it be a bad thing if the component is not found to check the application namespace for that library? One little check in the app namespace before calling your delegate resolver or throwing a component not found exception. Let me know if you are interested in this enhancement and how you would want me to supply it. Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
