Generally speaking, stuff in the internal module is private and not directly extensible.
There are interfaces that are likely to change quite a bit and I'm trying to keep a lid on them. They may eventually move into the public side, or there may be extension points added that are public, even if the service is private/internal. On 3/9/07, Dan Adams <[EMAIL PROTECTED]> wrote:
I'm looking at the t5 sources and trying to see if it's possible to configure a different implementation of ComponentClassResolver than the default and it doesn't look like it. Is this correct? I'm currently planning a library/framework built on t5 and one of the things that it *might* need to be able to do is intercept a request for a page/component/mixin with a mapping that is different than is currently possible. -- Dan Adams Senior Software Engineer Interactive Factory 617.235.5857 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
