You mentioned "provided dynamically"? You can't just instantiate components, only Tapestry can do that, once it has transformed the class. What you can do is place the components, in the template, inside a <t:block> element.
On Jan 14, 2008 7:42 AM, Bret Gregory <[EMAIL PROTECTED]> wrote: > I am running into a problem with a custom component that I am attempting > to write. The component is a dropdown menu. Inside the menu there are > menu items which are components that are provided dynamically. These > components are then looped over and each menu item component is to be > rendered based on its type. However, I am getting a Null Pointer when > attempting to render the individual items. It looks like the > transformation of the components adds a render() method to the component > that defers to the ComponentResources class's queueRender method. But > for my Menu Items the resources is null and I am not sure why that is > the case. > > The MenuItem component class extends an Abstract class from the > root.base package. This class also looked to be getting transformed by > tapestry which I didn't expect since it wasn't in the pages or > components package. The concrete MenuItem component lives in the > root.components.nav package. > > Any ideas on why the ComponentResources are not available in my Menu > Item components? > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
