click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Schellink (JIRA)" <>
Subject [jira] Commented: (CLK-560) Google App Engine support
Date Thu, 18 Jun 2009 06:22:07 GMT


Bob Schellink commented on CLK-560:

Yes, we should try and align with the spec and rename our auto-deployment folder from META-INF/web
to META-INF/resources. In ConfigService we can check the servlet major version whether resources
should be deployed or left to the container to serve. See #4 here:

An interim solution for 2.1.0 final could be as follows: move all static resources under 'META-INF/web'.
IDE's such as Eclipse, Netbeans and Intellij makes it easy to view the content of jars and
provides an easy way to copy out all resources from the jar to the web application root folder.
Currently its a bit of a pain as one needs to deploy the application to say, Tomcat, to find
all resources deployed under the 'click' folder.

> Google App Engine support
> -------------------------
>                 Key: CLK-560
>                 URL:
>             Project: Click
>          Issue Type: New Feature
>            Reporter: Bob Schellink
>            Assignee: Bob Schellink
>             Fix For: 2.1.0
> Google App Engine (GAE) provides free Java hosting and an ideal solution for startups
or student wanting to host their applications.
> This JIRA is to provide out-of-the-box support for Click applications.
> Here are the issues enountered thus far:
> 1. - OGNL SecurityManager has to be set to null. This can be achived via a new ServletContextListener
in the extras package.
> 2. - GAE doesn't support writing to the file system so Click cannot deploy its resources
on the fly. Instead users will have to package resources within the war itself. Servlet 3.0
may come to the rescue as it allows serving static resources from the META-INF/resources folder.
Very similar to Click's auto deployment from META-INF/web, except Servlet 3.0 serves resources
directly from this location without having to deploy them.
> 3. - FileUpload doesn't work out of the box as it writes to the file system. Should look
at a Memory FileItem or somesuch solution.
> 4. - GAE's appengine-web.xml must be setup to exclude serving *.htm resources (if PerformanceFilter
is used png, gif, css and js files should also be excluded)

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

View raw message