On Tue, May 18, 2010 at 04:48:47PM -0700, mdigg...@atmire.com wrote:
On May 17, 2010, at 9:23 AM, Mark H. Wood wrote:
On Fri, May 14, 2010 at 01:57:45PM -0700, mdigg...@atmire.com wrote:
On May 14, 2010, at 12:53 PM, Mark H. Wood wrote:
On Fri, May 14, 2010 at 02:17:01PM +,
On May 17, 2010, at 9:23 AM, Mark H. Wood wrote:
On Fri, May 14, 2010 at 01:57:45PM -0700, mdigg...@atmire.com wrote:
On May 14, 2010, at 12:53 PM, Mark H. Wood wrote:
On Fri, May 14, 2010 at 02:17:01PM +, Tim Donohue (JIRA) wrote:
(Sidenote: Eventually, someday, I feel we should
On Fri, May 14, 2010 at 01:57:45PM -0700, mdigg...@atmire.com wrote:
On May 14, 2010, at 12:53 PM, Mark H. Wood wrote:
On Fri, May 14, 2010 at 02:17:01PM +, Tim Donohue (JIRA) wrote:
(Sidenote: Eventually, someday, I feel we should move the majority of all
configurations to the
On Mon, May 17, 2010 at 12:23:14PM -0400, Mark H. Wood wrote:
[moving complex configuration structures to Spring]
I agree that there are areas of the current configuration that
strongly resist being squashed into Properties format and should
change *somehow*. I'll have to study a bit, though,
I would say something like the database config / connection string would be
the only thing that *needs* to stay in the configs.
So if everything else moved to the DB, then that could be easily/safely
modified in an admin section of the user interface, by the admin user.
Somewhat like modifying
