Hello, I like to have the configuration parameters of my webapps not being bundled in resource files in my webapp(*). So that my webapp can be packaged once and for all for a given version, and not be repackaged for each deployment target.
The technique I'm generally using when doing this, which is the most agnostic (IMHO) wrt "where" the webapp will run, is to pass via a JNDI parameter the absolute path to the configuration file having the values relevant to the execution environment. By doing so, the team responsible for managing the webapp has the ability to specify where the configuration file should live. For example, if my webapp must call some remote xml-rpc service, then the URL of the service will change from environment to environment (not the same for testing, pre-production, production, for example). So now my question : is there already somewhere in the ring ecosystem, or elsewhere, a package which already provides this as well as perhaps other facilities to still enable to painlessly use it in conjunction with unit and/or integration testing, etc. ? Thanks in advance, (*) : recent discussions / readings have, tho, somehow started to make me doubt about the "dogma" around my approach. For example, currently, Amazon Elastik Beanstalk seems to promote uploading wars created specifically for a platform (there's not the ability to bootstrap the webapp but from its own embedded resources, AFAIK). -- Laurent -- 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
