Maybe you work for a company that leaves DB passwords in plaintext in configuration files on their servers. You would probably be among the majority. Or maybe your company encrypts passwords in configuration files: Also not that uncommon. What’s not common (in my experience) is having the devops team “transmit” the password to the application after it has already been started. It’s a reasonable requirement, but out of the box, Play 2.1 presents several hurdles. continue reading >>
Is anyone else using the Play! framework? I'd be curious to hear your experiences.
Is anyone else using the Play! framework? I'd be curious to hear your experiences.
0 Comments On This Entry
← January 2022 →
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | 3 | 4 | 5 | 6 | 7 | 8 |
| 9 | 10 | 11 | 12 | 13 | 14 | 15 |
| 16 | 17 | 18 | 19 | 20 | 21 | 22 |
| 23 | 24 | 25 | 26 | 27 | 28 | 29 |
| 30 | 31 |
My Blog Links
Recent Entries
-
Changing Play 2 DB Configuration At Runtimeon May 19 2013 05:39 AM
-
Play Framework 2.1: Addendumon Apr 30 2013 03:52 AM
-
Play Framework 2.1: The Bloom Is Off The Roseon Apr 30 2013 03:50 AM
-
Spring 3.0 RESTful web serviceson Dec 01 2009 07:47 PM
-
Useful Java Utilities and Frameworkson Jul 25 2008 08:56 AM
Recent Comments
Search My Blog
4 user(s) viewing
4 Guests
0 member(s)
0 anonymous member(s)
0 member(s)
0 anonymous member(s)



Leave Comment








|