so you've not solved the problem, just moved it.

Moving the problem to one password that can be stored as a variable, file, or entered at application boot time, is more manageable, and...]]> Fri, 30 Nov 2007 09:33:57 -0500 Fri, 30 Nov 2007 09:33:57 -0500 Fri, 30 Nov 2007 09:33:57 -0500 Nov 30, 2007 James Watson 0 http://www.theserverside.com/discussions/thread.tss?thread_id=47662

so you've not solved the problem, just moved it.

Moving the problem to one password that can be stored as a variable, file, or entered at application boot time, is more manageable, and IMO more...]]> Thu, 29 Nov 2007 00:04:31 -0500 Thu, 29 Nov 2007 00:04:31 -0500 Thu, 29 Nov 2007 00:04:31 -0500 Nov 29, 2007 Mark N 0 http://www.theserverside.com/discussions/thread.tss?thread_id=47662

so you've not solved the problem, just moved it.

Moving the problem to one password that can be stored as a variable, file, or entered at application boot time, is more manageable, and IMO more...]]> Wed, 28 Nov 2007 17:55:56 -0500 Wed, 28 Nov 2007 17:55:56 -0500 Wed, 28 Nov 2007 17:55:56 -0500 Nov 28, 2007 Daniel Fernandez 1 http://www.theserverside.com/discussions/thread.tss?thread_id=47662

so you've not solved the problem, just moved it.

Moving the problem to one password that can be stored as a variable, file, or entered at application boot time, is more manageable, and IMO more...]]> Wed, 28 Nov 2007 15:09:22 -0500 Wed, 28 Nov 2007 15:09:22 -0500 Wed, 28 Nov 2007 15:09:22 -0500 Nov 28, 2007 James Watson 3 http://www.theserverside.com/discussions/thread.tss?thread_id=47662

Also, why not just store configuration in a simple database table with 2 (or 3) columns: property, value and perhaps server,

where do you put the configuration for that database?

...]]> Wed, 28 Nov 2007 15:05:48 -0500 Wed, 28 Nov 2007 15:05:48 -0500 Wed, 28 Nov 2007 15:05:48 -0500 Nov 28, 2007 James Watson 0 http://www.theserverside.com/discussions/thread.tss?thread_id=47662 Wed, 28 Nov 2007 13:50:19 -0500 Wed, 28 Nov 2007 13:50:19 -0500 Wed, 28 Nov 2007 13:50:19 -0500 Nov 28, 2007 Paul Casal 0 http://www.theserverside.com/discussions/thread.tss?thread_id=47662 so you've not solved the problem, just moved it.

Moving the problem to one password that can be stored as a variable, file, or entered at application boot time, is more manageable, and IMO more secure.]]> Wed, 28 Nov 2007 11:37:10 -0500 Wed, 28 Nov 2007 11:37:10 -0500 Wed, 28 Nov 2007 11:37:10 -0500 Nov 28, 2007 Matt Giacomini 4 http://www.theserverside.com/discussions/thread.tss?thread_id=47662 Wed, 28 Nov 2007 10:39:47 -0500 Wed, 28 Nov 2007 10:39:47 -0500 Wed, 28 Nov 2007 10:39:47 -0500 Nov 28, 2007 Steve Cresswell 5 http://www.theserverside.com/discussions/thread.tss?thread_id=47662 Also, why not just store configuration in a simple database table with 2 (or 3) columns: property, value and perhaps server,

where do you put the configuration for that database?]]> Wed, 28 Nov 2007 00:10:58 -0500 Wed, 28 Nov 2007 00:10:58 -0500 Wed, 28 Nov 2007 00:10:58 -0500 Nov 28, 2007 Mark N 1 http://www.theserverside.com/discussions/thread.tss?thread_id=47662 I never understood why people store login information for a datasource in properties files. It's inflexible, and JEE has a perfectly good working solution for this: jndi datasources.

Also, why not just store configuration in a simple...]]> Tue, 27 Nov 2007 12:27:31 -0500 Tue, 27 Nov 2007 12:27:31 -0500 Tue, 27 Nov 2007 12:27:31 -0500 Nov 27, 2007 Matt Giacomini 0 http://www.theserverside.com/discussions/thread.tss?thread_id=47662 Tue, 27 Nov 2007 09:35:38 -0500 Tue, 27 Nov 2007 09:35:38 -0500 Tue, 27 Nov 2007 09:35:38 -0500 Nov 27, 2007 Peter Mularien 0 http://www.theserverside.com/discussions/thread.tss?thread_id=47662 Tue, 27 Nov 2007 04:51:32 -0500 Tue, 27 Nov 2007 04:51:32 -0500 Tue, 27 Nov 2007 04:51:32 -0500 Nov 27, 2007 Joris Verschoor 4 http://www.theserverside.com/discussions/thread.tss?thread_id=47662 - Hibernate integration: you have to think a bit about your solution if you wanna encrypt PK-FK relationships, no out of the box solution... (yet?)