Oh SNAP! I just figured it out. I had so many components that I decided to move my border-related components from
..../components to ..../components/layout But I also had a component that was named layout. So the error stemmed from Tapestry trying to resolve ..../components/layout/layout.class (and also layout.html) I had not been referencing the component named layout in any of my code or templates, so I guess Tapestry maps everything out ahead of time. Sorry for the flood of emails. Hope this helps someone. It seems there are other recent emails regarding the Pidgeonhole nature of Tapestrys shortened references. Daniel Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
