From 6d6958301ebad805b90a3bf8082a92f7814d2be9 Mon Sep 17 00:00:00 2001 From: Constantine Vetoshev Date: Tue, 9 Nov 2010 17:48:49 -0500 Subject: [PATCH] Documented a couple of pain points. --- README.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/README.md b/README.md index d996817..b3143c3 100644 --- a/README.md +++ b/README.md @@ -89,6 +89,10 @@ resulting project, but do take a careful look at it. In particular, you should avoid checking in `resources/WEB-INF/lib/` or `resources/WEB-INF/classes/`: let Leiningen take care of managing those directories. +NB: When editing the Leiningen `project.clj` file, do not point `:compile-path` +or `:library-path` to `resources/WEB-INF/classes/` and +`resources/WEB-INF/lib/`. This will interfere with deployment. + ### Development process @@ -321,6 +325,19 @@ A few simple examples: ## Limitations +### Using App Engine API calls + +Most App Engine services do not work when invoked without an initialized App +Engine context. For the time being, this context only exists (1) inside an +application's Ring handlers, and (2) in the automatic testing environment +provided by `appengine-magic.testing`. This means that you cannot directly +invoke most App Engine API functions from the REPL. + +This limitation will be addressed in the future. (In the meanwhile, avoid tight +coupling between your application code and App Engine services.) + + + ### Incomplete features When using the interactive REPL environment, some App Engine services are more