You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Ezra Epstein (JIRA)" <de...@tapestry.apache.org> on 2007/11/07 00:44:50 UTC
[jira] Created: (TAPESTRY-1888) Support multiple instances of
org.apache.tapestry.TapestryFilter per web-app.
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
[jira] Commented: (TAPESTRY-1888) Support multiple instances of
org.apache.tapestry.TapestryFilter per web-app.
Posted by "Ezra Epstein (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555672#action_12555672 ]
Ezra Epstein commented on TAPESTRY-1888:
----------------------------------------
How about instead, just support init-param/s in addition to (eventually instead of?) the context-param/s so that folks web.xml files are tidier.
> 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
[jira] Commented: (TAPESTRY-1888) Support multiple instances of
org.apache.tapestry.TapestryFilter per web-app.
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555657#action_12555657 ]
Howard M. Lewis Ship commented on TAPESTRY-1888:
------------------------------------------------
The construction of T5 is such that two applications sharing (as above) will each have their own Registry, which will make sharing of caches and such very difficult. I'm really, really, really hesitant to head down this path.
> 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
[jira] Commented: (TAPESTRY-1888) Support multiple instances of
org.apache.tapestry.TapestryFilter per web-app.
Posted by "Ezra Epstein (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540909 ]
Ezra Epstein commented on TAPESTRY-1888:
----------------------------------------
I think you guys may both be right. I also think this is partly a case of a customer proposing a solution rather than stating a feature request. Let me try again.
I really just would like two things:
1. To be able to specify multiple packages for the location of Tapestry page/component classes.
2. To be able to specify these as init-param element/s (rather than as context-param element/s). That way my config is nice and tidy and grouped.
So, with that proper restatement of the feature request, do either of those make sense and/or sound like good ideas in the context of Tap 5?
> 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
[jira] Closed: (TAPESTRY-1888) Support multiple instances of
org.apache.tapestry.TapestryFilter per web-app.
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-1888.
------------------------------------------
Resolution: Won't Fix
Assignee: Howard M. Lewis Ship
Tapestry 5 is explicitly structured such that one WAR is a single application. Since you can split your application across folders easily (more easily than T4) there's no reason to support multiple applications, especially now that per-folder Index pages have been added.
> 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
> Assignee: Howard M. Lewis Ship
>
> 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
[jira] Commented: (TAPESTRY-1888) Support multiple instances of
org.apache.tapestry.TapestryFilter per web-app.
Posted by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540826 ]
Jesse Kuhnert commented on TAPESTRY-1888:
-----------------------------------------
I don't know if I like the idea of multiple applications being rolled up in to one either, but just wanted to say that I have seen other people do similar things with "rolling up sub-sites". The only other person I've seen do it said it was done to increase throughput / reduce memory consumption of multiple web applications all hitting the same database because they could then use the same hibernate cache / etc....
There are probably better ways to solve the same problem, just sharing information I've seen before. I definitely don't like the idea either but who knows...
> 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
[jira] Commented: (TAPESTRY-1888) Support multiple instances of
org.apache.tapestry.TapestryFilter per web-app.
Posted by "Ezra Epstein (JIRA)" <de...@tapestry.apache.org>.
[ 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 approach.
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
[jira] Commented: (TAPESTRY-1888) Support multiple instances of
org.apache.tapestry.TapestryFilter per web-app.
Posted by "Brent Thomas (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541055 ]
Brent Thomas commented on TAPESTRY-1888:
----------------------------------------
I cannot speak to the ambiguity issue that Howard mentions, but I agree that using an init-param instead of a context-param makes more sense. The init-param ties the property to the TapestryFilter where it makes more sense rather than to the WAR as a whole.
> 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
[jira] Commented: (TAPESTRY-1888) Support multiple instances of
org.apache.tapestry.TapestryFilter per web-app.
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540818 ]
Howard M. Lewis Ship commented on TAPESTRY-1888:
------------------------------------------------
I'm not sure I want to support multiple Tapestry applications in a single WAR. It leads to a lot of ambiguity.
> 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