On May 2, 2013 2:04 AM, "David Toomey" <[email protected]> wrote: > Is there anything > I could show that could reveal the problem?
Yes, you should have shown the stack trace of the exception (or at least the part from the top of the text down to your code). But even without that, you have an error coming out of noir.session that says something is unbound where an atom was expected. That should send you to the source for noir.session. There you'll see everything depends on the dynamic global *noir-session*, which is only ever bound by wrap-noir-session, which you're not calling. That's a compojure middleware fn. Take a look at some compojure tutorial to see where and how they're used. There are likely other similar middleware fn calls noir will expect you to have made. Hopefully having struggled with this one, figuring the others out will be easy. -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
