tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kalle Korhonen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-2067) Error loading classes with Tomcat 7 parallel deployment
Date Sat, 09 Feb 2013 19:43:12 GMT

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

Kalle Korhonen commented on TAP5-2067:

The reason I haven't attempted fixing it is that I don't see the issue in my Tomcat 7 parallel
deployment environment. I'm running Tapestry 5.3.6 with Tomcat 7.0.27 on CentOS release 5.8
(Final) x86_64. I'd be interested in knowing why it works on some environment and doesn't
in others. What are the details of your environment?
> 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

View raw message