click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Schellink (JIRA)" <>
Subject [jira] Commented: (CLK-639) Click GAE does not support automapped pages in production modes
Date Wed, 14 Jul 2010 00:11:52 GMT


Bob Schellink commented on CLK-639:

GAE does not properly implement the Servlet specification -> ServletContext.getResourcePaths("/").

The Javadoc is quite explicit about the usage of "/":

There is an outstanding issue raised with GAE:

Even though GAE does not support getResourcePaths("/") it does return resources if the resourcePath
is not root. For example getResourcePaths("/pages") does return resources under the folder
For now we can add a workaround where templates and pages must be placed under the "/pages"
or "/page" folder. If Click determines it is running under GAE, it will scan these two folders
explicitly for page templates.

> Click GAE does not support automapped pages in production modes
> ---------------------------------------------------------------
>                 Key: CLK-639
>                 URL:
>             Project: Click
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.1.0
>            Reporter: Bob Schellink
>            Assignee: Bob Schellink
>             Fix For: 2.3.0-M1
> Google App Engine does not seem to support looking up directories from the servlet context
path. This in turn means Click cannot find the templates to build up a cached map of templates
to Page classes.
> This problem only affects production and profile modes, not development modes, since
development modes access the templates files directly (which GAE supports) if it fails to
find it in the cached map.
> The workaround for now is to manually map Pages to templates in the click.xml file:
> <pages package="">
>       <page path="home.htm" classname="HomePage" ></page>
>       <page path="/ajax/form-demo.htm" classname="ajax.FormDemo"></page>
>       ...
>   </pages>

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

View raw message