Hi, The version of DynamicBlock in the jar downloadable from within Eclipse via Tapestry Palette consults it's parent namespace first then it's own. This seemed appropriate since it's a library component used to render other components with names unknwown until runtime.
Perhaps namespaces could be made more like java packages? Then the namespace is a global hierarchical namespace with no chance of collision aand no need to worry about relative namespace paths. Mike The assumption is that the On Thursday, June 16, 2005, at 10:07AM, phillip rhodes <[EMAIL PROTECTED]> wrote: >I am using a cool little component someone wrote >called DynamicBlock. > >Unfortunately, I just figured out that DynamicBlock >appears to be limited to finding and rendering >components within the same library that it is declared >in. > >It subclasses the BaseComponent and uses the >getComponents() method to search for the named block >that you want to render. My block is defined in >another library, so the component is never found. > > >Has anyone ever tried to located from one library a >reference to a component within another library? >Is there a way to obtain a list of all components in a >particular namespace? > > > >Thanks. > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
