On Wed, Apr 4, 2012 at 12:44 PM, Softaddicts <lprefonta...@softaddicts.ca> wrote: > On some application containers (tomcat, weblogic, ...), AOT can simplify your > life > when configuring your app context, you may need to refer to some of your > Clojure > components but the container can only refer to compiled classes. > On the fly compilation is not an option in this case.
I'll add a caveat here: you need AOT for code that is _directly_ called from Java (such as from an application container), but for code that is called indirectly, you can certainly avoid AOT by requiring namespaces / resolving symbols at runtime. At World Singles, we only have a thin layer of AOT'd code and it does a require followed by a resolve to get at the entry point to the non-AOT'd code. That means we can mostly just ignore all the downsides of AOT :) We have a small project for our AOT code and the rest of our code is in a separate non-AOT'd project. -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ World Singles, LLC. -- http://worldsingles.com/ "Perfection is the enemy of the good." -- Gustave Flaubert, French realist novelist (1821-1880) -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
