Just chance. I think it's very chancy to try to override T5's built in components this way. You should put them in a component library. I'll be working on docs about how to do that shortly :-)
On Tue, Oct 21, 2008 at 2:36 PM, Tom Zurkan <[EMAIL PROTECTED]> wrote: > How can I guarantee that my LibraryMapping is going to override the Tapestry > Module LibraryMapping since the contribution's ordering is random? > I am contributing a componentClassResolver LibraryMapping with the path > prefix of "core" so that my library will be searched first for a component. > This worked in Tapestry 5.11 but doesn't in 5.16. Was it just by chance > that it worked before? > > Any help would be greatly appreciated. > Thanks, > > Tom Zurkan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
