You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2009/06/10 14:48:07 UTC

[jira] Created: (TAP5-743) It is too much work to hide all T5 pages inside a virtual folder, for use in mixed-implementation deployments

It is too much work to hide all T5 pages inside a virtual folder, for use in mixed-implementation deployments
-------------------------------------------------------------------------------------------------------------

                 Key: TAP5-743
                 URL: https://issues.apache.org/jira/browse/TAP5-743
             Project: Tapestry 5
          Issue Type: Improvement
          Components: tapestry-core
    Affects Versions: 5.1.0.5
            Reporter: Howard M. Lewis Ship


In a mixed-implementation deployment (mixing Tapestry 5 with Tapestry 4 or some other framework), it would be nice if the T5 apps could be "hidden" in a virtual /t5 folder.

This is doable, but awkward and ugly, today.

Ideally, this would be a matter of changing the web.xml mapping to:

<url-filter>/t5/*</url-filter>

and making some form of configuration change, i.e.,

configuration.add(ConfigurationConstants.TAPESTRY_APP_FOLDER, "t5");

This would affect link generation, prefixing urls with "t5/" (including the virtual /assets folder, which would be /t5/assets). Since the /t5 portion is part of the URL mapping, it would not be part of the request pathInfo, so existing dispatch code would not need to change.  

Of course, Websphere has some bugs in this area that might cause some grief.

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

[jira] Commented: (TAP5-743) It is too much work to hide all T5 pages inside a virtual folder, for use in mixed-implementation deployments

Posted by "Inge Solvoll (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TAP5-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850558#action_12850558 ] 

Inge Solvoll commented on TAP5-743:
-----------------------------------

I would be extremely interested in finding out if this can be done with url rewriting...

> It is too much work to hide all T5 pages inside a virtual folder, for use in mixed-implementation deployments
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-743
>                 URL: https://issues.apache.org/jira/browse/TAP5-743
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Howard M. Lewis Ship
>
> In a mixed-implementation deployment (mixing Tapestry 5 with Tapestry 4 or some other framework), it would be nice if the T5 apps could be "hidden" in a virtual /t5 folder.
> This is doable, but awkward and ugly, today.
> Ideally, this would be a matter of changing the web.xml mapping to:
> <url-filter>/t5/*</url-filter>
> and making some form of configuration change, i.e.,
> configuration.add(ConfigurationConstants.TAPESTRY_APP_FOLDER, "t5");
> This would affect link generation, prefixing urls with "t5/" (including the virtual /assets folder, which would be /t5/assets). Since the /t5 portion is part of the URL mapping, it would not be part of the request pathInfo, so existing dispatch code would not need to change.  
> Of course, Websphere has some bugs in this area that might cause some grief.

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

[jira] Commented: (TAP5-743) It is too much work to hide all T5 pages inside a virtual folder, for use in mixed-implementation deployments

Posted by "Thiago H. de Paula Figueiredo (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TAP5-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718057#action_12718057 ] 

Thiago H. de Paula Figueiredo commented on TAP5-743:
----------------------------------------------------

Can't this be implemented with <url-filter>/t5/*</url-filter> in web.xml and a URL rewriting rule (inbound and outbound)? Or the URL rewriting would not happen before the dispatchers execution?

> It is too much work to hide all T5 pages inside a virtual folder, for use in mixed-implementation deployments
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-743
>                 URL: https://issues.apache.org/jira/browse/TAP5-743
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Howard M. Lewis Ship
>
> In a mixed-implementation deployment (mixing Tapestry 5 with Tapestry 4 or some other framework), it would be nice if the T5 apps could be "hidden" in a virtual /t5 folder.
> This is doable, but awkward and ugly, today.
> Ideally, this would be a matter of changing the web.xml mapping to:
> <url-filter>/t5/*</url-filter>
> and making some form of configuration change, i.e.,
> configuration.add(ConfigurationConstants.TAPESTRY_APP_FOLDER, "t5");
> This would affect link generation, prefixing urls with "t5/" (including the virtual /assets folder, which would be /t5/assets). Since the /t5 portion is part of the URL mapping, it would not be part of the request pathInfo, so existing dispatch code would not need to change.  
> Of course, Websphere has some bugs in this area that might cause some grief.

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

[jira] Commented: (TAP5-743) It is too much work to hide all T5 pages inside a virtual folder, for use in mixed-implementation deployments

Posted by "Inge Solvoll (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TAP5-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850558#action_12850558 ] 

Inge Solvoll commented on TAP5-743:
-----------------------------------

I would be extremely interested in finding out if this can be done with url rewriting...

> It is too much work to hide all T5 pages inside a virtual folder, for use in mixed-implementation deployments
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-743
>                 URL: https://issues.apache.org/jira/browse/TAP5-743
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Howard M. Lewis Ship
>
> In a mixed-implementation deployment (mixing Tapestry 5 with Tapestry 4 or some other framework), it would be nice if the T5 apps could be "hidden" in a virtual /t5 folder.
> This is doable, but awkward and ugly, today.
> Ideally, this would be a matter of changing the web.xml mapping to:
> <url-filter>/t5/*</url-filter>
> and making some form of configuration change, i.e.,
> configuration.add(ConfigurationConstants.TAPESTRY_APP_FOLDER, "t5");
> This would affect link generation, prefixing urls with "t5/" (including the virtual /assets folder, which would be /t5/assets). Since the /t5 portion is part of the URL mapping, it would not be part of the request pathInfo, so existing dispatch code would not need to change.  
> Of course, Websphere has some bugs in this area that might cause some grief.

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

[jira] Commented: (TAP5-743) It is too much work to hide all T5 pages inside a virtual folder, for use in mixed-implementation deployments

Posted by "Thiago H. de Paula Figueiredo (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TAP5-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718057#action_12718057 ] 

Thiago H. de Paula Figueiredo commented on TAP5-743:
----------------------------------------------------

Can't this be implemented with <url-filter>/t5/*</url-filter> in web.xml and a URL rewriting rule (inbound and outbound)? Or the URL rewriting would not happen before the dispatchers execution?

> It is too much work to hide all T5 pages inside a virtual folder, for use in mixed-implementation deployments
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-743
>                 URL: https://issues.apache.org/jira/browse/TAP5-743
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Howard M. Lewis Ship
>
> In a mixed-implementation deployment (mixing Tapestry 5 with Tapestry 4 or some other framework), it would be nice if the T5 apps could be "hidden" in a virtual /t5 folder.
> This is doable, but awkward and ugly, today.
> Ideally, this would be a matter of changing the web.xml mapping to:
> <url-filter>/t5/*</url-filter>
> and making some form of configuration change, i.e.,
> configuration.add(ConfigurationConstants.TAPESTRY_APP_FOLDER, "t5");
> This would affect link generation, prefixing urls with "t5/" (including the virtual /assets folder, which would be /t5/assets). Since the /t5 portion is part of the URL mapping, it would not be part of the request pathInfo, so existing dispatch code would not need to change.  
> Of course, Websphere has some bugs in this area that might cause some grief.

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