Adam: You can do this exact thing in Immutant[1]. It can handle multiple applications at the same time, with each application getting an isolated ClassLoader. Each application can optionally have its dependencies resolved at deploy time via pomegranate, and can be (re)deployed independently of other applications within the same container.
[1]:http://immutant.org Adam Clements writes: > I'm working on a web api wrapper around a number of java/clojure libraries. > One problem that I have run into is transitive dependency conflicts, > especially when some of the projects are older than others. > > What I want to do is have each API endpoint's final handler function in its > own classloader, with its own dependencies, ideally downloaded at runtime. > That way none of them will interfere with one another and I can add new API > endpoints without restarting the entire api server process. > > Is this possible? I have come across pomegranate for dependency resolution > and classlojure for evaling in other classloaders, but I can't find any > examples of doing both at once, and my experiments have so far been > unsuccessful. > > Any hints would be much appreciated, > > Thanks, > Adam > > -- -- Toby Crawley http://immutant.org | http://torquebox.org -- -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
