You can work with two systems. The first system connects to the database. Once you have started it, you can use it to create the second system. Then you start the second system.
The code for this can be wrapped in a single component. On Sunday, May 3, 2015 at 12:02:00 AM UTC+2, Chap Lovejoy wrote: > > Hi, > > I'm building a system which handles data synchronization with remote > services. The credentials and configuration parameters for the remote > services are stored in the database. I'd like to be able to build a > component which is constructed from the information from the database and > uses component to resolve the dependencies for other components in the > system (s3, etc). Is there a mechanism for either adding components to a > system at runtime or resolving the dependencies for a component which can > then be stored as part of the state of another? > > Thanks, > Chap > -- 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.
