You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Nicolas Bouillon (JIRA)" <ji...@apache.org> on 2014/12/05 11:22:12 UTC

[jira] [Commented] (TAP5-2424) Application folder doesn't support "sub folders" (slash in path)

    [ https://issues.apache.org/jira/browse/TAP5-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235335#comment-14235335 ] 

Nicolas Bouillon commented on TAP5-2424:
----------------------------------------

The patch can be also applied on the master branch without conflics.

> Application folder doesn't support "sub folders" (slash in path)
> ----------------------------------------------------------------
>
>                 Key: TAP5-2424
>                 URL: https://issues.apache.org/jira/browse/TAP5-2424
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3.8
>            Reporter: Nicolas Bouillon
>              Labels: easyfix, newbie, patch
>         Attachments: 0001-Trim-the-applicationFolderPrefix-for-Event-Request-on-tap-5.3.8.patch
>
>
> I've set my tapstry servlet filter as :
> 	<filter-mapping>
> 		<filter-name>app</filter-name>
> 		<url-pattern>/path1/path2/*</url-pattern>
> 	</filter-mapping>
> And in the AppModule 
>         configuration.add(SymbolConstants.APPLICATION_FOLDER, "path1/path2");
> It works for Page Requests, but for Event requests it doesn't work.
> The probleme is here org.apache.tapestry5.internal.services.ComponentEventLinkEncoderImpl#decodeComponentEventRequest
> The method used to remotve the application folder is not the same as the one used in org.apache.tapestry5.internal.services.ComponentEventLinkEncoderImpl#decodePageRenderRequest
> In decodeComponentEventRequest, the request path comparison is done between the applicationFolderPrefix and the substring until the first "/". In decodePageRenderRequest, the comparison is done otherwise.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)