tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ezra Epstein (JIRA)" <...@tapestry.apache.org>
Subject [jira] Commented: (TAPESTRY-1888) Support multiple instances of org.apache.tapestry.TapestryFilter per web-app.
Date Wed, 07 Nov 2007 18:10:50 GMT

    [ https://issues.apache.org/jira/browse/TAPESTRY-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540823

Ezra Epstein commented on TAPESTRY-1888:

How so.  Is there a software limitation - that is, is Tapestry written with the assumption
of a single instance of the filter per JVM?  If not then why restrict it.  I don't think skilled
developers will shoot themselves in the foot - just the opposite it frees them to choose how
to build apps.  And for novices the tutorial can continue to show the one Filter per web-app

I'm reminded of why people thought Objective-C was bad: it's lack of strong typing could lead
to ambiguity.  Yes, and power. 

> Support multiple instances of org.apache.tapestry.TapestryFilter per web-app.
> -----------------------------------------------------------------------------
>                 Key: TAPESTRY-1888
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1888
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.0.6
>         Environment: All.
>            Reporter: Ezra Epstein
> Currently one configures org.apache.tapestry.TapestryFilter via a context-param.  It
would be really handy to be able to configure via an init-param.  If the TapestryFilter is
coded so that there may be multiple instances for a given app then it would be easier to roll
up sub-sites into a single site.  Thus allowing multiple, different packages to be specified
as the tapestry.app-pacakge.  E.g.,
> 	<filter>
> 		<filter-name>tapestry1</filter-name>
> 		<filter-class>org.apache.tapestry.TapestryFilter</filter-class>
> 		<init-param>
> 			<param-name>app-package</param-name>
> 			<param-value>com.foo.bar.web</param-value>
> 		</init-param>
> 	</filter>
> 	<filter>
> 		<filter-name>tapestry2</filter-name>
> 		<filter-class>org.apache.tapestry.TapestryFilter</filter-class>
> 		<init-param>
> 			<param-name>app-package</param-name>
> 			<param-value>com.foo.bar.subsite</param-value>
> 		</init-param>
> 	</filter>
> It also would keep the web.xml file a bit tidier. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

View raw message