tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (TAP5-2067) Error loading classes with Tomcat 7 parallel deployment
Date Sun, 10 Feb 2013 10:03:12 GMT

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

Pavel edited comment on TAP5-2067 at 2/10/13 10:01 AM:
-------------------------------------------------------

I have Debian 5.0 (x32) with Tomcat 7.0.33. Tapestry 5.3.6, application is deployed to root
context as ROOT##version folder
                
      was (Author: rodimusprime):
    I have Debian 5.0 (x32) with Tomcat 7.0.33
                  
> Error loading classes with Tomcat 7 parallel deployment
> -------------------------------------------------------
>
>                 Key: TAP5-2067
>                 URL: https://issues.apache.org/jira/browse/TAP5-2067
>             Project: Tapestry 5
>          Issue Type: Improvement
>    Affects Versions: 5.3.6
>            Reporter: Pavel
>
> When trying to deploy tapestry app using tomcat 7 parallel deployment (which demands
to name app dir like myapp##version) there is an FileNotFoundException when loading AppModule
file. The reason is, that path to app dir gets urlencoded whith those ## looking like %23%23.

> In PlasticInternalUtils there is already code dealing with urlencoded spaces
> private static InputStream getStreamForPath(....
> if (url.getProtocol().equals("file"))
>         {
>             String urlPath = url.getPath();
>             String decoded = urlPath.replaceAll("%20", " ");
>             return new FileInputStream(new File(decoded));
>         }
> could it be extended (or better generalised) to handle all urlencoded problems? I think
it is really easy to fix and is very annoying not being able to use parallel deployment. I
could even provide a patch if you think this issue is worth fixing. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message