Hello again! Well, it has been well over a week already. I appreciate the answers and works by the people who suggested the workarounds and the benign question about the version of Clojure we are using from the dev team. While the proposed workarounds are interesting in themselves and their technological complexity, and allow to somewhat approach the solution of that otherwise simple task, unfortunately, they do not really solve the problem for us: the thread bindings will be flushed on the next call to (require) from Clojure code, and creating a whole web service for classloading is an unaffordable overkill (though, again, thanks for sharing your thoughts and works, I understand that you have worked hard to create them, they just do not suit our usecase). Looks like we're failing.. another success story here.
-- 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/d/optout.
