Open GoogleCodeExporter opened 8 years ago
This is related to, but distinct from http://code.google.com/p/owasp-esapi-
java/issues/detail?id=86
Original comment by manico.james@gmail.com
on 21 Jan 2010 at 1:22
Original comment by manico.james@gmail.com
on 25 Jan 2010 at 10:19
Original comment by manico.james@gmail.com
on 1 Nov 2010 at 1:22
Original comment by chrisisbeef
on 20 Nov 2010 at 9:59
Original comment by manico.james@gmail.com
on 29 May 2012 at 3:20
I am reminded again by a blog post by Will Stranathan about the e-v-i-l-s of
XML for configuration. So if this is something that we would expect an
operations or system administration team to have to edit (and I think that at
least some of the the ESAPI properties would qualify), I think XML is a bad
idea and should be reconsidered.
I doubt I could be as eloquent as Mr. Stranathan, so I will leave it to you to
read his convincing blog post at:
http://will.thestranathans.com/post/20241350046/stop-it
Original comment by kevin.w.wall@gmail.com
on 25 Jun 2012 at 12:57
Original issue reported on code.google.com by
manico.james@gmail.com
on 21 Jan 2010 at 1:21