That would take some doing, it's something I thought of and dismissed.
T4 supports it, and that's one of the reasons it's so complex to
discuss which files are stored where. To me, this would be a
low-priority enhancement.
On 6/7/07, Bruce Petro <[EMAIL PROTECTED]> wrote:
I was thinking for development purposes it might be desirable to have
multiple contexts.
But I don't see how to tie a context-param (which determines which
classes handle the requests) to a filter definition (which specifies a
url pattern to handle)
I'm making a wild guess that in the sample "app" setup, perhaps it's the
app in the "tapestry.app-package" perhaps matches the app in the
filter-name.
Is that how they are paired up? If so, then please confirm this is how
you would do this. If this isn't true - can someone specify how it's
done?
Thanks.
tapestry.app1-package
com.myapplication.catalog
app1
org.apache.tapestry.TapestryFilter
app1
/catalog/*
tapestry.app2-package
com.myapplication.ordering
app2
org.apache.tapestry.TapestryFilter
app2
/order/*
--
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]
