I haven't documented how to create Tapestry component libraries yet.
Been kind of dragged all over the place.
In your AppModule class, add something like:
public static void
contributeComponentClassResolver(Configuration<LibraryMapping>
configuration)
{
configuration.add(new LibraryMapping("common", "com.reged"));
}
You can then reference your component as:
<span t:type="common/foo"> ... </span>
or
<t:common.foo> ... </t:common.foo>
for component com.reged.components.Foo.
On Nov 9, 2007 1:45 PM, Brandon Staton <[EMAIL PROTECTED]> wrote:
>
>
>
> Hey,
>
> I'm on the process of upgrading our current applications from Tapestry 3 to
> Tapestry 5. I'd like to put common components into a package like
> com.reged.components (subpackages as needed) and app-specific tapestry
> classes into packages like com.reged.sampleapp.pages for example. Based on
> having to make this setting in web.xml: tapestry.app-package to
> com.reged.sampleapp, Tapestry won't find any of the common components. Am I
> missing something?
>
> Let me know when you get a chance,
>
> Brandon S Staton
>
> Technical Projects Manager
>
> RegEd
> 2100 Gateway Centre Blvd.
>
> Suite 200
>
> Morrisville, NC 27560
>
> 919-653-5259 (phone)
>
> 919-653-6559 (fax)
>
> http://www.reged.com/
>
>
--
Howard M. Lewis Ship
Partner and Senior Architect at Feature50
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
