Comments on Fatvat: Clojure on the Google App Engine

grinnbearit - thanks for the feedback. Leiningen ...

2010-01-31T00:08:06.848-08:00

grinnbearit - thanks for the feedback.

Leiningen looks really good - building with Ant isn't fun. I haven't had a chance to use Leiningen for anything yet - do you have an example of it'd look for this project compared to Ant?

Very helpful, thanks. Especially since the latest ...

2010-01-30T20:38:51.245-08:00

Very helpful, thanks.
Especially since the latest compojure throws up several errors if I use it with appengine.

btw, I find Leiningen much easier than ant while building my clojure apps

Hi Sergey, Thanks for the comments! You definite...

2009-05-11T11:53:00.000-07:00

Hi Sergey,

Thanks for the comments!

You definitely could do this and it's an interesting idea. It could reduce the verbosity (if you use Lisp instead of XML then you avoid the tax on repeated close tag statements).

I'm guessing the XML for the application description would look a little like this:

(appengine-web-app
(:xmlns "http://appengine.google.com/ns/1.0")
(application)
(version 1))
The nesting and parenthesis avoid the need for extra close tags. This would then generate the XML and build artefacts and feed the next part of the process.

That's definitely something I might look at in more detail later. Next on my list will be looking at the persistence API on GAE.

As far as I know, Clojure (as any other Lisp diale...

2009-05-11T07:14:00.000-07:00

As far as I know, Clojure (as any other Lisp dialect) may emit additional sources at compile time using macros.

If this is true (I am not a Lisp hacker, so could not say for sure), it would be interesting to see your example written in pure Clojure that emits all deployment artifacts (like web.xml) using this technique.

What do you think?