Contribute to the tapestry.ComponentClassResolver service's configuration.
The contribution for the core library is: public static void contributeComponentClassResolver(Configuration<LibraryMapping> configuration) { configuration.add(new LibraryMapping("core", "org.apache.tapestry.corelib")); } This maps the virtual folder "core" to the given package (with pages, components, etc. packages beneath). You can define a new virtual folder this way, or extend an existing one. Why can't the components be in the standard location? On 2/22/07, Dennis Kempin <[EMAIL PROTECTED]> wrote:
Hello, I want to make a bunch of components available to my application, but these are not inside the [root].components package. How can i add additonal packages to the search path for components? thanks, Dennis --------------------------------------------------------------------- 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]